get_store_analytics
The analytics report of one store, read from the same code as the merchant’s Analytics page and its export. Every revenue, order, buyer, conversion, AOV or engaged-shopper number you give comes from this report, so the merchant sees the same number in the chat, on the page and in the export. A number you build yourself in SQL has another meaning and will not match. Amounts are in report.currency. This store’s domains, headless shop, app traffic and widgets. A shopper who watched a video, finished a try-on or chatted. Autoplay counts only after the shopper interacts, and opens are counted separately. An order counts if the same shopper placed it in this store within the window after a widget open, both in the same period. For conversion, the window starts at engagement. Engaged shoppers who bought within the window after engaging, divided by all engaged shoppers. No daily conversion: engagement and order can fall on different days. Items added to cart from a widget within the window before the order. N/A: no widget add to cart was recorded. Other items a widget showed within the window before the order. Other items in the same order. Direct (In-video + Post-video) + Indirect. Average order value of Tolstoy shoppers compared with the store’s other orders. A comparison, not lift. N/A means nothing was measured; 0 is a real zero. Impressions, Plays and Shoppers who wrote show N/A when none was recorded. The overview section holds overview, daily, widgetCatalog, liveWidgetTypes, widgetTypes and widgets; the details section holds topVideos, topProducts, events, tryOn and chat. A section that was not asked for is null. Rows do not add up: one shopper or order can count under several widgets. Widgets that ran on this store in the period or are live, whatever the filters. Live = published and active. Widget type tolstoy-sdk lists the store’s own events sent with the Tolstoy SDK. They are not opens, engagement, try-ons, add to carts or revenue.Input schema
Input schema