Shopify server-side tracking
Deploy a first-party Shopify signal path with one gateway, routed destinations, delivery health, and a cleaner operator workflow than piecing together multiple browser pixels.
- 10 minutes
- Trial for validation, Pro for active production use
A Shopify storefront that sends first-party events into Anacoic, where you can inspect health, security, recent delivery, and destination status from one control plane.
One Shopify event stream, routed through a gateway you control, with delivery visibility, custom-domain support, and a destination setup path that stays consistent across platforms.
- Page view
- Product view
- Add to cart
- Checkout start
- Purchase
- Meta CAPI
- Google Ads
- TikTok Events API
- LinkedIn CAPI
- Snapchat CAPI
- Pinterest CAPI
- Reddit CAPI
- X
- Bing
- Webhooks
Prerequisites
- An Anacoic account and a gateway
- Access to your Shopify theme or theme app extensions
- Destination IDs or credentials for the platforms you plan to use
Shopify brands and ecommerce agencies
Implementation steps
Create a gateway for the storefront
Start with one dedicated gateway per store so health, domains, delivery, and receipts stay isolated.
Install the tracker or server call
Use the hosted tracker on the storefront or send events to the ingestion endpoint from your app backend.
<script src="https://edge.anacoic.com/v1/ana.js" data-gateway-id="YOUR_GATEWAY_ID"></script>Connect the destinations you actually use
Configure the ad and analytics endpoints you care about first, then validate them one by one from the simulator and recent delivery views.
Move to a first-party domain when ready
After validation, add a custom tracking domain so the storefront uses your brand-controlled first-party surface.
Questions teams ask before rollout
Do I need a Shopify app?
No. The simplest path is the hosted tracker or a server-side call from your existing stack, then configuring destinations inside the dashboard.
Can I run this next to my existing pixels?
Yes. The safest rollout is parallel validation first, then you retire redundant browser-only paths once delivery and match quality are confirmed.
Validate with one live path first
The best rollout is always one controlled path first: configure the gateway, validate the destination, then scale out once the delivery and health surfaces reflect the expected traffic.
Keep the integration isolated while you test it.
Confirm the request shape, security checks, and delivery outcome.
Cut over the real path only after the dashboard truth matches the simulation.