Troubleshooting
Common issues and how to resolve them. If you don't find your answer here, contact support.
Banner doesn't appear
Script not installed
Make sure the LiteConsent script tag is present in the <head> of every page. Check the Installation tab in your site settings for the correct snippet.
Wrong site key
Check that the site ID in your c.js URL (/s/YOUR_SITE_ID/c.js) matches the public ID shown in the dashboard.
Banner not activated
New sites start inactive. Go to the General tab and toggle the banner to "Active".
Domain mismatch
The domain in your site settings must match the domain where the script runs. If you're testing on localhost, add it as an allowed domain or use the debug mode.
Jurisdiction filtering
If your banner is set to show only in specific jurisdictions (e.g., "EU & UK only"), it won't appear for visitors outside those regions. Check the General tab for your visibility scope and fallback behavior settings.
Banner appears but scripts still run
Scripts not tagged
LiteConsent can only block scripts it knows about. If you're using markup mode, make sure third-party scripts have type="text/plain" and a data-consent attribute. Alternatively, add the script domains as resource rules in the Rules tab.
Script loads before LiteConsent
The LiteConsent script must load before other third-party scripts. Place it as the first script in the <head>. If another script fires before LiteConsent initializes, it cannot be blocked retroactively.
Inline scripts
Inline scripts (written directly in HTML, not loaded via src) must use markup mode with type="text/plain" to be blocked. Resource rules (domain-based matching) only work for external scripts.
Banner shows on every page load
Cookie blocked by browser
LiteConsent stores consent in a first-party cookie. If the browser blocks all cookies (e.g., incognito mode with strict settings), consent cannot be saved. This is normal behavior and the banner will re-appear.
Cookie domain mismatch
If you've configured a custom cookie domain (for cross-domain consent), make sure it matches the current domain. A cookie set for .example.com won't be readable on other-site.com.
Consent reset
If you clicked "Reset all consents" in the Danger Zone tab, all existing consent records are cleared. Visitors will see the banner again on their next visit.
Google Consent Mode not working
Tag loading order
The LiteConsent script must load before your Google tags (gtag.js or GTM container). LiteConsent sets the default consent state on initialization, and Google tags read it when they load. If Google tags load first, they won't see the default consent state.
Category mapping not configured
Make sure your cookie categories are mapped to the correct Google consent types. In the Categories & Cookies tab, check that Analytics is mapped to analytics_storage and Marketing to ad_storage.
Verification
Open Chrome DevTools, go to the Console tab, and look for gtag('consent', 'default', ...) and gtag('consent', 'update', ...) calls. In GTM, use the Consent Overview panel to check whether tags see the correct consent signals.
Banner style looks broken
CSS conflicts
Your site's CSS may override LiteConsent banner styles. The banner uses a Shadow DOM to isolate its styles, but some global CSS resets (e.g., * { box-sizing: border-box; }) can still affect it. Check your browser's DevTools to inspect the banner element and look for style overrides.
Z-index issues
If the banner appears behind other elements, another element on your page has a higher z-index. The LiteConsent banner uses z-index: 2147483647 (the maximum). If something still overlaps, that element likely also uses Shadow DOM or is in a different stacking context.
Cookie scanner not finding all cookies
Cookies set after interaction
Some cookies are only set after user interaction (e.g., submitting a form, logging in, watching a video). The scanner loads your page and waits for it to settle, but it may miss cookies that require specific actions. You can manually add these cookies in the Categories & Cookies tab.
Cookies on subpages
The scanner checks your homepage and a few additional pages. Cookies set only on specific subpages (e.g., a checkout page) may not be detected. Run a rescan after adding the relevant URLs, or add the cookies manually.
Cross-domain consent not syncing
Sites not grouped
Cross-domain consent requires all sites to be part of the same domain group. In the General tab, use the "Join group" feature to link related sites together.
Different cookie domains
For cross-subdomain consent (e.g., app.example.com and www.example.com), set the cookie domain to the root domain (.example.com) in the General tab. For completely different domains, consent is synced server-side via an identifier.