You own the storefront. Sumeru owns the data plane.
Headless commerce teams want infrastructure they can integrate, not a pre-built dashboard they have to live in. Sumeru's public REST API ingests events from any frontend; outbound webhooks fan out signed payloads; the OpenAPI spec generates client libraries in your language of choice. Framework-agnostic by design.
Three pain points for headless teams.
"Install our tag" doesn't work.
Most attribution platforms require a JS pixel in the storefront. Headless teams render server-side, generate HTML elsewhere, or use frameworks the pixel doesn't support.
No public ingest endpoint.
SaaS attribution platforms expose dashboards, not APIs. You can't pipe data in from your own systems; you're limited to whatever they ingest natively.
Data trapped in their dashboard.
Even if you ingest correctly, you can't get attributed events back out into your own data warehouse. Custom integrations require export jobs.
Four capabilities most relevant to headless teams.
Public REST API
OAuth + per-shop API keys with scope minimisation. POST events to /v1/events; receive 200 with traceId. OpenAPI spec for any-language client generation.
Outbound webhooks
Subscribe to any event type (attribution.closed, decay.detected, etc.). Payloads HMAC-SHA256 signed. Retry × 4 with exponential backoff, dead-letter queue after.
Identity without pixel
Shopify customer ID is canonical. Cookie + email match optional. Server-side identity stitch handled by the runtime, not the storefront.
Bulk export
BigQuery / Snowflake scheduled export at Enterprise tier. Stream attributed events into your own data warehouse for custom modelling.
Three headless integration shapes.
Capability, not customer deployments - we have none to report yet.
Runs behind a Hydrogen storefront
Hydrogen and other server-rendered storefronts can wire Sumeru through the public API with no pixel at all: events post from your server-side fetch into the ingest endpoint and identity stitches on the Shopify customer ID. You keep the storefront; Sumeru is the data plane behind it.
Custom event ingest from any framework
Composable stacks on Next.js, Remix or SvelteKit stream checkout events over REST against a published OpenAPI spec, with historical backfill supported so attribution is not starting from zero on day one. Ingest latency is measured on your own traffic during the architecture review, not quoted from someone else's.
Outbound webhooks into your own warehouse
If you would rather own the analytics layer, subscribe to the attribution.closed event and the rest of the typed catalogue. Every payload is signed HMAC-SHA256, retried with backoff, and dead-lettered after four attempts. You write your own SQL; Sumeru runs the pipeline that feeds it.
What's included for headless teams.
| Capability | Included |
|---|---|
| Public REST API for event ingest | ✓ OpenAPI spec available |
| Outbound webhooks · HMAC-SHA256 signed | ✓ retry · DLQ · 4 attempts |
| Per-shop API keys with scope minimization | ✓ scoped read/write |
| Event catalog · 18 typed triggers | ✓ payload schema documented |
| Custom event ingest from any framework | ✓ Hydrogen · Next · Remix · custom |
| Identity resolution via Shopify customer ID | ✓ no pixel needed |
| BigQuery / Snowflake bulk export | ✓ Enterprise tier |
| Recommended tier | Pro / Enterprise |
API-first integration surfaces.
Walk through the API + webhook signing.
We sketch your storefront stack, walk through the OpenAPI spec, fire a few sample events live, and demonstrate the outbound webhook signature flow. By the end you have a working integration plan and a price range, in writing.