← Back to Blog

4 Consent Signals Your WordPress Site Must Send for Google Ads Conversions

Quick Answer: WordPress sites must send four Consent Mode v2 signals to Google Ads: analytics_storage, ad_storage, ad_user_data, and ad_personalization (Didomi, 2026). Since June 15, 2026, ad_storage alone governs advertising data in your Google Ads account. Most WordPress consent plugins only map two of the four parameters — sites with incomplete signals saw 40–60% audience drops (Plainly, 2026). Here’s what each signal controls and how to verify yours are firing correctly.

WordPress sites must send four distinct consent parameters to maintain Google Ads conversion tracking: analytics_storage, ad_storage, ad_user_data, and ad_personalization (Didomi, 2026). Each parameter controls a different slice of what data Google can collect and how it can use it.

Before June 2026, most WordPress stores could get by with two — analytics_storage for GA4, ad_storage for ads. That’s no longer enough. Google’s Consent Mode v2 enforcement now requires all four signals to fire on every page load, and each one gates a specific advertising function. Miss one, and a whole category of conversion data goes dark without a single warning in your dashboard.

WordPress sites must send 4 distinct consent parameters — analytics_storage, ad_storage, ad_user_data, and ad_personalization — to maintain Google Ads conversion data (Didomi, 2026).

Here’s the thing: these aren’t optional upgrades. They’re the minimum your consent management platform must map for Google to count your conversions accurately. The table below breaks down what each one does.

ParameterControlsWhat breaks when denied
analytics_storageGA4 cookies and measurementGA4 stops collecting user-level data
ad_storageAdvertising cookies (sole ad data control since June 2026)Google Ads receives no cookie-based conversion data
ad_user_dataUser data sent to Google for advertisingEnhanced Conversions and Customer Match stop working
ad_personalizationData used for ad personalisationRemarketing audiences from GA4 can’t be used for targeting

ad_storage controls whether advertising cookies can be set and read on the visitor’s browser — and since June 15, 2026, it is the sole parameter governing what advertising data reaches your Google Ads account (OneTrust, 2026). Before June, GA4 could pass conversion signals to linked Ads accounts on its own. That bridge is gone.

Translation: if ad_storage is denied, Google Ads gets nothing from that visitor. No click conversion, no view-through, no audience signal. The visitor bought your product, your payment processor recorded it, but your ad platform doesn’t know it happened. Smart Bidding keeps optimising in the dark.

This is the parameter most WordPress consent plugins already handle. The problem isn’t ad_storage itself — it’s that store owners assume this one parameter is enough, when three more now sit behind it.

Related: Consent Mode v2 Deadline June 2026: What Happens to Your Google Ads Data When GA4 Leaves the Loop

What does ad_user_data control?

ad_user_data controls whether user-level data such as email addresses and phone numbers can be sent to Google for advertising purposes — this is the signal that gates Enhanced Conversions and Customer Match uploads (Didomi, 2026). Without it granted, Google can’t receive the hashed first-party data that powers its highest-quality conversion matching.

Enhanced Conversions work by matching a hashed email or phone number against Google’s signed-in user base. It’s the best weapon WordPress stores have against cookie loss. But when ad_user_data defaults to denied — which it does in most consent plugin configurations — that entire matching pipeline shuts down silently.

The commercial impact is real. A WooCommerce store running Google Ads without ad_user_data consent is relying entirely on cookie-based attribution. Cookies are already degraded by Safari ITP, Firefox tracking protection, and ad blockers. Take away Enhanced Conversions on top of that, and the gap between actual revenue and reported revenue keeps widening.

What does ad_personalization control?

ad_personalization controls whether collected data can be used to personalise ads shown to the visitor — it will become the exclusive control for personalised ad targeting via linked Analytics accounts (Didomi, 2026). When this signal is denied, remarketing audiences built from GA4 data can’t be used for personalised targeting in Google Ads.

