AI Visibility Tracking — Count Pixel Requests
Add a tracking pixel to a site and review counted requests grouped by reported crawler user agent. The counts are a partial signal.
What can AI Visibility Tracking count?
Register a site, add its pixel URL to pages you control, and view the requests that reach it. ZTools groups counted hits by day and by the crawler name reported in each request's user agent. You don't need an AI provider key. Your plan limits how many sites you can register. A crawler may skip the pixel, and a user agent can be spoofed. The recent-day table isn't a complete or verified count of AI crawls.
Use cases
- Check whether the pixel receives requests. Add the pixel to pages you control and watch the recent-day table. A zero may mean no matching request reached the pixel.
- Compare registered sites. Register another site if your plan allows it, then review each site's counted requests. The tool cannot prove which bot actually made a request.
- Investigate a change. If a count changes, check your page markup, server logs, and crawl settings. The pixel is one signal, not a diagnosis.
How it works
- Register a site. In the AI Visibility Tracking screen, register a domain you control and copy its pixel URL.
- Add the pixel URL. Add the generated pixel URL to pages you control. A request appears only if something loads that URL.
- Receive requests. The function receives the pixel request and reads its self-reported user-agent for classification.
- Group by reported user agent. The function groups matching user-agent strings into GPT, Claude, Gemini, Perplexity, or Other buckets. The label does not verify the requester's identity.
- Review recent counts. Review the recent daily counts in the table. The current screen has no export or per-page breakdown.
- Investigate changes. Use the counts as a prompt to inspect server logs or crawl settings; they cannot prove indexing or citation.
Examples
Input: A registered site whose pixel receives a request claiming GPTBot
Output: The recent daily table adds one count to the GPT bucket if recording succeeds.
The user-agent is self-reported; the request is not authenticated as GPTBot.
Input: A page where no request reaches the pixel
Output: No hit from that page is counted.
A zero does not prove no crawler fetched the page.
Frequently asked questions
Is AI Visibility Tracking free, and what does it cost?
The Free plan allows a limited number of tracked sites. Paid Growth plans may allow more; check your current limit in ZTools. The screen currently shows a bounded recent-day table and doesn't establish a longer paid retention period.
Does it capture every AI bot visit to my site?
No. It counts only requests that reach the pixel URL. Some crawlers do not load page images, and pages without the snippet are absent. Treat the table as recorded pixel activity, not a representative sample of all crawler visits.
Do I need an API key or to bring my own key for this tool?
No provider key is needed. Add a site in ZTools and place its pixel URL on the pages you want to measure. Only requests that reach that URL can appear in the dashboard.
If I see GPTBot hits, does that mean ChatGPT will cite me?
No. A pixel hit cannot prove indexing, training, or an AI citation. The user-agent is not a verified identity.
How does it know a request came from a specific AI bot?
The function matches text in a request's user-agent and groups it into GPT, Claude, Gemini, Perplexity, or Other. That text can be spoofed.
Will the pixel slow my site or collect visitor data?
The pixel request reaches a ZTools server function, which reads request information to classify and count it. Its purpose is crawler counts, but the user-agent string is self-reported. Review the pixel and your site's own notice before adding it.
Can I track more than one website?
Yes, up to your plan's tracked-site limit. Each registered site has its own pixel URL. Check the current limit before adding another site.
Pro tips
- Put the pixel URL in a shared page template if you want it present on several pages.
- Compare the counted requests with your server access logs to understand what the pixel misses.
- If a count changes after a site edit, check server logs before attributing it to robots.txt or another file.
- A flat count can have several causes; check whether the pixel still loads.
Reviewed by the ZTools team · Last updated 2026-10-14 · Part of ZTools.
For the full,
formatted version of this page, please enable JavaScript and reload
https://ztools.zaions.com/growth/visibility-tracking.