Troubleshooting
What to do when the Console shows no banner, a CSP error, a missing data layer, or two Specifications loaded.
Four problems, each with what you will see, why it happens, and what to do.
Containers that block Custom HTML
Symptom: your tag never fires in Preview, and there is no banner in the Console.
Why: some GTM setups disallow Custom HTML tags. Whoever owns the GTM container can set an allowlist or blocklist that stops them.
What to do: ask whoever owns the GTM setup. The tag type must be allowed in the container.
A Content Security Policy blocks inline scripts
Symptom: the Console shows a CSP error naming script-src, and there is no banner.
Why: the snippet is an inline script. A Content Security Policy that blocks inline scripts stops it before it runs.
What to do: ask your developers. They can allow GTM's inline scripts through the policy, or add the nonce or hash GTM provides. Quadrano sends nothing, so the policy itself is not Quadrano's to set.
Custom dataLayer names
Symptom: you installed the snippet, but the Console says there is no data layer.
Why: Quadrano Local reads window.dataLayer only. If the site pushes to a data layer with another name, the snippet cannot see it.
What to do: there is no workaround in Quadrano Local today. Ask whoever owns the site's GTM setup whether the site can use the standard dataLayer name.
Two Specifications loaded
Symptom: the Console shows a "Two Specifications loaded" warning naming two spec IDs.
Why: two Quadrano tags fired on the same page, or one tag fired twice with two different Specifications.
What to do: keep one tag per site, and one Specification per tag. See One Specification per site.
Still stuck?
Work through the docs in order, and check each step against the Console. The fastest person to ask is whoever owns your site's GTM container — they can see the tags, the triggers and the policy.