Your WooCommerce dashboard shows 40 orders last week. Meta Ads Manager reports 31. Google Ads reports 24. Nothing is wrong with your store. The ad platforms simply never heard about some of those sales.
That gap costs more than a messy report. Meta and Google only learn from the conversions they receive, so every missing sale makes their bidding, targeting and audiences a little worse. This guide shows how to send conversion data to Meta and Google Ads from a WordPress or WooCommerce site, through the browser, your own domain and your server, without counting the same sale twice.
The short answer: keep the Meta Pixel and the Google tag for the basics, turn on advanced matching and enhanced conversions, then add server-side tracking (the Meta Conversions API, server-side Google Tag Manager or offline uploads) for the sales the browser misses. Give each sale the same event ID on every route so it is counted once.
What changed recently: since June 2026, Google Ads treats enhanced conversions as a single on/off setting, and offline conversion uploads sent through an API now use the Data Manager API instead of the Google Ads API. Many older tutorials still describe the previous setup. Both changes are covered below.

Table of contents
- Why do Meta and Google need your conversion data?
- Why does conversion data go missing?
- What are the ways to send conversion data?
- How do you send conversion data to Google Ads?
- How do you send conversion data to Meta?
- Google Ads vs Meta: the matching tools side by side
- Which setup fits your WordPress site?
- WordPress problems that quietly break conversion tracking
- How do you test your setup before trusting it?
- What should you watch out for?
- Your conversion tracking checklist
- How this guide was checked
- Server-side tracking, CAPI and enhanced conversions: quick answers
Why do Meta and Google need your conversion data?
A conversion is the action you pay ads to produce: a purchase, a lead form, a booked call or a signup. When it happens, Meta and Google need to hear about it, and they use that signal in three ways.
Reporting
The numbers in Ads Manager and Google Ads decide which campaigns you keep. If a platform undercounts, a profitable campaign can look weak, and you may pause the one that was paying for itself.
Optimization
Both platforms learn who to show ads to by studying the people who converted. Fewer reported conversions means slower learning, wider guesses and a higher cost per result. Smart Bidding in Google Ads and Advantage+ campaigns on Meta both depend on this feedback loop.
Audiences
Retargeting lists and lookalike audiences (new people who resemble your buyers) are built from converters. Missing conversions shrink those lists and make them less accurate.
Why does conversion data go missing?
Most of the loss happens between the visitor’s browser and the ad platform. These are the usual causes:
- Ad blockers and privacy browsers stop tracking scripts from loading or sending data.
- Cookie banners. Visitors who decline tracking are not tracked by the browser tag, which is exactly how it should work.
- Browser limits. Safari and Firefox shorten how long tracking cookies last, so a buyer who returns days later may not be linked to the original ad click.
- Offline and delayed sales. A deal closed on a call or paid by invoice never touches your website.
- Site changes. A new form plugin, a removed thank-you page or a checkout redesign can silently stop the tag from firing.
- WordPress-specific causes such as page caching, delayed JavaScript and off-site payment gateways, covered in their own section below.
Run a gap check, and compare the right numbers. Ads Manager and Google Ads only show conversions they credit to an ad, so they will always sit below your total orders. For a cleaner test, compare last week’s paid WooCommerce orders (or qualified leads in your CRM) with the Purchase events Meta received in Events Manager, which counts events whether or not an ad gets credit, and with purchases in GA4. If Meta received far fewer Purchase events than you had orders, events are getting lost before they arrive. A gap that suddenly widens, or zero conversions on a day you had sales, means something broke.
A worked example. Say WooCommerce shows 120 paid orders last week, Events Manager shows 84 Purchase events received, and Ads Manager credits 41 purchases to your ads. The 41 is an attribution number and will always be lower, so leave it out of this check. The 84 is the real problem: 36 orders, or 30 percent of your sales, never reached Meta at all. That missing 30 percent is the gap the Conversions API is built to close.

