---
title: "Find Your ChatGPT Traffic in GA4—and See Which Pages Convert"
description: "Build a custom GA4 channel group for ChatGPT and other AI assistants, find their landing pages and conversions, and understand what the reports miss."
url: "https://groas.com/post/tracking-traffic-from-chatgpt-and-other-ai-tools-in-ga4"
image: "https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/4b76dcf2-d8c9-48f2-a990-c7a165595de9.png"
published: "2026-11-19T14:32:53.629Z"
modified: "2026-11-19T14:32:53.732Z"
---

November 19, 2026 · 10 min read

# Find Your ChatGPT Traffic in GA4—and See Which Pages Convert

[](https://groas.com/author/alexander-perelman)

[Alexander Perelman](https://groas.com/author/alexander-perelman)Personally Tested

Head Of Product @ groas

[LinkedIn](https://www.linkedin.com/in/alexander-433793253/)

![A miniature sorting room where tiny clerks move envelopes from a messy heap into five colour-coded pigeonholes, while a pile of blank, untraceable envelopes stays roped off.](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/4b76dcf2-d8c9-48f2-a990-c7a165595de9.png)

In this article

1. [Before starting: get access and choose your reporting window](#before-starting-get-access-and-choose-your-reporting-window)
2. [Step 1: Find the AI sources your property actually records](#step-1-find-the-ai-sources-your-property-actually-records)
3. [Step 2: Create one channel group with separate assistant rows](#step-2-create-one-channel-group-with-separate-assistant-rows)
4. [Step 3: Confirm the group reclassifies historical sessions](#step-3-confirm-the-group-reclassifies-historical-sessions)
5. [Step 4: Build the landing-page and conversion view](#step-4-build-the-landing-page-and-conversion-view)
6. [Step 5: Mark the traffic this setup cannot identify](#step-5-mark-the-traffic-this-setup-cannot-identify)
7. [Step 6: Ask your assistant through groas to read the report](#step-6-ask-your-assistant-through-groas-to-read-the-report)
8. [Step 7: Fix one landing page before chasing more visits](#step-7-fix-one-landing-page-before-chasing-more-visits)
9. [Step 8: Verify the setup, then repeat the useful part monthly](#step-8-verify-the-setup-then-repeat-the-useful-part-monthly)

Your ChatGPT traffic may already be in GA4, buried under Referral beside random blogs and tool spam. I start by fixing the filing system, not by chasing more traffic.

By the end of this tutorial, you will have **a custom channel group that separates AI assistants, a saved landing-page report, and a way to ask your assistant which pages deserve attention through groas**. You will also know what this setup cannot recover. Better reporting is useful. Pretending it captures everything is not.

## Before starting: get access and choose your reporting window

Have these ready:

- `Editor` access to your GA4 property. Viewer access cannot create channel groups.
- About 20 minutes for the setup.
- A reporting window with enough traffic to inspect. I use 90 days where available.
- Key events configured for the actions you want to measure.

GA4 now includes a [built-in AI Assistant channel](https://support.google.com/analytics/answer/9756891?hl=en\&ref_topic=11151952). Check it, but do not stop there. This tutorial creates separate rows for ChatGPT, Perplexity, Gemini, Claude and Copilot so you can inspect each assistant rather than one combined bucket.

[Custom channel groups apply retroactively](https://support.google.com/analytics/answer/13051316?hl=en). **You can reclassify recorded traffic; you cannot recreate attribution signals GA4 never received.** That distinction matters throughout the setup.

## Step 1: Find the AI sources your property actually records

Open `Reports > Acquisition > Traffic acquisition`. Set the primary dimension to `Session source`, then search for these names one at a time:

```text
chatgpt
openai
perplexity
gemini
claude
copilot
deepseek
grok
```

Write down the source values that appear. Common examples include `chatgpt.com`, legacy `chat.openai.com`, `perplexity.ai`, `gemini.google.com`, `claude.ai`, `copilot.microsoft.com`, `chat.deepseek.com` and `grok.com`. [These are the domains practitioner guides repeatedly identify](https://www.analyticsmania.com/post/ai-traffic-in-google-analytics-4/), but your own report should decide the list.

For the five-assistant setup below, the combined source pattern is:

```regex
chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|claude\.ai|copilot\.microsoft\.com
```

Do not build a rule that matches anything containing `ai`. That is a substring, not an attribution strategy. It can collect unrelated tools and `.ai` domains along with the assistants you meant to measure.

**Expected result:** a short list of recognizable assistant sources already present in your property.

**Common mistake:** copying a domain list without checking whether your source values match it. If a source differs, use the value your report actually records rather than silently excluding it.

## Step 2: Create one channel group with separate assistant rows

Go to `Admin > Data display > Channel groups`. Open the three-dot menu beside `Default Channel Group`, choose `Copy to create new`, and name the copy:

```text
AI split by assistant
```

Work inside that copy. Standard properties allow [up to two custom channel groups, with up to 25 channels in each](https://www.analyticsmania.com/post/ai-traffic-in-google-analytics-4/), so keep the assistant rows together rather than spending a group on each one.

Add a channel named `AI: ChatGPT`. Set its condition to `Source` → `matches regex`, then paste:

```regex
chatgpt\.com|chat\.openai\.com
```

Repeat for the other four channels:

| Channel name     | Source pattern            |
| ---------------- | ------------------------- |
| `AI: Perplexity` | `perplexity\.ai`          |
| `AI: Gemini`     | `gemini\.google\.com`     |
| `AI: Claude`     | `claude\.ai`              |
| `AI: Copilot`    | `copilot\.microsoft\.com` |

[GA4 regex uses full matching by default, and an unescaped dot is a wildcard](https://support.google.com/analytics/answer/1034324). These patterns match the listed source values. If Step 1 revealed a different value, adjust the relevant pattern deliberately.

**Do not add a condition requiring the default channel to be Referral.** A recognizable assistant source can arrive through a tagged URL without a referrer and fall outside that bucket. The source is the signal this group needs to catch.

![Referral filing drawer overflowing with ChatGPT and Perplexity folders](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/89fa2159-9737-47de-9043-5c6afca8026f.png)

Drag all five assistant channels above the existing channels that could otherwise claim those sessions, including `Referral`, `Organic Search` and `AI Assistant` if present. Apply the ordering and save the group.

[GA4 assigns traffic to the first channel it matches](https://www.analyticsmania.com/post/ai-traffic-in-google-analytics-4/). A perfect rule underneath an earlier matching rule does nothing useful.

**Expected result:** one saved group containing five named assistant channels, followed by the existing channels.

**Common mistake:** leaving the new rows below Referral and concluding that AI traffic is zero. **Check channel order before debugging the regex.**

## Step 3: Confirm the group reclassifies historical sessions

Return to `Reports > Acquisition > Traffic acquisition`. Select your new group’s session-scoped dimension in the primary-dimension picker, then use the same date range you inspected in Step 1.

Look for the assistant sources you already found. Their sessions should now appear under the corresponding `AI:` rows rather than whichever broader channels previously held them.

Do not expect every assistant row to contain traffic. A rule creates a category, not visitors. If your property recorded no Claude sessions, an empty Claude row is not a setup failure.

If an expected row is empty, check in this order:

1. Confirm that the report uses `AI split by assistant`, not the default group.
2. Confirm that the date range includes the source sessions from Step 1.
3. Check the new channels’ position in the group.
4. Compare the recorded source value with the regex, character by character.
5. Confirm that no Referral-only condition slipped into the rule.

**Expected result:** historical sessions with matching sources appear in the assistant rows. You do not need to wait for new traffic to test the classification.

**Common mistake:** expecting a custom group to repair Direct sessions that contain no assistant source. It cannot. Fix the classification you have evidence for; leave the rest unclaimed.

## Step 4: Build the landing-page and conversion view

Open `Explore > Blank exploration`. Name the exploration so you can find it again, then import these dimensions:

- `Session source`
- `Landing page + query string`
- The session-scoped dimension for `AI split by assistant`

Import these metrics:

- `Sessions`
- `Engaged sessions`
- `Key events`
- `Session key event rate`

Set up the free-form table:

1. Put `Landing page + query string` in `Rows`.
2. Put your custom channel group’s session dimension in `Columns`.
3. Put the four metrics in `Values`.
4. Add a filter on that same channel-group dimension: `begins with` → `AI:`.
5. Set the reporting dates and save the exploration.

This [landing-page layout connects assistant traffic with the pages people actually reach](https://www.preaeo.com/blog/ga4-ai-referral-traffic/). The acquisition report tells you volume. This view gives you somewhere to act.

Keep `Landing page + query string` while investigating. [ChatGPT can append `utm_source=chatgpt.com` to destination URLs](https://www.preaeo.com/blog/ga4-ai-referral-traffic/), so the query string can help explain how a visit arrived.

But do not confuse URL detail with session attribution. **Removing the query string from the displayed landing-page dimension does not erase the session source or merge non-AI traffic into an AI-filtered report.** It groups URL variants together. Keep the detail when diagnosing; simplify the view when that detail becomes clutter.

**Expected result:** separate assistant columns showing landing pages, session volume and key-event performance.

**Common mistake:** treating key-event counts as conversion rates. A page with more events may simply have more traffic. Read the rate alongside the count, and check that the configured key events represent actions you care about.

## Step 5: Mark the traffic this setup cannot identify

Before sharing the report, add a plain-language limitation: **these are identifiable AI-referred sessions, not all visits influenced by AI.**

GA4 needs a usable signal to attribute a visit to an assistant. [App opens and copied-and-pasted links can arrive without a referrer](https://perceptric.com/blog/ai-search-attribution/). A source tag can preserve attribution when the referrer is absent; without either signal, this channel group has nothing to match.

Source-only tagging also explains why the rules must not require Referral. [A ChatGPT URL tagged only with `utm_source=chatgpt.com` can appear as `chatgpt.com / (not set)`](https://seoaeogeo.app/blogs/ga4-ai-assistant-channel-track-ai-traffic). The recognizable source is still useful even when the medium is not.

Keep three other boundaries clear:

- A citation without a click is not a website session.
- Crawlers such as GPTBot that do not run your tag are not measured as these visitor sessions.
- [Google’s AI Overviews and AI Mode remain in Organic Search](https://support.google.com/analytics/answer/9756891?hl=en\&ref_topic=11151952). Do not force them into this assistant table.

Tagging behavior can change, too. [Profound documented a sharp interruption in ChatGPT’s UTM tagging](https://www.tryprofound.com/blog/chatgpt-missing-utm-tags) and warns against turning its observations into a multiplier for your revenue reports. Restored tags do not repair visits already recorded without them.

**Expected result:** a report labeled as an attributable slice of traffic, with its limits visible.

**Common mistake:** multiplying the measured sessions by a guessed correction factor. Treat the count as a floor, not an invitation to invent the missing total.

## Step 6: Ask your assistant through groas to read the report

Once the group works, connect GA4 through groas and give your assistant the group name. The repetitive job is pulling the same sessions, pages and key events every week without changing the question halfway through.

Start with:

```text
Through groas, use the GA4 channel group “AI split by assistant” to show AI referral sessions by assistant for the last 90 days. List the top landing pages, sessions, key events and session key event rate. Keep the reporting window consistent and flag missing data rather than estimating it.
```

Then compare visits with citations:

```text
Compare those landing pages with the pages AI answers cite for our tracked prompts. Where do the two lists differ? Separate pages that are cited without recorded visits from pages that receive AI visits but do not appear in the tracked citations.
```

That comparison makes [why ChatGPT and Perplexity cite some pages and not others](https://groas.com/post/how-chatgpt-and-perplexity-actually-choo) a question about your own pages rather than somebody else’s theory.

![Leaky AI traffic bucket losing Direct visits while a measuring cup catches identifiable ChatGPT visits](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/369cd720-9c8f-44fd-a601-e63bb54b6688.png)

Visits and citations do different jobs. A page can appear in ten answers and receive zero clicks. Another can receive ChatGPT visits while Perplexity cites a competitor.

Through [groas’s AI mention and citation workflow](https://groas.com/post/track-brand-mentions-in-chatgpt-claude-and-perplexity-from), your assistant can compare the GA4 sessions with the AI visibility data groas collects around the clock. That saves the two-CSV export and the ritual squinting afterward.

**Expected result:** a shortlist of visited pages, cited pages and mismatches worth investigating.

**Common mistake:** treating your tracked prompts as every answer an assistant gives. **Compare the two datasets without pretending either is complete.**

## Step 7: Fix one landing page before chasing more visits

Return to the exploration. Find a page that receives AI traffic but performs poorly on the action you want visitors to take. Compare it with the same page’s organic traffic over the same dates.

For example, suppose ChatGPT sends 400 sessions to a pricing page with a 0.8% session key event rate, while organic traffic converts on that page at 2.4%. That is a reason to inspect the page, not proof that attribution needs another dashboard.

I start with three checks:

1. Does the opening answer the question that brought the visitor there?
2. Is supporting proof visible within one scroll?
3. Is the next action obvious without hunting through navigation?

**Change one thing on a page AI visitors already reach.** Start with the CTA if it is unclear, or the opening if it fails to deliver on the likely question.

Ask your assistant to propose the edit first. Review it, then explicitly approve publication through groas. Changes are logged with their reasons and can be undone in one step. Autopilot stays off until you enable it, but that setting is not a substitute for a clear approval instruction.

**Expected result:** one deliberate page change with a recorded reason, not a site-wide rewrite prompted by a small table.

**Common mistake:** declaring the channel a failure because one landing page converts badly. Inspect what the visitor encounters before buying more traffic to send there.

## Step 8: Verify the setup, then repeat the useful part monthly

Reopen `Reports > Acquisition > Traffic acquisition` and select `AI split by assistant`. Confirm that known assistant sources appear in the correct rows for your historical reporting window. Then reopen the saved exploration and confirm that its filter includes only `AI:` channels.

**That is the verification: known sources classify correctly, and the landing-page report carries that classification through to key events.** A populated table alone is not enough if it is the wrong table.

Once a month:

1. Record sessions and key events by assistant.
2. List the top five landing pages and their session key event rates.
3. Note which tracked cited pages receive no recorded visits.
4. Pick one page to improve.
5. Keep the same attribution caveat beside the numbers.

For an outside check, use [the monthly routine combining GA4, Search Console branded clicks, a how-did-you-hear-about-us form and a 30-to-50-prompt tracker](https://perceptric.com/blog/ai-search-attribution/). Those signals add context; they do not manufacture missing GA4 sessions.

After the first page edit, wait two weeks and rerun the first groas prompt. Compare the same metrics, while remembering that a before-and-after movement is not proof by itself.

The first change once the setup works: **fix the CTA on a high-traffic AI landing page that converts below its organic rate.** Do that before adding more assistants to the regex.

Build the group. Save the exploration. Fix the page. Some traffic really is invisible to GA4. The traffic already sitting under Referral does not need another attribution debate. It needs a better report.

## Frequently Asked Questions

### How do I see ChatGPT traffic separately in GA4 instead of it showing up as Referral?

Create a custom channel group in GA4 with one channel per assistant, using a Source matches regex condition such as chatgpt\\.com|chat\\.openai\\.com for ChatGPT. Drag these channels above Referral, Organic Search and the built-in AI Assistant channel, because GA4 assigns traffic to the first channel it matches.

### Which AI assistants can I split into their own GA4 channels?

The setup in the article creates separate channels for ChatGPT, Perplexity, Gemini, Claude and Copilot, so each assistant gets its own row instead of being lumped into one combined AI bucket. Deepseek and Grok are also worth searching for in your Traffic acquisition report, since your own recorded source values should decide the final list.

### Why shouldn't I just match anything with 'ai' in the source name when building a GA4 rule?

Because 'ai' is a substring, not an attribution strategy. A rule that matches anything containing 'ai' can collect unrelated tools and .ai domains along with the assistants you meant to measure. Instead, search your Traffic acquisition report for specific source values like chatgpt.com or perplexity.ai and build rules from what your property actually records.

### Does a new GA4 channel group work on past traffic or only future sessions?

Custom channel groups apply retroactively, so sessions GA4 already recorded get reclassified as soon as you save the group. You cannot, however, recreate attribution signals GA4 never received, such as sessions that arrived without a referrer or source tag.

### My new AI channel row in GA4 is empty—did I set it up wrong?

Not necessarily. A rule creates a category, not visitors, so if your property recorded no sessions from that assistant the row stays empty. Check that the report uses your new group, that the date range covers the sessions, and that the channel sits above Referral in the group; but remember a custom group cannot recover Direct sessions that contain no assistant source.

### Does GA4 capture all traffic that AI assistants send to my site?

No. These reports show identifiable AI-referred sessions, not all visits influenced by AI. App opens and copied-and-pasted links can arrive without a referrer, and without a referrer or a source tag the channel group has nothing to match. Crawlers like GPTBot that do not run your tag are also not measured as visitor sessions.

### What should I do if ChatGPT sends traffic to a page that barely converts in GA4?

Compare that page's key event rate with its organic rate over the same dates, then inspect what the visitor encounters: whether the opening answers the likely question, whether proof is visible within one scroll, and whether the next action is obvious. Change one thing, such as an unclear CTA, rather than declaring the channel a failure or buying more traffic.

## Run Your Marketing On groas

Plug ChatGPT, Claude or any AI agent into groas and let it do the work of a whole marketing team: $19 a month flat with every feature included, and autopilot whenever you’re ready.

[Start For $19](https://groas.com/pricing)

[Or have groas run it for you](https://groas.com/done-for-you)

## Structured data

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://graph.groas.com/entity/groas","name":"groas","url":"https://groas.com/","description":"groas is the marketing infrastructure for your own AI: it connects your AI to all your marketing and gives it proprietary marketing data collected 24/7. Plug Claude, ChatGPT or any AI agent into groas and run all your marketing from it, for a tiny fraction of the usual cost, with the groas app there whenever you want to see more. It is the layer ChatGPT, Claude and any AI assistant run a business’s online marketing on. Through groas an assistant can do anything you could do natively in Google Ads, Bing Ads, Meta Ads and ChatGPT ads, on your website and in AI search, and, where the owner switches it on, can run connected campaigns by itself, so AI agents do the work a whole marketing team used to. groas also gives those agents large-scale proprietary marketing data it collects around the clock, on any schedule the owner chooses: every ad competitors run on Google and Meta, their landing pages and full funnels with the offers and prices in them, Reddit customer research, AI search answers from ChatGPT, Google AI Overviews, Gemini, Claude and Perplexity, and SEO data from Semrush and Ahrefs, backlinks included ($19 a month, flat, with everything included, for unlimited teammates on one shared workspace and unlimited ad accounts and websites, delivered as an MCP server). Separately, its done-for-you service has senior people and proprietary quantitative systems run paid ads, SEO and AI search for businesses, and white label for agencies, from $5,000 a month.","logo":{"@type":"ImageObject","url":"https://groas.com/icon-512.png","width":512,"height":512},"sameAs":["https://www.linkedin.com/company/groas/"]},{"@type":"WebSite","@id":"https://groas.com/#website","name":"groas","url":"https://groas.com/","inLanguage":"en-US","publisher":{"@id":"https://graph.groas.com/entity/groas"}},{"@type":"WebPage","@id":"https://groas.com/post/tracking-traffic-from-chatgpt-and-other-ai-tools-in-ga4#webpage","url":"https://groas.com/post/tracking-traffic-from-chatgpt-and-other-ai-tools-in-ga4","name":"Find Your ChatGPT Traffic in GA4—and See Which Pages Convert","description":"Build a custom GA4 channel group for ChatGPT and other AI assistants, find their landing pages and conversions, and understand what the reports miss.","inLanguage":"en-US","isPartOf":{"@id":"https://groas.com/#website"},"about":{"@id":"https://graph.groas.com/entity/groas"},"primaryImageOfPage":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/4b76dcf2-d8c9-48f2-a990-c7a165595de9.png"},"breadcrumb":{"@id":"https://groas.com/post/tracking-traffic-from-chatgpt-and-other-ai-tools-in-ga4#breadcrumb"},"dateModified":"2026-11-19T14:32:53.732Z","mainEntity":{"@id":"https://groas.com/post/tracking-traffic-from-chatgpt-and-other-ai-tools-in-ga4#article"}},{"@type":"BreadcrumbList","@id":"https://groas.com/post/tracking-traffic-from-chatgpt-and-other-ai-tools-in-ga4#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://groas.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://groas.com/blog"},{"@type":"ListItem","position":3,"name":"Find Your ChatGPT Traffic in GA4—and See Which Pages Convert","item":"https://groas.com/post/tracking-traffic-from-chatgpt-and-other-ai-tools-in-ga4"}]},{"@type":"BlogPosting","@id":"https://groas.com/post/tracking-traffic-from-chatgpt-and-other-ai-tools-in-ga4#article","url":"https://groas.com/post/tracking-traffic-from-chatgpt-and-other-ai-tools-in-ga4","mainEntityOfPage":{"@id":"https://groas.com/post/tracking-traffic-from-chatgpt-and-other-ai-tools-in-ga4#webpage"},"isPartOf":{"@id":"https://groas.com/blog#blog"},"headline":"Find Your ChatGPT Traffic in GA4—and See Which Pages Convert","description":"Build a custom GA4 channel group for ChatGPT and other AI assistants, find their landing pages and conversions, and understand what the reports miss.","datePublished":"2026-11-19T14:32:53.629Z","dateModified":"2026-11-19T14:32:53.732Z","image":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/4b76dcf2-d8c9-48f2-a990-c7a165595de9.png"},"author":{"@id":"https://groas.com/author/alexander-perelman#person"},"publisher":{"@id":"https://graph.groas.com/entity/groas"},"keywords":"assistant, chatgpt, pages, traffic, ga4, channel, source, group","wordCount":2130,"inLanguage":"en-US"},{"@type":"Person","@id":"https://groas.com/author/alexander-perelman#person","name":"Alexander Perelman","jobTitle":"Head Of Product @ groas","description":"My background includes Goldman Sachs and Stanford Computer Science.","image":"https://groas.com/media/blog/4f17cac3a81acc224cc1b2cfab8f94bbc295a3089d13e8421125771ef8d4064f.jpg","worksFor":{"@id":"https://graph.groas.com/entity/groas"},"sameAs":["https://www.linkedin.com/in/alexander-433793253/"]},{"@type":"FAQPage","@id":"https://groas.com/post/tracking-traffic-from-chatgpt-and-other-ai-tools-in-ga4#faq","mainEntity":[{"@type":"Question","name":"How do I see ChatGPT traffic separately in GA4 instead of it showing up as Referral?","acceptedAnswer":{"@type":"Answer","text":"Create a custom channel group in GA4 with one channel per assistant, using a Source matches regex condition such as chatgpt\\.com|chat\\.openai\\.com for ChatGPT. Drag these channels above Referral, Organic Search and the built-in AI Assistant channel, because GA4 assigns traffic to the first channel it matches."}},{"@type":"Question","name":"Which AI assistants can I split into their own GA4 channels?","acceptedAnswer":{"@type":"Answer","text":"The setup in the article creates separate channels for ChatGPT, Perplexity, Gemini, Claude and Copilot, so each assistant gets its own row instead of being lumped into one combined AI bucket. Deepseek and Grok are also worth searching for in your Traffic acquisition report, since your own recorded source values should decide the final list."}},{"@type":"Question","name":"Why shouldn't I just match anything with 'ai' in the source name when building a GA4 rule?","acceptedAnswer":{"@type":"Answer","text":"Because 'ai' is a substring, not an attribution strategy. A rule that matches anything containing 'ai' can collect unrelated tools and .ai domains along with the assistants you meant to measure. Instead, search your Traffic acquisition report for specific source values like chatgpt.com or perplexity.ai and build rules from what your property actually records."}},{"@type":"Question","name":"Does a new GA4 channel group work on past traffic or only future sessions?","acceptedAnswer":{"@type":"Answer","text":"Custom channel groups apply retroactively, so sessions GA4 already recorded get reclassified as soon as you save the group. You cannot, however, recreate attribution signals GA4 never received, such as sessions that arrived without a referrer or source tag."}},{"@type":"Question","name":"My new AI channel row in GA4 is empty—did I set it up wrong?","acceptedAnswer":{"@type":"Answer","text":"Not necessarily. A rule creates a category, not visitors, so if your property recorded no sessions from that assistant the row stays empty. Check that the report uses your new group, that the date range covers the sessions, and that the channel sits above Referral in the group; but remember a custom group cannot recover Direct sessions that contain no assistant source."}},{"@type":"Question","name":"Does GA4 capture all traffic that AI assistants send to my site?","acceptedAnswer":{"@type":"Answer","text":"No. These reports show identifiable AI-referred sessions, not all visits influenced by AI. App opens and copied-and-pasted links can arrive without a referrer, and without a referrer or a source tag the channel group has nothing to match. Crawlers like GPTBot that do not run your tag are also not measured as visitor sessions."}},{"@type":"Question","name":"What should I do if ChatGPT sends traffic to a page that barely converts in GA4?","acceptedAnswer":{"@type":"Answer","text":"Compare that page's key event rate with its organic rate over the same dates, then inspect what the visitor encounters: whether the opening answers the likely question, whether proof is visible within one scroll, and whether the next action is obvious. Change one thing, such as an unclear CTA, rather than declaring the channel a failure or buying more traffic."}}]}]}
```