This is the parameter most stores don’t even know exists. It governs whether the audiences you build in GA4 — purchasers, cart abandoners, high-value segments — can flow into Google Ads for remarketing. Without it, your audience lists exist in GA4 but sit locked away from your ad campaigns.

The question isn’t whether personalisation matters. The question is whether your consent plugin even sends this signal. For most WordPress sites, it doesn’t.

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

Most WordPress consent plugins only map consent choices to analytics_storage and ad_storage — ad_user_data and ad_personalization are frequently either missing or defaulting to denied (Didomi, 2026), which silently blocks Enhanced Conversions and remarketing personalisation without any warning in your Google Ads dashboard.

The typical WordPress consent plugin was built for GDPR cookie consent — a binary “accept cookies or don’t” model. Consent Mode v2’s four-parameter architecture requires a more granular mapping: the visitor’s consent choice needs to fan out into four separate signals, each one controlling a different Google function.

Some plugins have updated. CookieYes, Complianz, and a few others now expose all four parameters in their settings. But the default configurations still ship with ad_user_data and ad_personalization either unmapped or set to denied. If you installed your consent plugin before June 2026 and haven’t touched the Consent Mode settings since, you’re almost certainly sending only two of the four.

Most WordPress consent plugins map only 2 of 4 required signals, silently blocking Enhanced Conversions and remarketing personalisation (Didomi, 2026).

Open Chrome DevTools, go to the Network tab, filter for collect requests to Google, and inspect the GCS parameter — it encodes the consent state for all four parameters as a string of characters that map to granted or denied (Google Ads Help, 2026).

Here’s how to read it. The GCS parameter appears on every measurement hit your site sends to Google. It’s a compact string where each character position represents one of the four consent states. A character value of 1 generally means granted; other values mean denied or not set. If you see fewer than four positions populated, your consent plugin isn’t mapping all the parameters.

For a quicker check, use Google Tag Assistant. Load your page, open Tag Assistant, accept the consent banner, and look at the consent state readout. It should show all four parameters with their current values. If ad_user_data or ad_personalization shows “not set” or “denied” after a visitor accepts your banner, your plugin configuration has a gap.

The fix is usually in your consent plugin’s settings under the Google Consent Mode integration. You need to map your “marketing” or “advertising” consent category to all three ad parameters — ad_storage, ad_user_data, and ad_personalization — not just ad_storage alone.

Related: The June 15 Consent Mode Cutover Silently Broke Your Google Ads Data — Here’s How to Tell

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 !

When ad_user_data consent is absent or denied, Enhanced Conversions can’t send hashed user data to Google — conversion matching falls back to cookie-based attribution, which is already degraded by browser restrictions. The result is a growing gap between your actual sales and what Google Ads reports.

Think about what this means in practice. A customer clicks your Google Ad, lands on your WooCommerce store, browses for a day, comes back on Safari (which wipes the click cookie after 7 days via ITP), and buys. Without Enhanced Conversions, Google never sees that purchase. With ad_user_data granted and Enhanced Conversions active, Google matches the hashed email from checkout against its user base and attributes the sale. That’s the difference.

The irony is that most store owners have Enhanced Conversions turned on in their Google Ads settings. They’ve done the technical work. But the consent layer underneath is blocking the data from ever reaching Google, and nothing in the Google Ads interface tells them it’s happening.

Sites with incomplete consent signal configurations saw audience and conversion drops of 40–60% after the June 2026 enforcement (Plainly, 2026). Google silently falls back to modeled data rather than alerting the site owner, so many stores don’t realise the drop until they reconcile against actual revenue.

Let that sink in. A 40–60% drop in reported conversions doesn’t mean your revenue dropped — it means your ad platform no longer knows about those conversions. Smart Bidding is now optimising on half the signal it had before. Your cost per acquisition climbs, your ROAS reporting looks wrong, and your next budget decision is built on incomplete numbers.

