Analytics

Analytics Overview

4min

Required for conversion rate reporting as well as machine learning, the Magento module will send data for all orders placed on the store being synchronised, including those placed through the Magento admin panel.

Data is queued for synchronisation after the order is first created in Magento, and sent to Klevu’s APIs in a background process a short time later to ensure synchronisation actions do not interfere with the speed and stability of the installation. Orders can also be manually queued for synchronisation, for example when integrating a store with existing order history.

Quick Reference

CLI Commands

Command

Purpose

klevu:analytics:queue-orders-for-sync

Adds Magento orders to the internal queue to be processed in an upcoming sync operation

klevu:analytics:sync-orders

Sends unprocessed order records to Klevu’s analytics APIs

Cron Jobs

Code

Schedule

Group

 

klevu_analytics_remove_synced_order_history

Every day at midnight (0 0 * * *)

klevu

Prunes order history records, if enabled in configuration settings

klevu_analytics_requeue_stuck_orders

On the hour (0 * * * *)

klevu

Moves orders stuck in “processing” back into the queue for sync

klevu_analytics_sync_orders

Custom (default */5 * * * *)

klevu

Sends unsynced orders to Klevu’s analytics APIs

Config Settings

Klevu > Data Sync > Order Analytics

Sync status, frequency, and order status exclusions list

Klevu > Developer Settings > Order Analytics

Contains advanced settings primarily designed to tweak performance, data provision, and other system-related configuration

Klevu > Developer Settings > Logging

Allows setting the verbosity of analytics related messages

Backend Interfaces

Additional sync-related data added to the native Magento Order Grid and View Order screens.