1. Check that all your domains are whitelisted
Every domain and subdomain where the Pixel is deployed must be individually added to the Configured Domains list in the Uniqode dashboard.
For example, if your user journey touches both www.example.com and shop.example.com, both must be whitelisted — they are treated as separate domains.
How to check: Go to the Uniqode dashboard → Pixel Setup → Configured Domains. Confirm that every domain where you expect to see tracking data is listed.
2. Check that your GTM container is published
If you installed the Pixel through Google Tag Manager, changes need to be published before they take effect on your live site. Saving a tag alone is not enough.
How to check: In Google Tag Manager, look for a blue Submit button in the top-right corner. If there are unpublished changes, click Submit → Publish. After publishing, visit your site and confirm data starts appearing in Insights.
3. Check that your GTM tag type is Custom HTML
The Pixel must be added as a Custom HTML tag in GTM. If it was added using a different tag type (such as one that loads inside an iframe), the Pixel won't be able to read your page's URL, which breaks tracking and attribution.
Signs this may be the issue: Events appear in Insights but show the wrong domain, or pageview events are not linked to any QR code scans.
How to check: In Google Tag Manager, go to Tags → click on your Uniqode Pixel tag → confirm the tag type is Custom HTML. If it's set to anything else, recreate the tag as Custom HTML following the setup guide. Then publish the container.
4. Check whether your website has a Content Security Policy (CSP)
Some websites enforce security policies that can block third-party scripts like the Pixel from loading or sending data. If your organization manages a Content Security Policy, two URLs need to be allowlisted for the Pixel to work.
Share the following with your IT team:
What to allowlist | Where to add it | Why it's needed |
script-src | Allows the Pixel script to load | |
connect-src | Allows tracking events to be sent |
Note: If only the first URL is allowlisted but the second is not, the Pixel will appear to load correctly but will silently fail to send any tracking data.
If you're not sure whether your website uses a CSP, check with your IT team or website administrator.
5. Check that URL parameters are preserved
When someone scans a QR code, Uniqode adds a ?uq= parameter to the destination URL. This parameter is what connects the website visit back to the original QR scan — without it, Insights can't attribute pageviews to specific scans or scanners.
Signs this may be the issue: Pageview events appear in Insights, but they aren't linked to any QR code or scanner profile.
Common causes:
Your CMS or marketing platform automatically removes unrecognized URL parameters.
A redirect chain between the QR code and your final landing page drops query strings.
How to check: Scan one of your QR codes and look at the URL in your browser's address bar when you land on the destination page. If you see ?uq= (or &uq=) in the URL, the parameter is being preserved. If it's missing, something in your redirect chain is stripping it.
If you're unsure how to fix this, contact Uniqode support — we can help identify where the parameter is being lost.
6. Check multi-domain journeys
If your user journey spans multiple domains (e.g., QR code → domain1.com → domain2.com), the Pixel must be installed on each domain, each domain must be whitelisted, and the ?uq= parameter must be preserved across the full redirect chain.
Multi-domain setups can be complex depending on your architecture. Contact Uniqode support and we'll help you get it configured correctly.
Quick reference
What you're seeing | Most likely cause | What to do |
No events appearing at all | Domain not whitelisted | Check Configured Domains in Pixel Setup (#1) |
Pixel works in GTM Preview but not on live site | GTM container not published | Publish your GTM container (#2) |
Events show the wrong domain | Wrong GTM tag type | Confirm tag is Custom HTML (#3) |
Pixel loads but no data comes through | CSP blocking the tracking endpoint | Share allowlist URLs with your IT team (#4) |
Events appear but aren't linked to QR scans | ?uq= parameter being stripped | Check that URL parameters are preserved (#5) |
Still having trouble? Contact Uniqode support and we'll help you diagnose the issue.
FAQ
Is a new Pixel required per domain?
No. Each account has a single Pixel. The same Pixel code can be used across multiple domains.
Does every domain and subdomain need to be whitelisted?
Yes. Each domain and subdomain must be individually whitelisted.
What if the journey spans multiple domains (e.g., QR code → domain1 → domain2)?
This requires technical support from Uniqode.
Multi-domain journey considerations:
Subdomain changes: Tracking works if cookies are retained and the Pixel is installed on each subdomain
Domain changes (or cookie loss): The
?uq=******URL parameter must be preserved throughout the journey for accurate tracking