WooCommerce server-side tracking
Send WooCommerce events through a first-party gateway instead of relying on a stack of browser pixels and plugin-specific reporting logic.
- 15 minutes
- Trial for proof, Pro when multiple destinations matter
A WooCommerce store that can emit first-party events into Anacoic and inspect destination delivery, blocked/security traffic, and recent health from the same dashboard.
WooCommerce setups often drift across plugins and ad pixels. Anacoic gives you one routing path, one health surface, and a single definition of what was actually delivered.
- Page view
- Product view
- Add to cart
- Checkout
- Purchase
- Meta CAPI
- Google Ads
- TikTok Events API
- LinkedIn CAPI
- Snapchat CAPI
- Pinterest CAPI
- Reddit CAPI
- X
- Bing
- Webhooks
Prerequisites
- An Anacoic gateway
- WordPress or theme access
- Destination credentials for the channels you plan to use
WooCommerce stores and performance teams
Implementation steps
Create a dedicated gateway
Keep the WooCommerce implementation isolated so you can validate store-specific delivery and domain settings cleanly.
Add the tracker or POST directly to /track
The hosted script works for browser-side collection, but backend posting is also supported when you want a stricter server-side path.
Connect only the active destinations first
Validate the real business-critical channels before expanding to the long tail of platforms.
Use the simulator and analytics view to verify
Confirm that the gateway identifies the store correctly and that the destinations show delivery activity as expected.
Questions teams ask before rollout
Does WooCommerce require a plugin?
Not necessarily. The simplest route is using the tracker or direct POST ingestion from your current stack, then configuring destinations in the Anacoic dashboard.
Is the flow different from Shopify?
The store plumbing differs, but the gateway, destination, custom-domain, simulator, and proof workflow stay the same.
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.