What are the ways to send conversion data?
There are two basic routes, client-side and server-side, plus a middle option that sits between them.
Client-side (browser) tracking
A script in the visitor’s browser reports the conversion. The Meta Pixel and the Google tag both work this way. On WordPress it is the easiest place to start, because a plugin or Google Tag Manager (free) can install both in minutes. The weakness is that everything depends on the browser, so ad blockers, cookie choices and browser limits can stop it.
Server-side tracking
Your server, store or CRM sends the conversion straight to Meta or Google without relying on the visitor’s browser. It takes more setup, and some options add a monthly hosting cost. It is also the only way to send sales that happen offline or days later.
The middle option: tags on your own domain
The script still runs in the browser, but it loads and sends data through your own domain instead of a Google or Meta domain. Blockers stop fewer of these requests, though not all of them.

| Client-side | Own domain | Server-side | |
|---|---|---|---|
| Where it runs | Visitor’s browser | Browser, routed through your domain | Your server, store or CRM |
| Setup effort | Low | Low on Cloudflare, medium elsewhere | Medium to high |
| Blocked by ad blockers | Often | Less often | Rarely |
| Sends offline sales | No | No | Yes |
| WordPress example | Meta Pixel through a plugin, Google tag through Site Kit | Google tag gateway on Cloudflare | Meta for WooCommerce sending the Conversions API, or server-side GTM |
| Best for | Getting started | A quick improvement for Google tags | Stores and lead-gen sites spending real money on ads |
Why should you use both?
The strongest setup runs browser and server tracking together. The browser catches what it can, including details such as the ad click ID, and the server fills in what the browser missed. The platforms then remove duplicates so each sale counts once, which only works when both routes label the sale the same way. The Meta section below shows how.
How do you send conversion data to Google Ads?
Google offers six main methods, listed here from simplest to most involved, plus Consent Mode, which sits underneath all of them.
1. The Google tag or a Google Tag Manager conversion tag
The tag fires when someone reaches a thank-you page or submits a form. On WordPress, Google’s Site Kit plugin connects the Google tag without code, and the Google for WooCommerce plugin can set up purchase conversion tracking for a store. This is the starting point for everyone.
2. Importing GA4 key events into Google Ads
If GA4 already tracks your purchases or leads, mark them as key events and import them into Google Ads as conversions. It is simple, but it inherits every gap GA4 has. After importing, check whether each action is set as primary or secondary in Google Ads, because only primary actions feed bidding.
3. Enhanced conversions
Enhanced conversions sends a hashed (scrambled) email address or phone number along with the tag. Google uses it to match the sale to a signed-in Google user, which recovers conversions that cookies alone would miss. For very little work, it is one of the biggest accuracy gains available. Since June 2026, Google has combined enhanced conversions for web and for leads into a single on/off setting, so you no longer pick a method for each conversion action. The change has rolled out gradually, so some accounts still show separate web and leads rows for a while.
WordPress note: Site Kit has a setting called plugin conversion tracking, which used to be labeled “enhanced conversion tracking.” It records events from supported plugins such as WooCommerce, WPForms and Contact Form 7. It is not the same thing as Google Ads enhanced conversions, so check both settings.
4. Google tag gateway
Google tag gateway for advertisers loads Google’s tags through your own domain, so fewer requests get blocked and cookies are set on your domain. If your site already runs through Cloudflare with the proxy turned on (the orange cloud), setup takes a few clicks from Google Tag Manager or the Google tag settings, and Cloudflare does not charge for it. Akamai and manual setups also work. It only helps Google’s tags, not Meta’s.
5. Server-side Google Tag Manager
Here you run your own tagging server. The browser sends data to it once, and it forwards that data to Google Ads, GA4 and other platforms, Meta included. You get more control over what each platform receives, at the cost of more setup and a hosting bill. Hosted services such as Stape run the server for you.
6. Offline and CRM conversions
Use this when a lead turns into a sale later, such as a deal closed on a call. You send the sale back to Google with the customer’s details or the click ID (the code Google adds to ad links). Google calls this enhanced conversions for leads, and uploads go through Google Ads Data Manager using a connector, a file upload or an API. On a WordPress lead form, save the click ID in a hidden field so your CRM already has it when the deal closes.
One change matters if you follow older tutorials. Since June 15, 2026, Google routes offline conversion imports and enhanced conversions for leads uploads through the Data Manager API. New integrations can no longer use the Google Ads API for this, and existing ones are being migrated. Google’s enhanced conversions for leads documentation has the current setup steps.
Stop Google Ads from counting a sale twice
Google removes duplicates with a transaction ID. Pass the WooCommerce order ID as the transaction ID on your purchase conversion, and send the same ID with any server-side or uploaded copy of that sale. When two conversions for the same conversion action share a transaction ID, Google Ads counts only one, which also protects you when a buyer reloads the order-received page. The ID must be unique for every order: a fixed value would make Google throw away real sales.
Consent Mode v2
Google’s tags need to know each visitor’s cookie choice, and Consent Mode is how they receive it. Your consent banner passes four signals (ad_storage, analytics_storage, ad_user_data and ad_personalization), and the tags adjust what they collect. If you have visitors from the European Economic Area, the UK or Switzerland, Google expects these signals before it uses their data for ad measurement and personalization. Many WordPress consent plugins send them for you, but confirm that yours does.
How do you send conversion data to Meta?
Meta’s options for Facebook and Instagram ads mirror Google’s: a browser script, a way to improve matching, a server-side route and offline events.
1. Meta Pixel
The Meta Pixel is Meta’s browser script. It fires standard events such as Purchase, Lead and CompleteRegistration. You can add it to WordPress with a plugin or through Google Tag Manager, and our WordPress Facebook Pixel guide walks through both. Like any browser tag, it can be blocked.
2. Advanced matching
Advanced matching lets the Pixel send hashed customer details, such as the email typed at checkout, with each event. That helps Meta connect the event to a real account. Turn on automatic advanced matching in Events Manager, where Meta manages your Pixels and events.
3. Meta Conversions API (CAPI)
The Conversions API is Meta’s server-side route. Your server or store sends events directly to Meta, so ad blockers and browser limits do not stop them. It is the main fix for a Pixel that misses sales, and there are four ways to set it up:
- A partner integration. On WooCommerce, the official Meta for WooCommerce plugin (formerly Facebook for WooCommerce) sends Pixel and Conversions API events with matching event IDs. Shopify and other platforms have their own integrations.
- Meta’s Conversions API Gateway, which runs on cloud hosting you control and carries a monthly hosting cost.
- A Meta tag in server-side Google Tag Manager, handy if you already run a tagging server for Google.
- A direct integration that a developer builds against Meta’s API.
4. Offline and CRM events
When a sale closes later, your CRM can send it to Meta through the Conversions API, so Meta learns which leads actually became customers.
Run the Pixel and CAPI together
Meta recommends running both, and its documentation on deduplicating Pixel and Conversions API events sets out the matching rules. To avoid counting a sale twice, send the same event name and the same event ID from the Pixel and from the server. On a WooCommerce store, the order ID makes a good event ID for Purchase, because it is unique and both sides know it. When the name and ID match, Meta keeps one copy and drops the other. Good plugins handle this for you. The trouble starts when two different plugins send the same event, each with its own ID.

