Testing

Common install issues

Banner missing, trackers still firing, GTM double-load, leftover consent, wrong Configuration ID, and embeds that ship their own pixel.

The banner never appears

consent-widget.js is missing on the published site. View source and search for consent-widget.js and data-configuration-id.
The Configuration ID is empty, placeholder text, or belongs to another site.
You are on a preview URL that strips custom code (Webflow Designer, Squarespace preview, Wix editor).
A leftover sitetrust_consent value is hiding the banner. Clear it and reload.
An ad blocker removed the widget. Retest with the blocker off.
The script is in the footer or behind afterInteractive. Move it to the first position in <head>.

The banner appears, trackers still fire

GTM, GA4, or Meta is still above SiteTrust in the head.
You installed in the head and in GTM. Remove one path.
A Shopify customer-events pixel, a Wix marketing app, or a Squarespace connected account loads beside theme code.
A LeadConnector / GoHighLevel form, booking iframe, or chat widget loads Meta inside the iframe. Gate the embed until sitetrust_consent exists.
Someone added a manual gtag('consent', 'update', { analytics_storage: 'granted' }) that grants on every page.

Consent Mode default never logs

On GTM installs, the Consent Default tag is missing or uses All Pages / Window Loaded instead of Consent Initialization.
Tag sequencing is wrong: the widget fires before the default tag.
You logged dataLayer after the first push. Paste the logger, then reload.

Accept works, Decline does not

A tag ignores Built-in Consent Checks and fires on All Pages anyway.
A hardcoded script in the theme loads GA on every view.
You tested Decline in the same profile that already accepted. Use a new Incognito window.
The next page is a different template that never received the widget.

You installed the badge instead

widget.js with data-sitetrust-id is the Trust Badge. It will not show a consent banner. The banner is consent-widget.js with data-configuration-id. You can run both. Consent stays first.

Site Audit says 0 trackers or N/A and that feels wrong

Run A now also runs a source pre-scan. If trackers are in the HTML but the banner blocked them, the UI should say they were detected and blocked, not pretend the site has no tags. If Run B was marked N/A only because zero tags fired, that is outdated thinking: blocked tags are still tags. See Run A, Run B, and Run C.

← Previous

Consent records and Privacy Choices

Troubleshooting checklist

Need help?

Email wecare@sitetrust.com with your site URL and platform. One business day response, Monday through Friday.