The fix doesn’t require a new consent plugin or a complete technical overhaul. For most WordPress stores, it’s a configuration change: open your consent plugin settings, find the Consent Mode integration, and verify that your advertising consent category maps to ad_storage, ad_user_data, and ad_personalization — all three, not just the first. Then validate with the GCS check above.

For stores using server-side tracking, the picture gets simpler. Transmute Engine routes events server-side and ensures all four consent signals are correctly forwarded to Google regardless of which client-side consent plugin is installed. The consent state travels with the event payload, so nothing is lost to a misconfigured CMP mapping. It doesn’t replace your consent plugin — it makes sure the signals your plugin collects actually reach Google intact.

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

  • 4 signals, not 2: WordPress sites must send analytics_storage, ad_storage, ad_user_data, and ad_personalization for complete Google Ads conversion tracking.
  • ad_storage is now sole gatekeeper: since June 15, 2026, it’s the only parameter that controls whether advertising data reaches Google Ads.
  • Most consent plugins miss half the signals: ad_user_data and ad_personalization are typically unmapped or defaulting to denied in standard WordPress consent plugin configurations.
  • 40–60% data drops are real: sites with incomplete signals saw audience and conversion drops of this magnitude after the June 2026 enforcement.
  • The fix is configuration, not code: map your advertising consent category to all three ad parameters in your consent plugin’s Consent Mode settings, then verify with the GCS check.
What are the 4 consent signals WordPress sites must send for Google Ads?

WordPress sites must send analytics_storage (controls GA4 cookies), ad_storage (controls advertising cookies), ad_user_data (controls whether user data can be sent to Google for advertising), and ad_personalization (controls whether data can be used for ad personalisation). All four must be mapped in your consent management platform and fired correctly on every page load.

What does ad_storage control in Consent Mode v2?

ad_storage controls whether advertising cookies can be set and read on the visitor’s browser. Since June 15, 2026, it is the sole parameter governing what advertising data reaches your Google Ads account. When denied, Google Ads receives no cookie-based conversion or audience data from that visitor.

What does ad_user_data control?

ad_user_data controls whether user-level data such as email addresses and phone numbers can be sent to Google for advertising purposes. This is the signal that gates Enhanced Conversions and Customer Match uploads. Without it granted, conversion matching falls back to cookie-based attribution only.

What does ad_personalization control?

ad_personalization controls whether collected data can be used to personalise ads shown to the visitor. It is becoming the exclusive control over personalising linked Ads accounts with Analytics data. When denied, remarketing audiences built from GA4 data cannot be used for personalised targeting.

Do most WordPress consent plugins support all four signals?

Most WordPress consent plugins only map consent choices to analytics_storage and ad_storage. The ad_user_data and ad_personalization parameters are frequently either missing or defaulting to denied, which silently blocks Enhanced Conversions and remarketing personalisation without any warning in your Google Ads dashboard.

How do you check which consent signals your WordPress site sends?

Open Chrome DevTools, go to the Network tab, filter for collect requests to Google, and inspect the GCS parameter. It encodes the consent state for all four parameters as a string of characters that map to granted or denied. You can also use Google Tag Assistant to verify consent state in real time.

What happens when ad_user_data consent is missing?

When ad_user_data consent is absent or denied, Enhanced Conversions cannot send hashed user data to Google. Conversion matching falls back to cookie-based attribution, which is already degraded by browser restrictions like Safari ITP and ad blockers. The result is a widening gap between actual conversions and what Google Ads reports.

How much conversion data can you lose from incomplete consent signals?

Sites with incomplete consent signal configurations observed audience and conversion drops of 40–60% after the June 2026 enforcement. Google silently falls back to modeled data rather than alerting the site owner, so many stores don’t realise the drop until they reconcile against actual revenue.

References

  1. Didomi (2026). Google Consent Mode 2026 Changes. Source
  2. OneTrust (2026). What Google’s June 2026 Consent Mode Changes Mean for Google Ads. Source
  3. Plainly (2026). What’s New in GA4 2026. Source
  4. Google Ads Help (2026). Consent Mode Overview. Source