Check whether consent and analytics tags work together

In Basic, tags wait for a decision. In Advanced, Google tags can send pings without cookies when the default is set to denied.

A one-size-fits-all “everything” agreement does not meet the requirements of the EDPB in many scenarios.

"Discard"/"Only Necessary" buttons cannot be hidden or made smaller in a manipulative manner.

GDPR requires that you can withdraw consent as easily as you can give it.

gtag consent default: ad_storage, analytics_storage, ad_user_data, ad_personalization → 'denied'.

You can use the region parameter in gtag and your own geographic rules in CMP. Set the scope in accordance with legal requirements and company policy.

The parameter is optional and gives the asynchronous CMP time to update the consent; 500 ms is an example, not a universal value.

url_passthrough can add advertising IDs to links; ads_data_redaction removes click IDs from Ads/Floodlight requests with denied ad_storage.

CMP category mapping → Consent Mode signals must include acceptance, refusal and subsequent withdrawal of consent.

Set default states as early as possible via a template using the GTM API; update them after the user's decision.

Google tags have built-in consent checks. An additional block may be needed for other tags or Basic mode, but in Advanced it should not accidentally block pings.

Without ad_storage/ad_user_data granted, advertising data should be limited.

List providers (Google, Piwik) and processing purposes.

Runbook dla marketingu i IT - kto zmienia co przy nowym tagu.

Np. event consent_update z obiektem stanów - ułatwia audyt w Preview.