Troubleshooting

Use symptoms, observations and targeted fixes rather than assumptions.

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.

Check the published page source for the correct public ID and one loader. Inspect blocked script requests, CSP violations, caches, stored choices and excluded routes. A returning visitor with an unexpired choice may not see automatic UI.

Duplicate or conflicting banners

Inspect theme/header plugins, GTM, the official WordPress plugin and native builder banners. Choose one installation owner. Two UIs can issue conflicting signals.

Unexpected tracking

Check immediate defaults and each tag's consent requirements. Determine Basic versus Advanced mode before labelling every denied Google request a failure. A cookie category does not automatically block an unrelated script.

Language or design differs

Review browser language, configured fallback, customised text, RTL, mobile settings, published versus draft configuration and cached assets. Do not “fix” this with undocumented global CSS overrides.

Events missing

Confirm the selected website, period/timezone, actual banner display, exclusions and event requests. Blocked requests or uncovered periods are not proof of no visitors. Do not use consent-log deletion or traffic-reset shortcuts.

Provide useful support evidence

Send the URL, platform/version, time, selected method, expected result and redacted console/network observations. Never include API keys, cookies, raw CSV records or unredacted visitor identifiers.

Follow the targeted GTM, preferences or hosting guide for the relevant failure; fix observed causes and rerun verification.

Related articles

Still need help?

Contact the ConsentEase team and include the website and steps you tried.