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, and the two get conflated often enough that it is worth saying at the top. 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, because GTM is the gate the client already runs and a new gate is a new failure surface. We keep GA4. This tag does not replace the site's analytics program, and a client who hears "we added a tag" should not hear "we removed GA4."
Confirm visitor analytics is in the SOW. If it is not, skip the tag, because a tag that is not in scope is a tag that bills hours nobody asked for. Two install options: the GTM community template, or a header script. We use the template when GTM is already the gate, because the template is the shape GTM expects and it inherits GTM's version control. We use the script when there is no GTM and nobody wants to add it for one pixel, because adding GTM for one pixel is a bigger change than the pixel itself.
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, not on every page the site has, because a tag that fires everywhere bills events for pages nobody reads. We do not need a separate container, and a separate container is a new thing to maintain. We do not strip GA4 tags to "make room," because there is no room to make; tags coexist. 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, because the rule is about the data, not the install method. 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, which is a slice of traffic GA4 does not isolate cleanly. The client's existing conversions stay in GA4 unless they explicitly asked us to also mark conversions in Promptwatch, and "unless they asked" is the rule, because moving conversions without asking is a change to the client's measurement of their own business.
Then we ignore office IPs. Agency Wi-Fi, the client's HQ, and the staging VPN will otherwise look like a traffic story, and that traffic story will be wrong, because the office is not the market. Ignore known IPs in Promptwatch. Keep doing whatever IP filters you already have in GA4, because GA4's filters are GA4's filters and Promptwatch's are Promptwatch's. Two products, two ignore lists, same idea, and the idea is: keep internal traffic out of the numbers the client pays you to report. Ignore office and staging IPs in Promptwatch. Mirror the habit in GA4, so the two tools agree on what does not count.
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, because an AI-referred session is not a Google click and the two should not be charted as the same thing. After a week, read AI referrers and top pages. Do not call it a case study, because a week of data is a signal, not a finding, and a case study needs more than a signal. For blending those charts with GA4 and Search Console, see Looker. Still no averages across units, because the units problem does not go away when the charts are on the same page. Google's generative AI performance reports stay in Search Console for Overviews, because they are Google's numbers for Google's surface. They are not the same as an AI-referred session in this tag, and the two measure different things.
Visitor events sit on the plan. Essential is 200K events at $95/mo, which is enough for a single-brand site with modest AI-referred volume. Professional is 1M at $245/mo, for a site that gets real AI traffic. Business is 10M at $579/mo, for a larger property or a portfolio. Kick-off at $199/mo is the agency plan (unlimited projects and prompts, 10 seats), so an agency runs many clients on one plan. Explore is free, 10 ChatGPT prompts, and is not a traffic program, so do not point a client at Explore for visitor analytics. 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, and that view is a different pipe from a human click. That view starts on Professional for brand plans and is also included on the agency plans; Essential only supplies the visitor side of this comparison, so a team on Essential sees the human click but not the bot fetch. A human clicking a citation is visitor analytics. We will not diagnose a robots block from GTM, because GTM does not see bots. If a cited URL has zero AI visits, check crawler logs on a plan that includes them before rewriting the page, because the page may be fine and the bot may be blocked.
It is not local pack tracking. If they need maps, we run the local SEO playbook, because maps are a different surface with a different measurement. Locations in visitor analytics are where visitors were, not a simulated city on a prompt, and the two are not interchangeable. Personas and city checks are a different setup, and a prompt-level city check is a Promptwatch feature on Professional or an agency plan, not a visitor analytics output.
It is not instant alerts. We read referrers on the same cadence as the rest of the retainer, because a cadence is a habit and a habit is what gets read.
We do not put a write API key in GTM. The tag is a collector, and a collector does not need write capability. Keys for Looker and MCP stay read-only on analyst laptops, because a write key in a tag is a write key in a page source, and a page source is public.
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, which is a slice GA4 does not isolate. The client's existing conversions stay in GA4.
Is this the same as crawler logs?
No. ChatGPTBot fetching a page is Agent Analytics on Professional, Business, or an agency plan. Essential has no listed crawler-log allowance. A human clicking a citation is visitor analytics, and the two are different pipes.
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, so it does not cover visitor events.
If you want the tag in an existing container, hello@1001seomedia.com. Send the GTM account and the IPs to ignore.