← Back to Blog

Consent Mode v2 and the Data Manager API: The Signals You Must Pass

Quick Answer: Every first-party data upload to Google Ads must now carry 2 consent mode v2 parameters — ad_user_data and ad_personalization — or EEA user data becomes unusable for measurement and personalisation (Tag Manager Help, 2026). These signals were added in November 2023 alongside the original ad_storage and analytics_storage, bringing the total to 4 core consent parameters your setup must define. Consent doesn’t stop at the banner — it must travel with every server-side upload, or the data you collected with permission arrives without proof.

For EEA users you must pass both ad_user_data and ad_personalization, the 2 parameters added in consent mode v2 (Tag Manager Help, 2026). Without these signals on the upload itself, Google Ads treats the data as if consent was never obtained — making it unusable for measurement or personalisation, regardless of what the visitor actually clicked on your cookie banner.

This is the gap most WooCommerce stores miss. You captured consent in the browser. You stored it somewhere. But when your server-side event or your Data Manager upload fires, it doesn’t carry that consent state with it. The data arrives at Google without proof, and Google treats no proof as no consent.

The fix is mechanical: your upload payload must include the consent fields, populated from the state you captured at interaction time. The banner isn’t enough — it’s the starting point, not the finish line.

For EEA users you must pass both ad_user_data and ad_personalization — the 2 consent mode v2 parameters — with every first-party data upload (Tag Manager Help, 2026).

Consent mode was updated in November 2023 to add ad_user_data and ad_personalization on top of ad_storage and analytics_storage (Google for Developers, 2026). These aren’t new requirements imposed overnight — they’ve been in the spec since late 2023, but enforcement on uploads tightened through 2025 and 2026 as Google rolled out the Data Manager API and shut down legacy conversion import paths.

The original consent mode (v1) had two parameters: ad_storage and analytics_storage. They controlled whether cookies were written and whether analytics data was collected. V2 added two more — ad_user_data and ad_personalization — specifically to govern what happens with first-party data after collection. One controls whether your data can be used for measurement; the other controls whether it can be used for ads personalisation.

Your consent defaults should set all 4 parameters: ad_storage, ad_user_data, ad_personalization, and analytics_storage (Google for Developers, 2026). Missing any one creates a gap — the parameter defaults to denied when absent, which silently reduces what Google can do with your data.

Here’s the thing… Most consent management platforms (CMPs) set ad_storage and analytics_storage correctly but handle the v2 parameters inconsistently. Some map them to the same toggle as ad_storage; others leave them undefined. An undefined parameter is a denied parameter, and a denied ad_user_data means your enhanced conversions, your Customer Match uploads, and your offline conversion imports all arrive at Google as if consent was refused — even when the visitor granted it.

ParameterVersionControlsWhen denied
ad_storagev1Advertising cookiesNo new cookies; cookieless pings sent
analytics_storagev1Analytics cookiesNo analytics cookies; modelled data only
ad_user_datav2First-party data for measurementUploaded data unusable for enhanced conversions
ad_personalizationv2First-party data for ads personalisationCustomer Match and remarketing blocked

Related: Why Google Consent Mode v2 Is Now the Single Point of Failure for Your Google Ads Data

If you don’t send consent signals you lose ads personalisation capabilities, and uploaded data may not be usable (Google Ads Help, 2026). For EEA traffic this means enhanced conversions, Customer Match, and store sales data all become inert — collected but not actionable. The data sits in your account, technically present, functionally useless.

The failure mode is silent. No error message, no warning banner. Your upload succeeds, your conversion actions show as configured, but the match rate drops to zero for EEA users because Google can’t use the data without the consent signal. You see fewer conversions in your reports and assume the campaigns underperformed — when the real problem was a missing field in your upload payload.

Your consent defaults should set all 4 parameters: ad_storage, ad_user_data, ad_personalization, and analytics_storage — a missing parameter defaults to denied (Google for Developers, 2026).

Which signal controls whether uploaded first-party data can be used?

The ad_user_data signal, 1 of the 2 consent mode v2 parameters, is required for measurement use cases such as enhanced conversions and tag-based conversion tracking (Google Ads Help, 2026). It’s the gate: granted means your uploaded data is usable for matching conversions back to ad clicks; denied means the data is stored but can’t be matched.

Think of ad_user_data as the measurement signal and ad_personalization as the targeting signal. For conversion tracking, ad_user_data is the one that matters — without it, your enhanced conversions can’t match the hashed email or phone to a click ID. For Customer Match and remarketing, both signals must be granted.

Yes — store sales and Customer Match data from EEA users is only usable when both ad_user_data and ad_personalization are granted (Google Ads Help, 2026). Denied on either signal makes the entire audience segment unusable for that user, even if the data itself was collected legally under your privacy basis.

This is where the consent chain becomes critical for WooCommerce stores running Customer Match audiences. You might have a perfectly legal basis for collecting and storing customer email addresses. But if the consent signal wasn’t granted at the moment of interaction — and carried through to the upload — Google can’t use that record for audience matching. Legal collection and usable collection are now different things.

