1. Home
  2. /
  3. Resources
  4. /
  5. Conversion tracking and consent: how opt-outs should reach ad platforms
Article

Conversion tracking and consent: how opt-outs should reach ad platforms

Omar Al Shoubaki
Omar Al Shoubaki
Journify
October 20, 2026 5 min read
Share
Conversion tracking and consent: how opt-outs should reach ad platforms

Ad platforms find your next customer by learning from your current ones. Every click, visit, add to cart, phone call, store visit, and purchase is a lesson. The lessons that should reach the platform are the ones your customers agreed to share.

Conversion tracking with consent means sending conversion data to Meta, Google, TikTok, Snap, and Amazon only for shoppers who allowed it, and only in the form each platform needs. Hashing is part of that: it keeps the raw email or phone number from being shared. Consent decides whether anything should be sent at all.

Consent-based conversion tracking is the practice of respecting each shopper's consent choice before any conversion event or identifier leaves your systems, then sending only the fields required for matching, in hashed form. It covers every path a conversion can take: the browser pixel, server-side events, and orders confirmed later in a backend or CRM. A setup respects consent when the shopper's choice controls what reaches the platform on every one of those paths. Hashing alone doesn't get you there.

What hashing protects, and what it doesn't

Before an email address or phone number is sent through a Conversions API, it's normalized and hashed, usually with SHA-256. The platform receives the hashed value instead of the raw email or phone number. Our Conversions API field reference covers what each platform requires and how it's hashed.

What hashing doesn't do is make the data anonymous. Matching works because the platform hashes its own users' emails and phone numbers the same way, then compares the results. If your hashed email matches theirs, the platform knows exactly who the shopper is. That's the point of sending it.

So hashing changes how an identifier is shared. It doesn't decide whether you're allowed to share it.

Moving tracking server-side doesn't change what the shopper agreed to

Server-side tracking sends events from your server instead of the shopper's browser, so ad blockers and browser restrictions don't drop them. That makes tracking more reliable. The shopper's consent still applies.

A shopper who declined ad tracking on your cookie banner declined it for your brand, wherever the code runs. If the browser pixel respects that choice but the server keeps sending the same shopper's contact details, the setup has only moved the tracking somewhere less visible. Server-to-server tracking explained covers how the server path works. The consent rules on that path should be the same ones the browser follows.

How opt-outs should flow through to ad platforms

The shopper's choice starts in your consent management platform, the banner or preference center that records what they agreed to. From there, it needs to travel with every event:

1. Read the consent state before sending. Each event, browser or server, should carry the consent state recorded for that shopper at that moment.

2. Hold back what wasn't allowed. If a shopper opted out of ad tracking, their contact details shouldn't reach ad platforms. Your brand's policy decides whether anything is sent for that shopper at all.

3. Pass the state along where platforms accept it. Google's Consent Mode carries the banner's choice with Google tags. Server-side uploads to Google through the Data Manager API carry two consent fields, ad_user_data and ad_personalization, which Google has required for users in the EEA since March 2024. Meta's Conversions API accepts a Limited Data Use flag for shoppers in US states whose privacy laws give them the right to opt out.

PlatformPathWhere the consent choice goes
GoogleTags on your siteConsent Mode: ad_storage, ad_user_data, ad_personalization
GoogleServer-side uploads (Data Manager API)Consent fields ad_user_data and ad_personalization, required for EEA users
MetaPixel and Conversions APIdata_processing_options set to LDU (Limited Data Use) for US state privacy laws

4. Apply it to orders confirmed later. Cash-on-delivery orders, phone orders, and CRM updates are sent from a backend days after the visit. The consent recorded at checkout has to stay with the order record so the backend respects it too.

That fourth step is where setups most often slip. The browser respects the banner, then a backend integration sends every order with full contact details, because nobody connected the consent record to the order.

For shoppers who opted out, yes: the platform receives fewer identifiers for them, or none at all. That's the correct outcome, because those shoppers made a choice.

The way to protect match rate is to improve what you send for shoppers who did consent: complete, correctly formatted email and phone, plus click IDs carried through to the purchase. How to improve your Meta match rate covers what to check. Ignoring opt-outs to recover match rate trades a reporting gain for a trust problem.

Journify reads each shopper's consent state and applies it to every event before it's sent to Meta, Google, TikTok, Snap, and Amazon through official Conversion APIs, whether the event comes from the browser, your server, or your backend. The same choice holds on every path.

FAQ

Is hashed data anonymous?

No. Platforms match hashed emails and phone numbers to their own users, so a hashed identifier still points to a specific person. Hashing keeps the raw value from being shared.

Does server-side tracking need the same consent as the pixel?

It should follow the same consent choices, because the shopper's choice applies to your brand wherever the code runs. Confirm the specifics with your legal team.

Do offline and backend orders need to respect consent?

Yes. The consent recorded at checkout should travel with the order, so events sent later from a CRM or order system follow the same choice.

Does Google Consent Mode replace a consent banner?

No. Consent Mode passes along the choice your banner collects. You still need the banner or preference center to ask the shopper.

What is Meta's Limited Data Use flag?

It's a data processing option you send with Pixel or Conversions API events (data_processing_options set to LDU). For people in US states where it applies, Meta limits how it uses that data, to support compliance with state privacy laws.

Complete signal means sending everything shoppers agreed to share, on every path, and sending it well.

Book a call to check how consent flows through your signal today.

Omar Al Shoubaki
Omar Al Shoubaki
Journify

Omar AlShoubaki is Chief Revenue Officer at Journify. He has spent his career in digital and data businesses across the GCC and US, working closely with performance marketing teams at brands across retail, finance, and consumer. At Journify, he focuses on making sure every brand on the platform sees results they can measure and defend.

You might also find this useful

More from the Article series.