Skip to main content
storekit collects behavioural events to help you understand customer journeys, optimise conversions, and power marketing integrations. This page explains what we track, how data flows, and how events integrate with third-party platforms.
This page is the reference for the raw events. For how those events are turned into the numbers on the Guest activity page — Guests, Total Sessions, Sessions with Order, Conversion Rate and the Conversion Funnel steps — see Visitor Metrics Explained.

Native Event Collection

storekit automatically collects events across web and native apps without requiring additional code.

Core Commerce Events

Fired when a customer lands on the store.
Fired when a customer opens a product modal.
Fired when an item is added to the basket.
Fired when an item is removed from the basket.
Fired when the customer opens the checkout screen.
Fired when payment is confirmed and the order is placed.

Search & Discovery Events

Fired when a customer performs a search (debounced by 1 second).
Fired when the cross-sell modal is displayed.
crossSellType is either "product" or "category" depending on configuration.
Fired when the upsell modal is displayed after a customer adds an item to the cart.

Discount Events

Fired when a customer submits a discount code.
Fired when a discount code is successfully applied.
Fired when a discount code is rejected.

Promotional Offer Events

Fired when a promotional offer becomes visible.
Fired when a customer clicks on a promotional offer.

Stories Events

Fired when a customer opens the story viewer.
Fired when a story page is viewed.
Fired when a customer navigates between story pages.
Fired when a customer clicks a CTA within a story.
Fired when a customer views all pages of a story.
Fired when the story viewer is closed.

Experimentation Events

Fired when a customer is exposed to an A/B test variant.

Item ID Resolution

When sending begin_checkout and purchase items to Google Tag Manager, storekit resolves the item_id using the following priority:
  1. PLU - Point of sale lookup code (preferred for POS-connected stores)
  2. SKU - Stock keeping unit
  3. POS ID - External POS system identifier
  4. ID - storekit’s internal product ID (fallback)
The other events use a shorter chain: view_item uses plu || sku || id, and add_to_cart uses the PLU only, so item_id is left out (undefined) for products without a PLU.
For best results, ensure your products have PLU codes configured if you’re using a POS integration. This keeps your analytics data consistent with your POS reports.

Platform Integrations

storekit forwards events to third-party platforms in their native format. Events are transformed automatically—no mapping required.

Meta (Facebook) Pixel

Events are sent to Meta’s Pixel API. A PageView event fires automatically on initialisation.
Triggered by add_to_cart
Triggered by started_checkout
Triggered by order_completed
When the order has a customer email, storekit also passes the customer’s email, phone and name to the Pixel as advanced matching data before sending Purchase.
These events are sent from the customer’s browser by the Meta Pixel. storekit doesn’t send server-side events to Meta.

Google Analytics 4 / Google Tag Manager

Events are pushed to the dataLayer following GA4’s e-commerce schema. The ecommerce events (view_item, add_to_cart, begin_checkout, purchase) carry their fields twice: under ecommerce, as Google documents, and at the top level as shown below. Each one is preceded by { "ecommerce": null }. Item prices include paid modifiers, and every item carries item_category. Before the container loads, storekit also pushes { "order_channel": "web" }, or { "order_channel": "app", "app_platform": "ios" } inside your storekit app. See Google Tag Manager.
Triggered by viewed_product
Triggered by started_checkout
Triggered by order_completed

Klaviyo

Events are sent to Klaviyo for email marketing automation. Customer identity is linked via email when available using klaviyo.identify(). Klaviyo’s own Active on Site metric is recorded by Klaviyo’s script once a profile is identified; storekit doesn’t send it. Prices are in major units (3.5 means £3.50). ProductId is the first of the product’s PLU, SKU, POS ID or Deliverect ID that is set, falling back to storekit’s product ID.
Triggered by active_on_site on a store
Triggered by active_on_site on a brand’s store-selection page
Triggered by viewed_product. storekit also records the product in Klaviyo’s recently viewed items.
Triggered by add_to_cart. Also carries the whole basket: $value, CheckoutURL, ItemCount, ItemNames, Categories and Items.
Triggered by started_checkout. Also carries the basket fields listed under Added to Cart.

1st Party Event Collection

storekit also sends events to its own first-party analytics pipeline, which powers reports such as Guest activity. These events stay with storekit: they are not part of Data Warehouse Export, which exports orders, menus and payments. All events include base context properties automatically. The pipeline also receives further events not listed here, such as modifier, kiosk, reorder and payment-step events. Base context (included in all events):
Triggered by active_on_site. Also identifies the user.
Triggered by viewed_product
Triggered by click_offer
Triggered by viewed_experiment

Configuration

Enabling Integrations

  1. Go to Stores → your store → Settings → Integrations
  2. Select the analytics platform
  3. Enter your pixel/measurement ID or API key:
    • Google Tag Manager: Google Tag Manager ID (GTM-XXXXXXX)
    • Meta Pixel: Meta Pixel ID
    • Klaviyo: turn on Enable Klaviyo and enter your Private key
  4. Events begin flowing immediately

Supported Chat Integrations

The analytics system also initialises chat widgets when configured:
  • Front Chat
  • Superchat
  • Tawk.to
  • Intercom

Troubleshooting

Check that your pixel ID is correct and the integration is enabled. Events are sent from the customer’s browser, so ad blockers and browser privacy settings can stop some of them. Some platforms take a while to show new events in their reports.
Ensure your analytics platform is configured for the correct currency. storekit sends values in the store’s local currency. The raw events above carry prices in minor units (pence/cents); the values sent to Meta, Google and Klaviyo are converted to major units (pounds, euros, dollars).
Anonymous visitors are tracked with a device-based ID. User identity is associated once they provide their email at checkout.
Analytics are disabled when viewing the store in Store Designer mode to avoid polluting your data with test traffic.