GA4. Ads personalization toggle. Align reporting with EEA policy.

What this means for your store

Since March 2024, GA4 properties serving EEA, UK, or Swiss users must respect ads personalization choices. The Admin Ads personalization setting defines whether GA4 may use data for personalized advertising when consent is ambiguous. It works with Consent Mode's ad_personalization flag - Admin is the property-level backstop; the CMP signal is per user.

Scenario on a real storefront

Marketplace EU sells across 12 countries and runs OneTrust. Set the property default and confirm consent signals reach GA4 before exporting remarketing lists:

# GA4 Admin
Admin → Data settings → Data collection → Ads personalization
→ Choose behavior for EEA users:
   "Allow ads personalization" only when ad_personalization = granted
   (recommended for most EU ecommerce)

# CMP must send Consent Mode v2
gtag('consent', 'update', {
  ad_personalization: marketingConsent ? 'granted' : 'denied',
  ad_user_data: marketingConsent ? 'granted' : 'denied',
});

# Tag Assistant → Consent tab → confirm ad_personalization state
# Google Ads → Audience manager → check EU user list health

What to do next

• Align legal, CMP, and analytics on one consent taxonomy - mismatched labels break the toggle.
• If remarketing lists shrink in the EEA, check denied ad_personalization before blaming tagging.
• US-only properties can keep defaults, but global storefronts should set EEA rules explicitly.

Bottom line

The ads personalization Admin setting is the property-level guardrail for EEA remarketing. Pair it with Consent Mode v2 from your CMP. One without the other leaves gaps.