Tag Behaviour & Cookie Cleanup
Separate consent signals, tag enforcement and reachable cookie removal.
Content and code last checked 2026-10-06 by ConsentEase product documentation. This is a review of the written content and code, not a test on a live third-party platform.
Four different mechanisms
- Inventory: describes cookies/providers.
- Signals: communicate visitor choices to integrations.
- Tag configuration: determines which scripts fire or what they send.
- Cleanup: attempts to remove reachable disallowed first-party cookies.
Configure every optional tag
Use supported provider consent APIs or GTM consent checks. Google built-in consent behaviour differs from arbitrary third-party tags. Additional consent requirements may be necessary for non-Google tags; merely selecting a category in ConsentEase does not enforce that requirement.
Cleanup limits
ConsentEase uses category metadata and JavaScript-visible cookies for best-effort cleanup after denial/withdrawal. It cannot access HttpOnly cookies, arbitrary third-party cookies or every path/domain variation. Browser restrictions also affect what is reachable.
Cleanup preserves granted categories and depends on the real inventory loading. A missing metadata response must not be treated as a known inventory or silently change the visitor's choices.
Do not confuse removal with prevention
Deleting a cookie does not undo a request already sent, provider-side storage or data processing. Conversely, Advanced Consent Mode can send cookieless requests with storage denied. Verify expected future processing separately.
Keep tag settings, notices and inventory consistent, and rerun checks when adding providers.