"My pixel isn't tracking" checklist

If Ana shows no visitors, no events, or numbers that look far too low, work through the four steps below in order. They go from the most common cause to the rarest: the pixel script isn't on the page at all, the script is there but events aren't arriving, an ad blocker is interfering with your own testing, or you're looking at the wrong site's data. Most missing-data reports are resolved by step 1 or step 2.

Before you start, note which page you expect to be tracked and have it open in a browser tab — every step below checks something on that page.

Step 1: Is the pixel script on the page?

The pixel can only track pages it is actually loaded on. Check the page source directly rather than trusting that the install "should" be everywhere:

1. Open the page in your browser.
2. View the page source (right-click → View Page Source, or your browser's equivalent).
3. Search the source for zalify. You're looking for the pixel snippet you copied during installation.

If the snippet is missing, the pixel was never installed on this page — common when the snippet was added to one template but not others, or when a site redesign or theme change removed it. Reinstall it following Installing the Zalify pixel, then re-test. Fixed? Stop here.

If you installed via the Shopify integration rather than a manual snippet, check that the integration is still connected — see Connecting Shopify.

Step 2: Is the script loading but events not arriving?

The snippet being present in the source doesn't guarantee events are reaching Ana. Verify from the Zalify side:

1. Open Ana and check whether your site shows recent activity.
2. Visit your site yourself in a normal browser window, browse a few pages, then look for your own visit. New events should appear within a few minutes.

If your test visit shows up, the pixel is working — a "low numbers" complaint at this point is usually a reporting-window or expectations question, not a tracking failure. See Analytics overview for how the reports count visitors. Fixed? Stop here.

If your test visit does not show up, check the browser's developer console on your site for JavaScript errors, and confirm the snippet wasn't modified when it was pasted in (a truncated or re-formatted snippet is a frequent culprit). Re-copy a fresh snippet per Installing the Zalify pixel. Fixed? Stop here — otherwise continue to step 3 before concluding anything, because the next step can make a working pixel look broken.

Step 3: Is an ad blocker blocking your test?

Ad blockers, privacy extensions, and some browsers' built-in tracking protection can block analytics scripts — including yours, on your own site. This produces the classic confusing symptom: the pixel works for most real visitors, but you never see your own test visits.

1. Retry your test from step 2 in a browser with no extensions, or a fresh browser profile. Don't just use a private/incognito window — many blockers stay active there.
2. If the clean browser's visit shows up in Ana, your pixel is fine; your everyday browser was blocking it. Fixed? Stop here.

Some fraction of your real audience runs blockers too, so Ana's numbers will always sit somewhat below your platform's raw traffic numbers. That gap is expected and affects every analytics tool, not just Zalify. If you're comparing Ana against another analytics product and the totals differ modestly, this is usually why.

Step 4: Are you looking at the right site's pixel?

Each site in your workspace has its own pixel. If you manage more than one site, two mix-ups are common:

• Wrong snippet installed. Site B's snippet was pasted onto Site A's pages, so Site A's traffic lands in Site B's reports. Compare the identifier in the installed snippet against the one shown for the site in Zalify.
• Wrong site selected in reports. The pixel is fine, but you're reading another site's dashboard. Check which site is currently selected before digging further.

Reinstall the correct snippet if it's the first case, or switch sites if it's the second — see Managing sites. Fixed? Stop here.

Still stuck?

If you've cleared all four steps and events still aren't arriving, contact support via the in-app Help entry in the top navigation. Include the page URL you're testing, the site name in your workspace, and roughly when you ran your test visit — that's enough for us to check what your pixel is sending.

Note that tracking and identification are related but different problems: the pixel can be tracking visits correctly while a Reach automation still doesn't trigger, because the visitor isn't identified as a contact yet. If your actual symptom is "my automation didn't fire", see Zalify pixel and Reach and the "My email wasn't delivered" checklist.