Ingest usage events
POST/api/v1/usage_events
Reports what merchants do inside your app. Events power the Behavior section (analytics, funnels, metrics) and can trigger flows.
Send a single event at the root, or a batch of up to 200 under events; a top-level myshopifyDomain covers events without their own customerId. Events named page_view with a path feed web analytics and page-view reports.
Event fields
Section titled “Event fields”eventNamestringrequired- Stable, action-shaped name (
nameis accepted as an alias). customerIdstringrequired- The shop’s myshopify domain (
myshopifyDomainis an alias). eventIdstring- Idempotency key; duplicates are silently dropped, so retries are safe.
timestampstring- ISO 8601; defaults to arrival time.
propertiesobject- Free-form; numeric values power report calculations.
pathstring- For
page_viewevents. sessionKeystring- Groups page views into sessions; a 30-minute gap rule applies regardless.
Returns
Section titled “Returns”202Ingested;
dropped counts nameless or shopless events.400No valid events in the payload.
401Bad or missing
X-Api-Key.429Past 1,200 events/minute for this app.