Related: How much conversion data does Consent Mode V2 lose when visitors decline?

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Let's Do It !

Because the offline upload itself carries a consent field, and failing to populate it may result in conversions that are not attributable (Google Ads Help, 2026). The banner captures consent at the moment of interaction; the upload must carry proof of that consent to the destination. Two separate events, two separate signals.

The architectural gap in most WooCommerce setups: the consent management platform fires in the browser, sets a cookie or a localStorage flag, and the banner goes away. Then the server-side event fires from your server — where there is no cookie, no localStorage, and no browser. Unless your server-side pipeline explicitly reads the consent state and includes it in the upload payload, the consent signal never reaches Google.

For WooCommerce stores running Transmute Engine, the server-side pipeline forwards the consent state with each event — so consented data arrives at Google Ads with proof attached and denied data is withheld at the source. That’s the gap this architecture closes: consent travels with the data, not beside it.

What does denied ad_storage change about collection?

With ad_storage denied, no new advertising cookies are written and tags send cookieless pings so Google can still model conversions (Google for Developers, 2026). You still get modelled data — it’s not a blackout — but the match rate drops because there’s no cookie to link the visit to a later conversion.

The cookieless pings are Google’s conversion modelling input. They give the system enough signal to estimate what happened, even without a deterministic match. It’s better than nothing, and significantly better than the alternative of losing the visitor entirely. But it’s a statistical estimate, not a measured conversion — and the accuracy depends on how much consented data you’re feeding the model from elsewhere in your pipeline.

Related: You Set Up Consent Mode v2 — Now Where Did Half Your Data Go?

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Start NOW !

Key Takeaways

  • 2 signals on every upload: EEA first-party data uploads must carry ad_user_data and ad_personalization or the data is treated as if consent was denied.
  • 4 parameters total: Your consent defaults must set ad_storage, analytics_storage, ad_user_data, and ad_personalization — a missing parameter defaults to denied.
  • Consent travels with data: The banner captures consent; the server-side upload must carry it — two separate events requiring two separate signals.
  • Silent failure mode: Missing consent signals don’t error — uploads succeed but data becomes unusable, silently reducing your reported conversions.
  • ad_user_data gates measurement: Without it, enhanced conversions and offline imports can’t match back to ad clicks.
  • Both signals needed for audiences: Customer Match and store sales data require both ad_user_data and ad_personalization granted.
Which consent signals must I send with first-party data uploads?

For EEA users you must pass both ad_user_data and ad_personalization, the 2 parameters added in consent mode v2. Without these signals on the upload itself, Google Ads treats the data as if consent was never obtained — making it unusable for measurement or personalisation.

When were these two consent parameters introduced?

Consent mode was updated in November 2023 to add ad_user_data and ad_personalization on top of ad_storage and analytics_storage. These aren’t new requirements — they’ve been in the spec since late 2023, but enforcement on uploads tightened through 2025 and 2026.

How many core consent parameters should my setup define?

Your consent defaults should set all 4 parameters: ad_storage, ad_user_data, ad_personalization, and analytics_storage. Missing any one creates a gap — the parameter defaults to denied when absent, which silently reduces what Google can do with your data.

What happens if I don’t send consent signals?

If you don’t send consent signals you lose ads personalisation capabilities, and uploaded data may not be usable. For EEA traffic this means enhanced conversions, Customer Match, and store sales data all become inert — collected but not actionable.

Which signal controls whether uploaded first-party data can be used?

The ad_user_data signal, 1 of the 2 consent mode v2 parameters, is required for measurement use cases such as enhanced conversions and tag-based conversion tracking. It’s the gate: granted means your uploaded data is usable; denied means it’s stored but can’t be matched.

Does denied consent block Customer Match uploads?

Yes — store sales and Customer Match data from EEA users is only usable when both ad_user_data and ad_personalization are granted. Denied on either signal makes the entire audience segment unusable for that user, even if the data itself was collected legally.

Why does consent belong on the upload, not just the banner?

Because the offline upload itself carries a consent field, and failing to populate it may result in conversions that are not attributable. The banner captures consent at the moment of interaction; the upload must carry proof of that consent to the destination.

What does denied ad_storage change about collection?

With ad_storage denied, no new advertising cookies are written and tags send cookieless pings so Google can still model conversions. You still get modelled data — it’s not a blackout — but the match rate drops because there’s no cookie to link the visit to a later conversion.

References

  1. Tag Manager Help (2026). Updates to consent mode for EEA traffic. Source
  2. Google for Developers (2026). Set up consent mode on websites. Source
  3. Google Ads Help (2026). Obtain user consent. Source
  4. Google Ads Help (2026). Consent mode reference. Source
  5. Google Ads Help (2026). Upgrade offline conversion import to enhanced conversions for leads. Source
  6. Google for Developers (2026). Consent mode overview. Source