How to Track ChatGPT Traffic in GA4

When usable traffic-source information reaches your site, GA4 records it in session-scoped source dimensions. AI referrals may appear among other sources rather than in a dedicated AI category, so the reliable starting point is the source data in your own property.

This tutorial moves from a quick source check to a reusable exploration and custom channel group. It also explains what the report cannot prove, including the sessions that arrive without clear source information and the difference between a session and a person or company.

Do not copy a source list blindly. Record the values present in your date range, then build and maintain the filter from that evidence.

Before building anything, confirm you actually receive AI referral traffic:

1. In GA4, go to Reports, then Acquisition, then Traffic acquisition.
2. Click the primary dimension dropdown (it defaults to Session default channel group) and switch it to Session source / medium.
3. In the search box above the table, type "chatgpt".
4. Repeat the check for other assistants relevant to your market, and keep only the source values your property actually records.

If rows appear, note the exact source strings you see. You will use the observed values in the next step instead of relying on a copied list.

For a reusable report across all AI sources, use GA4’s Explore section:

1. Go to Explore and create a blank exploration.
2. Import dimensions: Session source, and Landing page + query string. Import metrics: Sessions, Active users, Engagement rate, and Key events.
3. Set Session source as the row dimension and add your metrics as values.
4. Add a filter for Session source using the verified source values from Step 1. A regex can combine several values when appropriate.
5. Test the filter against a known date range before relying on it for reporting.

Landing page + query string shows where identifiable sessions entered and preserves campaign parameters that reached the page. It can reveal which destinations attract AI-referred visits, but it does not prove why an assistant selected or cited a page.

Explorations are for analysis; channel groups put AI traffic on the same footing as Organic Search and Email in your standard reports. GA4 supports custom channel groups (Admin, then Data display, then Channel groups) where you can define a new channel:

1. In Admin, open Channel groups and create a new channel group (or copy the default one).
2. Add a channel named "AI" with the condition: Session source matches the same regex you validated in Step 2.
3. Drag the AI channel above Referral in the order, since channel rules apply top-down and Referral would otherwise capture these sessions first.
4. Save, then use this channel group as the dimension in Traffic acquisition reports.

Two housekeeping notes. Custom channel groups apply from creation onward in standard reports, so build this before you need the trend line. And revisit the regex quarterly: new assistants appear, and their referrer strings only show up in your Step 1 audit.

Whatever number this setup produces, it leaves out part of AI influence for reasons worth understanding before anyone puts the chart in a board deck.

• Source information can be absent. Sessions without clear referral or campaign information may appear as Direct.
• Consent and blockers apply. What GA4 collects or models depends on your consent configuration, tagging, and browser conditions.
• Source drift. Providers and browser behavior can change, so a saved filter may need maintenance.
• Answers without clicks. If an assistant answers without producing a visit, website analytics has no session to measure.

You will find dramatic percentages online for how much AI traffic hides in Direct. We are deliberately not quoting one: the measured share varies by site and methodology, and this category already has enough unsourced numbers. Use the report as an identifiable view, not as a complete measure of AI influence.

Everything above shows sessions attributed to the ChatGPT and AI source values observed in your property, which pages they landed on, and whether they engaged. For a B2B team, the next question is whether any of those sessions came from a relevant account. GA4 does not provide reliable company identity for a session.

Company-level visitor intelligence may add account context for the identifiable share of traffic. Where a supported company match is available, joining it to visit and source context can help a team prioritize an account. It does not identify every visitor or establish the identity of a specific person.

Company context depends on a supported match, so it covers only part of the traffic in the report. Treat unmatched traffic as unknown rather than forcing a company or person identity.

PageFox brings visit context together and can add company context where available. It explains the signals behind its intent guidance so a team can decide whether a visit deserves attention. Setup uses one website script, without promising a fixed installation time or identification result.

If you also run the PageFox chat widget, it can answer from approved website content and let a visitor choose to share contact details. Submitted details remain separate from anonymous company-level signals.

Set up the GA4 view first. If the traffic matters to your team, PageFox can then add company-level visitor signals where available without treating every anonymous visit as an exact-person match.