If Personyze isn’t recognizing visitors, nothing else works — no targeting, no actions, no data. Here’s how to tell the tracker isn’t firing and fix it fast.
How to tell
- In Settings → Tracking Code, the domain shows Not firing and “0 visits in the last 90 minutes.”
- Live activity stays empty while you browse your own site.
Running a caching or speed plugin? Exclude Personyze from it, or personalization will not appear until the visitor interacts with the page. What to exclude, and the one-line test.
Check these, in order
- Is the snippet on the page? View source on a live page and confirm the Personyze tracker script is present, ideally before
</head>. See Installing Personyze. - Right domain?
www.and the bare domain are two entries unless you used the all-domains code. Add the exact domain, or switch to the all-domains snippet. - Is it inside an iframe? The tracker must run on the top-level page, not embedded in an iframe.
- Is a consent manager blocking it? If a cookie/consent tool holds scripts until the visitor accepts, that’s working as intended — categorize the Personyze script so it loads after consent. See Privacy & GDPR.
- Single-page app? The tracker loads once; tell Personyze on each route change so page-level targeting keeps working (see the SPA note in the install guide).
- Ad/script blockers — test in a clean browser profile to rule them out.
Once a page loads with the snippet, refresh Tracking Code — the domain should flip to Active within a minute.