Wix strips my tag entirely (Free plan).

Cause: Wix Free plans hard-block custom <script> injection at the platform CSP layer — the Custom Code panel is not even exposed under Settings → Advanced . Fix (option 1): upgrade to a Premium plan ($16+/mo) which unlocks Custom Code. Fix (option 2, no upgrade): use Wix's Tracking Tools & Analytics panel instead (Settings → Marketing → Tracking Tools & Analytics ) which has its own injection mechanism that bypasses the CSP block. Add a Custom tracking tool, paste the snippet, set scope to All pages , save. Both paths land the same pixel.

CSP errors in DevTools after pasting on a Premium plan.

Cause: Wix injects a strict Content-Security-Policy response header on some sites that limits which third-party origins can load scripts. The pixel snippet is rendered correctly, but the browser blocks the https://admaxxer.com/js/script.js request before it executes. Symptoms: DevTools Console shows "Refused to load the script ‘https://admaxxer.com/js/script.js’ because it violates the following Content Security Policy directive: script-src …" . Fix: contact Wix support and ask them to allowlist admaxxer.com in your site's CSP — they handle this on a per-site basis. While waiting, you can self-host via the script.local.js variant (proxied through your own domain) which sidesteps the third-party origin check entirely.

The pixel only fires on the homepage, not on internal pages.

Cause: Wix has two separate page-scope settings — Add Code to Pages defaults to Choose specific pages rather than All pages . If left on the default the snippet only injects on whatever page was visible when you saved. Fix: reopen Settings → Custom Code , edit your Admaxxer entry, set Add Code to Pages to All pages , and re-save. Verify by viewing the source on a deep page.

No events are showing up. What now?

Open DevTools Console and Network. Filter for script.js and /api/event. If they are blocked:csp, your Content Security Policy is blocking admaxxer.com — see /documentation/troubleshoot/csp. Also double-check that data-website-id matches the ID shown in your dashboard.

Events show up in staging but not production.

Confirm data-domain matches the production hostname exactly (no protocol, no trailing slash). Also confirm the website's Allowed Domains list in settings includes the prod domain.

My site is a single-page app — am I missing pageviews?

Use script.hash.js if you rely on location.hash routing. Otherwise the default script.js already hooks history.pushState/replaceState and tracks SPA navigations.

Install Admaxxer on Wix | Admaxxer AI Analytics Docs

Steps

1 Open Custom Code

In your Wix dashboard, go to Settings → Advanced → Custom Code, then click + Add Custom Code.

2 Paste the snippet

Set Add Code to Pages to "All pages" and Place Code in to "Head". Paste the snippet below and save.

html

<script defer
  data-website-id="YOUR_WEBSITE_ID"
  data-domain="yourdomain.com"
  src="https://admaxxer.com/js/script.js"></script>

3 Set load behavior

Choose Load code once so the pixel initializes once per session, not per route change (the Admaxxer pixel handles SPA navigation internally).
4 Verify the install

Load any public page on your site in a fresh browser tab. Within a few seconds, the Admaxxer dashboard realtime view should show the event. If nothing lands after 2 minutes, re-check the snippet is actually in the rendered HTML <head> (View Source, not just DevTools).

Troubleshooting

Wix strips my <script> tag entirely (Free plan).: Cause: Wix Free plans hard-block custom <script> injection at the platform CSP layer — the Custom Code panel is not even exposed under Settings → Advanced. Fix (option 1): upgrade to a Premium plan ($16+/mo) which unlocks Custom Code. Fix (option 2, no upgrade): use Wix's Tracking Tools & Analytics panel instead (Settings → Marketing → Tracking Tools & Analytics) which has its own injection mechanism that bypasses the CSP block. Add a Custom tracking tool, paste the snippet, set scope to All pages, save. Both paths land the same pixel.
CSP errors in DevTools after pasting on a Premium plan.: Cause: Wix injects a strict Content-Security-Policy response header on some sites that limits which third-party origins can load scripts. The pixel snippet is rendered correctly, but the browser blocks the https://admaxxer.com/js/script.js request before it executes. Symptoms: DevTools Console shows "Refused to load the script ‘https://admaxxer.com/js/script.js’ because it violates the following Content Security Policy directive: script-src …". Fix: contact Wix support and ask them to allowlist admaxxer.com in your site's CSP — they handle this on a per-site basis. While waiting, you can self-host via the script.local.js variant (proxied through your own domain) which sidesteps the third-party origin check entirely.
The pixel only fires on the homepage, not on internal pages.: Cause: Wix has two separate page-scope settings — Add Code to Pages defaults to Choose specific pages rather than All pages. If left on the default the snippet only injects on whatever page was visible when you saved. Fix: reopen Settings → Custom Code, edit your Admaxxer entry, set Add Code to Pages to All pages, and re-save. Verify by viewing the source on a deep page.
No events are showing up. What now?: Open DevTools Console and Network. Filter for script.js and /api/event. If they are blocked:csp, your Content Security Policy is blocking admaxxer.com — see /documentation/troubleshoot/csp. Also double-check that data-website-id matches the ID shown in your dashboard.
Events show up in staging but not production.: Confirm data-domain matches the production hostname exactly (no protocol, no trailing slash). Also confirm the website's Allowed Domains list in settings includes the prod domain.
My site is a single-page app — am I missing pageviews?: Use script.hash.js if you rely on location.hash routing. Otherwise the default script.js already hooks history.pushState/replaceState and tracks SPA navigations.

Steps

1 Open Custom Code

2 Paste the snippet

3 Set load behavior

4 Verify the install

Verify installation

Troubleshooting

Related install guides