Native Event Collection
storekit automatically collects events across web and native apps without requiring additional code.Core Commerce Events
active_on_site
active_on_site
viewed_product
viewed_product
add_to_cart
add_to_cart
remove_from_cart
remove_from_cart
started_checkout
started_checkout
order_completed
order_completed
Search & Discovery Events
products_searched
products_searched
cross_sell_modal_view
cross_sell_modal_view
crossSellType is either "product" or "category" depending on configuration.upsell_modal_view
upsell_modal_view
Discount Events
discount_entered
discount_entered
discount_applied
discount_applied
discount_denied
discount_denied
Promotional Offer Events
viewed_offer
viewed_offer
click_offer
click_offer
Stories Events
story_viewer_opened
story_viewer_opened
story_viewed
story_viewed
story_cta_clicked
story_cta_clicked
story_completed
story_completed
story_viewer_closed
story_viewer_closed
Experimentation Events
viewed_experiment
viewed_experiment
Item ID Resolution
When sendingbegin_checkout and purchase items to Google Tag Manager, storekit resolves the item_id using the following priority:
- PLU - Point of sale lookup code (preferred for POS-connected stores)
- SKU - Stock keeping unit
- POS ID - External POS system identifier
- ID - storekit’s internal product ID (fallback)
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.
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. APageView event fires automatically on initialisation.
AddToCart
AddToCart
add_to_cartInitiateCheckout
InitiateCheckout
started_checkoutPurchase
Purchase
order_completedPurchase.Google Analytics 4 / Google Tag Manager
Events are pushed to thedataLayer 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.
active_on_site
active_on_site
view_item
view_item
viewed_productadd_to_cart
add_to_cart
begin_checkout
begin_checkout
started_checkoutpurchase
purchase
order_completedKlaviyo
Events are sent to Klaviyo for email marketing automation. Customer identity is linked via email when available usingklaviyo.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.
Viewed Brand
Viewed Brand
active_on_site on a brand’s store-selection pageViewed Product
Viewed Product
viewed_product. storekit also records the product in Klaviyo’s recently viewed items.Added to Cart
Added to Cart
add_to_cart. Also carries the whole basket: $value, CheckoutURL, ItemCount, ItemNames, Categories and Items.Started Checkout
Started Checkout
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):venue_loaded
venue_loaded
active_on_site. Also identifies the user.product_modal_view
product_modal_view
viewed_productadd_to_cart
add_to_cart
remove_from_cart
remove_from_cart
order_completed
order_completed
cross_sell_modal_view
cross_sell_modal_view
upsell_modal_view
upsell_modal_view
viewed_offer
viewed_offer
clicked_offer
clicked_offer
click_offerproducts_searched
products_searched
experiment_viewed
experiment_viewed
viewed_experimentstory_viewer_opened
story_viewer_opened
story_viewed
story_viewed
story_cta_clicked
story_cta_clicked
story_completed
story_completed
story_viewer_closed
story_viewer_closed
Configuration
Enabling Integrations
- Go to Stores → your store → Settings → Integrations
- Select the analytics platform
- 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
- Events begin flowing immediately
Supported Chat Integrations
The analytics system also initialises chat widgets when configured:- Front Chat
- Superchat
- Tawk.to
- Intercom
Troubleshooting
Events not appearing in Meta/Google
Events not appearing in Meta/Google
Revenue values don't match
Revenue values don't match
Missing user identity
Missing user identity
Store Designer mode
Store Designer mode