Event Match Quality
Event Match Quality is a score from 0 to 10 in Events Manager that shows how well your events match real Meta accounts. Sending more good customer details, such as email, phone and Meta’s click ID, raises it. Check it per event: a Purchase event with a low score usually means the server side is missing customer details.
Google Ads vs Meta: the matching tools side by side
Both platforms solve the same problems with differently named tools. Use this table to translate one setup into the other.
| Job | Google Ads | Meta |
|---|---|---|
| Browser tag | Google tag or Google Tag Manager | Meta Pixel |
| Customer-data matching | Enhanced conversions | Advanced matching |
| Server-side route | Server-side Google Tag Manager or the Data Manager API | Conversions API |
| Loading tags from your domain | Google tag gateway | No direct equivalent, so rely on the Conversions API |
| Offline and CRM sales | Enhanced conversions for leads through Google Ads Data Manager | CRM events through the Conversions API |
| Stopping double counts | Transaction ID (your order ID) | Event ID plus event name |
| Match quality check | Enhanced conversions diagnostics | Event Match Quality score (0 to 10) |
| Consent signals | Consent Mode v2 | Pixel consent controls set by your banner |
Which setup fits your WordPress site?

You do not need every method above. Match the setup to how your business makes money.
A small WooCommerce store
Start with Meta for WooCommerce for the Pixel and the Conversions API, and Google for WooCommerce or Site Kit for the Google tag. Turn on enhanced conversions and advanced matching, and add Google tag gateway if you already use Cloudflare. That covers most of the gap without a developer.
A growing store advertising on several platforms
Once you advertise on Meta, Google and one or two more networks, server-side Google Tag Manager starts to pay off: one data stream from your site, passed on to every platform, with a single place to manage consent and event IDs.
A lead-generation site with forms
Send each form submission as a lead conversion from the browser, with enhanced conversions and advanced matching on, and save the Google click ID in a hidden form field. When leads become customers, send those sales back through enhanced conversions for leads and Meta’s Conversions API, so both platforms learn which leads are worth paying for.
Phone, invoice or long sales cycles
Offline uploads are the core of your setup, not an extra. The browser will never see these sales, so connect your CRM or upload a file on a fixed schedule.
If you want the field-level detail behind these setups, such as which fields each event needs, hashing rules, how long to keep click IDs and setups for Shopify, SaaS and marketplaces, this detailed technical guide goes deeper than we do here. Editorial note: our reviewer, Ansh Agrawal, founded Datalyze, which publishes that guide. We link to it because it covers field-level setup in more depth than this article. Visualmodo has no commercial arrangement with Datalyze.
WordPress problems that quietly break conversion tracking
On WordPress, conversion tracking rarely breaks on the day you set it up. It breaks later, after an update or a change nobody connected to tracking. Watch for these five.
Page caching and delayed JavaScript
Caching makes WordPress fast, but it can serve one visitor’s page to the next. If a cached page contains an event ID, many visitors send the same ID, and Meta warns that it received the same event ID for many event instances. Keep cart, checkout and order-received pages out of the cache. If your caching plugin delays JavaScript until the first scroll or click, exclude your tracking scripts or confirm that events still fire for visitors who leave quickly.
Forms that never reach a thank-you page
Many WordPress form plugins submit without reloading the page, so a tag set to fire on a thank-you URL never fires. Either trigger the conversion on the form plugin’s success event, or redirect to a dedicated thank-you page and keep that page out of search results.
Off-site payment gateways
Some payment methods send the buyer to another site to pay. If the buyer never comes back to your order-received page, the browser never fires the Purchase event. A server-side event sent when WooCommerce marks the order as paid, usually after the payment provider confirms it in the background, does not depend on that return trip.
Two plugins sending the same thing
Site Kit, a Google Tag Manager plugin, a pixel plugin and a WooCommerce marketing plugin can all add the same tags. Each sends its own copy with its own ID, so deduplication fails and sales get counted twice. Pick one source for each platform and switch the others off.
Theme, checkout and plugin updates
Moving to WooCommerce’s block-based cart and checkout, or swapping a checkout builder, changes how events fire. Tracking plugins have needed updates to keep add-to-cart events working with the newer checkout. Test after every theme, checkout or form change, and use our website redesign checklist to catch the other workflows that tend to break after launch.
How do you test your setup before trusting it?
- Place a real test order or form submission. Use a low-price hidden product and refund it afterward, so the Purchase event carries a real value.
- Check Google. Tag Assistant shows whether the Google tag and the conversion event fired. In Google Ads, the enhanced conversions diagnostics show whether customer data is arriving. For uploaded conversions, judge results with the “All conv. (by conv. time)” column.
- Check Meta. Open Test Events in Events Manager and confirm the Purchase arrives from both the browser and the server and is deduplicated. The Meta Pixel Helper browser extension shows what the Pixel sent.
- Check Event Match Quality a day later for your main events.
- Repeat the gap check every week, and again after any site change.
What should you watch out for?
Consent still applies
Server-side tracking is not a way around a visitor’s choice. If someone declines tracking, respect that on every route: pass the choice to Google through Consent Mode and to Meta through your consent setup. If you are still choosing a banner, our roundup of free WordPress GDPR plugins compares the main options. Confirm that the one you pick supports Consent Mode v2.
Double counting
Duplicate plugins, or the Pixel and the Conversions API without a shared event ID, can count one sale two or three times. Inflated numbers do as much harm as missing ones, because the platforms then optimize toward the wrong people.
Send only real conversions
Mark purchases, qualified leads and signups as conversions. Page views and button clicks are not conversions, and using them as primary goals teaches the platforms to find clickers instead of buyers.
Send the sale value
Include the value and currency with every purchase, so value-based bidding can look for customers who spend more.
Never send raw personal data
Hash emails and phone numbers before they leave your site (good plugins do this automatically), and never send sensitive details such as health information. Meta also restricts what some industries can share. If your site is classed as health and wellness or financial services, for example, Meta may block custom parameters, the parts of your URLs after the domain, or some standard events.
Own-domain routing is not a full fix
Some ad blockers also block tracking routed through your domain. Treat Google tag gateway as an improvement, not a guarantee.
The numbers will never match exactly
Meta, Google and your store count differently, use different attribution windows, and each platform credits its own ads. Aim for numbers that are close and stable, and compare them with real orders every week. For campaigns whose value hardly shows up in click-based reports, such as video and display, our guide to measuring upper-funnel impact covers lift tests and other ways to prove what they deliver.
Your conversion tracking checklist
- Run the gap check: paid orders against the events Meta received in Events Manager and purchases in GA4.
- Keep one source per platform for the Meta Pixel and the Google tag, with no duplicate plugins.
- Turn on enhanced conversions in Google Ads and automatic advanced matching in Meta.
- Add the Conversions API, with the same event name and event ID as the Pixel.
- Add Google tag gateway if you use Cloudflare, or server-side GTM if you advertise on several platforms.
- Upload offline sales if deals close after the first visit.
- Confirm that your consent banner sends Consent Mode v2 signals.
- Test with a real order, then repeat the gap check every week.
How this guide was checked
Platform details in this guide were checked against Google Ads Help, Meta for Developers, Cloudflare and Google Site Kit documentation in November 2026, and the article was reviewed by Ansh Agrawal. Google and Meta change these tools often, so if a screen in your account looks different from what we describe, the platform documentation linked above is the final word.
Server-side tracking, CAPI and enhanced conversions: quick answers
Yes. The browser tags pick up details your server cannot see on its own, such as the ad click ID, and the server fills the gaps the browser leaves. Meta recommends running the Pixel and the Conversions API together, and server-side Google Tag Manager still relies on a browser tag to collect the data it forwards. Use a shared event ID so each sale counts once.
The Meta Pixel runs in the visitor’s browser and reports what happens on the page. The Conversions API sends events from your server, store or CRM, so ad blockers and browser limits do not stop it, and it can also send sales that happen offline. Use both with a shared event ID, so Meta gets the browser’s details and the server’s reliability without counting a sale twice.
Two reasons. Ads Manager only counts purchases it credits to a Meta ad, while WooCommerce counts every order from every channel. And some purchase events never reach Meta at all, because of ad blockers, declined cookies or buyers who never return to the order-received page. Compare WooCommerce orders with the Purchase events received in Events Manager to tell the two apart, and add the Conversions API to close the second gap.
No. Site Kit’s plugin conversion tracking, formerly labeled enhanced conversion tracking, adds conversion events from supported plugins such as WooCommerce, WPForms and Contact Form 7. Google Ads enhanced conversions is a separate feature that sends hashed customer details to improve matching. You can use both, but turn on and check each one separately.
No. Moving collection to your server changes where the data travels, not what you are allowed to collect. If a visitor declines, respect that choice on the server route too, and keep passing Consent Mode signals to Google.
For most stores, yes. Meta for WooCommerce handles the Pixel and the Conversions API, Google for WooCommerce or Site Kit handles the Google tag, and Google tag gateway on Cloudflare takes a few clicks. You will want a developer or a hosted service for server-side Google Tag Manager, custom CRM uploads and unusual checkouts.
Not for new integrations. Since June 15, 2026, Google routes offline conversion imports and enhanced conversions for leads uploads through the Data Manager API, and existing Google Ads API integrations are being migrated. If you upload files or use a CRM connector in Google Ads Data Manager, your process stays the same.