StoreMetrics Docs

StoreMetrics Docs

Search product docs or ask for an answer based on the docs.

Reference

Event reference

Every tracker and revenue event StoreMetrics understands — plain language first.

Event reference

Tracker events

EventPlain English
script_loadedTracker woke up on the page
page_viewSomeone viewed a page
product_viewSomeone viewed a product
add_to_cartCart intent
begin_checkoutCheckout started
rage_clickAngry repeated clicks — UX smoke
dead_clickClick that went nowhere useful
js_errorFront-end JavaScript error signal
network_errorFailed network request signal
page_exitLeaving / session timing signal

Revenue / commerce (normalized)

UI labelOrigin
PurchaseShopify paid order or Stripe paid session/invoice
RefundsStripe charge.refunded (affects revenue truth)

Common metadata

Path, title, referrer, UTM, browser, OS, device, viewport, geo, masked IP, visitor id, session id, browser id, identity hints, durations from visibility / page_exit.

Web JS API

// After login — stitch identity
window.velora("identify", {
  user_id: "user_123",
  name: "Ada",
  email: "ada@example.com",
});

Custom track / screen appear on the mobile install path. The web snippet is intentionally small.

Feed labels you will recognize

Purchase · Page view · Product view · Add to cart · Checkout started · Tracker loaded

Prompt

Map my storefront funnel to StoreMetrics events for YOUR_DOMAIN.

Which automatic events should I expect without custom code?
Where should I add identify()?
Which friction events (rage_click / dead_click / js_error) would explain my cart drop-off?