Reference
Event reference
Every tracker and revenue event StoreMetrics understands — plain language first.
Event reference
Tracker events
| Event | Plain English |
|---|---|
script_loaded | Tracker woke up on the page |
page_view | Someone viewed a page |
product_view | Someone viewed a product |
add_to_cart | Cart intent |
begin_checkout | Checkout started |
rage_click | Angry repeated clicks — UX smoke |
dead_click | Click that went nowhere useful |
js_error | Front-end JavaScript error signal |
network_error | Failed network request signal |
page_exit | Leaving / session timing signal |
Revenue / commerce (normalized)
| UI label | Origin |
|---|---|
| Purchase | Shopify paid order or Stripe paid session/invoice |
| Refunds | Stripe 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?