How to Set Up Promptwatch Visitor Analytics with Google Tag Manager

The first week of "AI visits" is often you reloading the homepage. Ignore known IPs for internal traffic before you send a screenshot to a client. Add the office egress, the VPN, and the agency wifi. This is not a bot filter for the whole internet. It is a list of IPs you know. If a founder works from a coffee shop, that visit will still count. That is fine. The damage is the always-on office NAT, the line of office desks that pings the homepage all day and inflates the AI-referrer number until it means nothing.

The reason this matters is that visitor analytics is the slice of Promptwatch that is hardest to fake your way out of. Mention counts can move because a model changed wording. Citation counts can move because a competitor published. But a visit that lands on /pricing after a ChatGPT referral is a person, and that person either converts or does not. If that number is polluted with your own staff, the whole cut becomes noise. Clean it once, at the IP level, and leave it.

Mention share without traffic is a slide. Promptwatch visitor analytics is how you see whether an AI answer sent a person to the site, which page they landed on, and from which source. It collects that with a header script or the official Google Tag Manager community template. Use that template, not a random tag someone pasted in Slack. A community template is versioned, documented, and updated when the underlying event schema changes. A Slack paste is none of those things, and it breaks silently.

Site: promptwatch.com. Event caps: 200K on Essential ($95/mo, 7-day trial), 1M on Professional ($245/mo), 10M on Business ($579/mo). Explore is free (ChatGPT, 10 prompts) and is not a traffic product. Agency Kick-off $199, Growth $399, Scale $799. Promptwatch is 4.7/5 on G2, 1,840+ brands.

Do not drop GA4. Keep GA4 for the full session story. Promptwatch visitor analytics is the AI-referrer slice, with top pages, sources, locations, and devices/browsers. The two tools answer different questions. GA4 tells you how many people came and what they did across the whole site. Promptwatch tells you which of those came from an AI answer and whether that AI-referred session was worth anything. You need both because collapsing them into one number hides the part you actually came here to measure.

One path: template or script

If you already ship tags through GTM, use the official Promptwatch community template. That keeps the snippet next to GA4 instead of a one-off paste in the theme. If you do not use GTM, put the header script on the pages you care about. Use the same GTM habits you already have for GA4. Publish the tag or script on the production hostname you actually track.

The choice between template and script is a workflow choice, not a quality choice. Both fire the same events. The template wins when your team already lives in GTM, because it sits in the same container, ships in the same publish flow, and gets reviewed in the same version history. The script wins when you have a small site and a single template file, because pasting once is faster than standing up a container. Pick the one that matches how you already ship tags, and do not invent a third path.

What you get after hits land: AI-referred visits, top pages, sources, locations, and devices/browsers. That is enough to answer "did ChatGPT send anyone to /pricing" without opening GA4's full acquisition report. Confirm an AI-referred test visit (or wait for a real one) and check top pages. The test visit matters because it tells you the tag fired. After that, the real visits tell you whether AI answers are sending people who care about your pricing page or your docs or your careers listing.

GA4 can still be your system of record for all traffic. Promptwatch is the cut that is about AI referrers. You can also blend both in Looker Studio on Professional and above. Keep them as two charts. Compare the slice to GA4 without merging the two into one metric. Merging them is the mistake people make when they want one clean number for a slide. The slide gets cleaner and the analysis gets worse, because you can no longer see whether AI referrers are over- or under-performing the rest of acquisition.

If you already connected GSC, you will see Google clicks and AI-referred visits in two places. They will not match. That is expected. OpenAI's Publishers and Developers FAQ documents utm_source=chatgpt.com on ChatGPT Search referrals. Filter that parameter in GA4 if you want. Promptwatch visitor analytics is still the AI-referrer slice, including sources that do not send a clean UTM. The UTM is a convenience for GA4. Promptwatch does not depend on it, which is why it catches AI referrers that GA4 misses or buckets into direct.

Events are not crawler logs

200K events on Essential is plenty for a single brand that is not a media site. Essential has no listed crawler-log allowance. Professional covers 1M visitor events and separately includes 25M crawler logs. Business covers 10M visitor events and 100M crawler logs. Do not assume visitor events and crawler logs share a bucket. They do not. Visitor events are people arriving. Crawler logs are bots fetching. The two numbers move for different reasons and live on different tiers, so price them separately when you scope a plan.

Otterly.AI from $29/mo and Peec AI from $95/mo track mentions, not this GTM AI-referral cut. Semrush AI Toolkit at $99/domain stays in Semrush reporting. Method: how we rank. Tools list.

FAQ

Should I drop GA4 after adding this tag?

No. Keep GA4 for the full session story. Promptwatch visitor analytics is the AI-referrer slice.

How many visitor events do the plans include?

Visitor-event limits are 200K on Essential ($95/mo), 1M on Professional ($245/mo), and 10M on Business ($579/mo). Essential has no listed crawler-log allowance. Professional and Business have separate crawler-log quotas of 25M and 100M.

Why did the first week look huge?

Office traffic. Ignore known IPs for the office egress, the VPN, and the agency wifi before you send a screenshot.