In this guide
- A Meta plugin sends server events for WooCommerce quickly. A Tag Manager server container covers more platforms and gives you control.
- For the container route you need a data layer from WooCommerce, for example from a Tag Manager plugin, plus a server container.
- Share an event ID and test in Test Events.
WordPress and WooCommerce stores sit on a spectrum. Some want a plugin that does the job. Others run Meta, Google and TikTok together and want one place for the data. This page covers both approaches and the common mistakes with WooCommerce. For general concepts read Conversions APIs explained.
Route 1: a plugin
Meta's own plugin for WooCommerce and several third-party plugins can send Conversions API events from your WordPress server. You connect the dataset and an access token, choose events and the plugin handles event IDs. This is the shortest path for a store that advertises on Meta only.
- Good for: a one-platform store and a small team.
- Limits: each platform needs its own plugin, cookies stay at browser defaults, and control over fields is limited by the plugin's settings.
Runs on your domain, anywhere
Your tracking runs on your own domain, so a visit from any country is handled the same way.
Route 2: a Tag Manager server container
Add Tag Manager and a data layer
Use a Tag Manager plugin for WordPress that pushes WooCommerce events (view item, add to cart, begin checkout, purchase) to the data layer.
Point the web container to your tagging subdomain
Set the server container URL in the Google tag settings. See DNS configuration.
Share the event ID
Push an event_id with each event and read it in both the pixel and the server tag. See event deduplication.
Pass customer data
Add hashed e-mail and phone from the checkout when the visitor has consented.
WooCommerce specifics
- The order received page can reload. Fire the purchase once, using the order number as the event ID or
transaction_id. - Caching plugins can serve an old data layer. Exclude cart, checkout and order pages from the cache.
- Payment gateways that redirect may drop the visitor on a thank-you page without your tags. Test your gateway.
- Variations need the right product ID in the items array, so catalog ads match.
Check your tracking in one pass
This is an example. Run the check on your own site to see where yours stands.
What a managed server adds
With Open Tracked as the host, the plugin question becomes a small one. The container, domain and power-ups run for you: Cookie Keeper keeps cookies alive, the Data Store and Enricher add stored data to later events, Custom Loader serves the Tag Manager script from your domain and Bot Detection helps keep crawler traffic out of your numbers. All of these are on the free plan. Open Tracked also has its own WordPress plugin, which connects your store with a one-time key and syncs orders from the server. You can use it with or without a Tag Manager plugin for the data layer.
Common problems
Which route would we pick?
A WordPress site with a handful of products and one ad platform does well with a plugin. A WordPress or WooCommerce store that runs Meta, Google and TikTok, or that wants longer cookies and stored customer data, does better with a server container. The deciding factor is rarely traffic. It is how many places you would otherwise have to fix the same problem. With three platforms you would configure three plugins, each with its own event IDs and its own idea of consent. With a container you do it once.
Whichever you choose, document it. Write down which plugin or container sends which event, who owns the access tokens and where the data layer comes from. WordPress sites change hands often, and the next developer will thank you. A one-page note kept next to your container notes is enough.
Terms you will see
- Data layer
- A list of values the page pushes for Tag Manager to read.
- Tag Manager plugin
- A WordPress plugin that adds the container and builds a data layer from WooCommerce.
- Order received page
- The WooCommerce page shown after payment.
- Page cache
- A stored copy of a page served without running WordPress.
- Event ID
- The value that lets Meta count a browser event and its server copy once.
Watch events arrive, live
A sample feed. In Open Tracked you see the same stream for your own store.
Frequently asked questions
Is there a Conversions API plugin for WooCommerce?
Yes. Meta offers one and several third-party plugins do too.
Do I need Tag Manager for the Conversions API on WordPress?
No. A plugin can do it. Tag Manager and a server container help when you use several platforms or want more control.
How do I stop double purchases on WooCommerce?
Use one server route and fire the purchase once per order with a shared event ID.
Does caching break tracking?
It can. Exclude cart, checkout and order pages from page caching.
Does Open Tracked have a WordPress plugin?
Yes. The Open Tracked WordPress plugin connects your store with a one-time key and syncs orders from the server. You can still use a Tag Manager plugin for the data layer.
Do I need spreadsheets to read my results?
No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.
Is Open Tracked different from Open Track or Open Space Track?
No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.
Fix your tracking at the source
Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.
The Open Tracked team
We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?
Comments
Loading comments...
Integrations · 5 min read