Tracking without third‑party cookies: pixel, Conversions API and GA4 done right

Privacy changes in browsers and phones have made measurement harder. Safari and Firefox block third‑party cookies, iOS asks permission to track across apps, and more and more people use ad blockers. The result: many ad accounts today "see" only part of the sales they generate.

That affects two things: your decisions (you turn off campaigns that do sell or keep others that don't) and the algorithm's ability to optimize, because Meta and Google learn from the conversions they receive. The good news is that with the right setup you can recover much of that visibility. This is the order I work in.

1. Define what you want to measure

Before installing anything, list the actions that matter to your business:

• Purchases (with value and currency).
• Submitted forms.
• WhatsApp clicks or calls.
• Booked appointments.
• Intermediate steps: view product, add to cart, start checkout.

If it isn't on the list, don't install it. Fewer well‑built events beat many confusing ones.

A measurement plan in one table

Writing it down keeps everyone who touches the account from installing different things:

Action	Meta event	GA4 event	Primary conversion?
Purchase	Purchase	purchase	Yes
Quote form	Lead	generate_lead	Yes
WhatsApp click	Contact	whatsapp_click (custom)	Secondary
Add to cart	AddToCart	add_to_cart	No

Use standard names whenever they exist. Platforms understand them better and reports come out cleaner.

If your business closes offline

Many businesses in Puerto Rico sell over WhatsApp, by phone or in person after a first online contact. In those cases, the button click isn't the sale. If you use a CRM, you can send the sales that close later back to Meta and Google (offline conversions), so the platforms learn which contacts actually become customers.

2. Pixel + Conversions API on Meta

The pixel measures from the browser; the Conversions API sends events from the server or your store platform. Using both together makes measurement more complete and more resistant to blocking.

Key points:

• Send the same event through both channels with an event ID so Meta doesn't count it twice.
• Share customer data securely (email, phone; sent hashed) to improve matching.
• Check match quality and deduplication in Events Manager, and fix the errors that show up in diagnostics.
• Verify your domain in Business Manager.

Many e‑commerce platforms offer official integrations that set this up for you. Use them when available: they're usually more stable than a hand‑built install.

3. Google: GA4, enhanced conversions and Google Ads

Google Analytics 4 measures with events. To make it useful:

• Mark only the conversions that matter as key events.
• Connect GA4 with Google Ads and Search Console.
• Turn on enhanced conversions in Google Ads, which use hashed customer data to recover conversions that would otherwise be lost.
• Set data retention to the maximum available and exclude your team's internal traffic.
• Use consistent UTM parameters on all your campaign, email and social links so you know where each visit comes from.

Rules for your UTMs

• Always lowercase: "facebook" and "Facebook" show up as two different sources.
• One written, shared convention: for example, utm_source=newsletter, utm_medium=email, utm_campaign=campaign-name-month.
• Tag your WhatsApp links, Instagram bio and printed QR codes too. Without that, all that traffic gets lost as "direct."

What about server‑side tagging?

For businesses with volume, a server‑side Google Tag Manager container gives more control over what data leaves your site and makes measurement more resilient. It costs money and needs maintenance. For most small businesses, well‑configured official integrations are enough to start.

4. Consent and privacy

Show a clear cookie notice where required and respect the user's choice. Google's and Meta's tools have consent modes that allow aggregate or modeled measurement while respecting privacy. If you sell to people in other places, such as Europe or certain U.S. states, the requirements can be stricter.

Also keep a published privacy policy on your website that explains what data you collect and why. It's not just a requirement: it builds trust with someone about to give you their information.

5. Test before you trust

An install nobody tested is a broken install until proven otherwise. Before launching campaigns:

1. Make a test purchase or submit a test form yourself.
2. Check in Meta's Events Manager that the event arrived through both browser and server and was deduplicated.
3. Check in GA4's DebugView that the event shows up with its parameters (value, currency, transaction ID).
4. Confirm Google Ads records the conversion.
5. Repeat the test on a phone and in another browser.

6. Compare against reality

No platform is the absolute truth. Each attributes sales its own way, with different windows and models, so the sum of what they report almost never matches your bank account. So:

• Every month, compare the sales platforms report with your business's real sales.
• Use MER (total revenue ÷ total marketing spend) as a control metric. If MER stays healthy while you scale, you're on track even if each platform says something different.
• If you can, ask customers how they found you, on the form or at the register. It's simple and revealing.

Rule of thumb: use each platform's data to optimize within that platform, and your real numbers to decide how much to invest overall.

Signs your tracking is broken

• Platforms report far more sales than you actually had (duplicate events).
• Or far fewer (events that don't fire).
• Purchase values show up as zero or in the wrong currency.
• A large share of your traffic appears as "direct" or "unassigned."
• A purchase gets recorded every time someone reloads the confirmation page.
• You don't know which channel your customers come from.

Common mistakes

• Installing the pixel twice: once by hand and again through the store integration.
• Counting WhatsApp button clicks as sales and optimizing campaigns for them without checking whether those contacts buy.
• Changing the website without checking tracking. A redesign or theme change can break events without anyone noticing.
• Not owning your access. Ad accounts, the pixel and GA4 should be in your business's name, not an agency's or an employee's.

FAQ

Do I need the Conversions API if I already have the pixel?

Yes, if you invest in Meta consistently. The pixel alone loses events to blocking and browser restrictions; the API sends those events from the server and gives the algorithm more signals.

Why do GA4 and Meta report different numbers?

Because they use different attribution models, windows and ways of counting. Meta may credit itself for a sale after an ad view; GA4 often gives credit to another channel. Neither is "wrong": they answer different questions.

How often should I review my tracking?

Do a quick check every month when you compare against real sales, and a full test every time you change something on your website, your store or your checkout.

Can I set it up myself?

With official integrations and patience, many parts, yes. Where I see the most errors is deduplication, offline conversions and consent. If your ad spend is significant, it's worth having someone experienced audit it.

Bottom line

Reliable measurement isn't a technical luxury: it's the basis of every marketing decision. Define your events, combine pixel and Conversions API, configure GA4 and Google Ads deliberately, respect privacy, test everything and always compare with your real numbers.

Share: LinkedIn · Facebook · X · WhatsApp

← Back to blog