How to Set Up Promptwatch Visitor Analytics with Google Tag Manager
How we add Promptwatch visitor analytics in Google Tag Manager with the community template or a script, ignore office IPs, and keep GA4.
Mentions are not visits. If the SOW includes AI-referred traffic, we add Promptwatch visitor analytics. We do it in Google Tag Manager when the account already lives there. We keep GA4. This tag does not replace the site's analytics program.
Confirm visitor analytics is in the SOW. If it is not, skip the tag. Two install options: the GTM community template, or a header script. We use the template when GTM is already the gate. We use the script when there is no GTM and nobody wants to add it for one pixel.
Template or script, then ignore the office
In GTM, add the Promptwatch community template (or the equivalent script tag). Fire it on the pages the SOW cares about. We do not need a separate container. We do not strip GA4 tags to "make room." Template if GTM is already how tags ship. Script if there is no GTM and adding one is out of scope. Same ignore-IP rule either way. Leave GA4 alone.
Do we remove the GA4 tag after Promptwatch is in GTM? No. Keep GA4. Promptwatch visitor analytics is for AI referrers and the pages those visits hit. The client's existing conversions stay in GA4 unless they explicitly asked us to also mark conversions in Promptwatch.
Then we ignore office IPs. Agency Wi-Fi, the client's HQ, and the staging VPN will otherwise look like a traffic story. Ignore known IPs in Promptwatch. Keep doing whatever IP filters you already have in GA4. Two products, two ignore lists, same idea. Ignore office and staging IPs in Promptwatch. Mirror the habit in GA4.
What we read after it is live: AI referrers, top pages, sources, locations. That is enough to say "this URL got sessions from an assistant" without pretending it is a GSC click. After a week, read AI referrers and top pages. Do not call it a case study. For blending those charts with GA4 and Search Console, see Looker. Still no averages across units. Google's generative AI performance reports stay in Search Console for Overviews. They are not the same as an AI-referred session in this tag.
Visitor events sit on the plan. Essential is 200K events at $95/mo. Professional is 1M at $245/mo. Business is 10M at $579/mo. Kick-off at $199/mo is the agency plan (unlimited projects and prompts, 10 seats). Explore is free, 10 ChatGPT prompts, and is not a traffic program. G2: 4.7/5.
What this is not
It is not crawler logs. ChatGPTBot fetching a page is Agent Analytics, usually via Cloudflare or another CDN. A human clicking a citation is visitor analytics. We will not diagnose a robots block from GTM. If a cited URL has zero AI visits, check crawler logs before you rewrite the page.
It is not local pack tracking. If they need maps, we run the local SEO playbook. Locations in visitor analytics are where visitors were, not a simulated city on a prompt. Personas and city checks are a different setup.
It is not instant alerts. We read referrers on the same cadence as the rest of the retainer.
We do not put a write API key in GTM. The tag is a collector. Keys for Looker and MCP stay read-only on analyst laptops.
FAQ
Do we remove the GA4 tag after Promptwatch is in GTM?
No. Keep GA4. Promptwatch visitor analytics is for AI referrers and the pages those visits hit. The client's existing conversions stay in GA4.
Is this the same as crawler logs?
No. ChatGPTBot fetching a page is Agent Analytics, usually via Cloudflare or another CDN. A human clicking a citation is visitor analytics.
Which plan covers visitor events?
Essential is 200K events at $95/mo. Professional is 1M at $245/mo. Business is 10M at $579/mo. Explore is not a traffic program.
If you want the tag in an existing container, hello@1001seomedia.com. Send the GTM account and the IPs to ignore.