# How to create a GA4 channel for AI traffic

With ever-increasing visits from AI tools such as Perplexity, Chatgpt or Gemini (to name a few), ecommerce managers find it useful to analyze and measure this type of visits separately. In GA4’s default channel grouping, traffic from AI-powered search engines and generative AI models falls under Referral channel - because GA4 treats these tools as external websites (which they technically are!).\
\
But the purchase intent and the funnel position of these visitors is arguably different from a vanilla referral coming from an external blogpost, for example.

That’s why it’s useful to have them in a dedicated channel:

![](https://3956158252-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1QhTbrMraNWciQeDvu1b%2Fuploads%2Fgit-blob-c47bb9667e128d7034469adf8d0093fd8fc1eef2%2F1-dedicated-ai-channel.png?alt=media)

In this case, AI Traffic outperformed both Paid and Organic Social, as well as Display and Paid Shopping campaigns when it comes to ARPU (Average revenue per user).

## AI Traffic custom channel creation

Go to Admin panel (1) and choose Channel groups (2). If you already have a custom channel group (3) we can enrich it with a dedicated AI traffic channel. If not, just click on the “Create new channel group” button.

![admin-new-channel-ga4](https://3956158252-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1QhTbrMraNWciQeDvu1b%2Fuploads%2Fgit-blob-f0e6a3935227f99d59ffacb20db59af89e699904%2Fscreenshot-2025-07-15-at-11.36.38.png?alt=media)

Both options will open a dialog box like the one shown below. Here, you can name your new channel group and add channels by clicking the "Add new channel" button:

![new-channel-group-ga4](https://3956158252-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1QhTbrMraNWciQeDvu1b%2Fuploads%2Fgit-blob-b3d467c98d6db0e9091c10cca5d3e2d0820bd633%2Fscreenshot-2025-07-15-at-11.38.24.png?alt=media)

## Define the AI traffic

Defining the traffic can be done multiple ways. In this example, we’re going to use Source as a rule.

![name-channel-rule-ga4](https://3956158252-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1QhTbrMraNWciQeDvu1b%2Fuploads%2Fgit-blob-8975a3358a6b0e2e3dfdb22a09def686acdecf1a%2F6-name-and-define-channel.png?alt=media)

For the Source, we’ll paste the following regex that we extracted from this [excellent AI traffic blogpost](https://kpplaybook.com/resources/how-to-report-on-traffic-from-ai-tools-in-ga4/) by Dana Di Tomaso:

^(?:chatgpt\\.com|chat-gpt\\.org|claude\\.ai|quillbot\\.com|openai\\.com|blackbox\\.ai|perplexity(?:\\.ai)?|copy\\.ai|jasper\\.ai|copilot\\.microsoft\\.com|gemini\\.google\\.com|(?:\w+\\.)?mistral\\.ai|deepseek\\.com|edgepilot|edgeservices|nimble\\.ai|iask\\.ai|aitastic\\.app|bnngpt\\.com|writesonic\\.com|exa\\.ai|waldo)$

Once you hit apply, make sure to **Save** the channel.

![](https://3956158252-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1QhTbrMraNWciQeDvu1b%2Fuploads%2Fgit-blob-47f06a5e07ff18e76b833c58575fce10c1f552db%2F7-overflow-and-save.png?alt=media)

## Reorder channels

Now that we have the AI traffic channel defined we need to make sure it gets checked before another channel captures this traffic. Since GA4 channel grouping works in a “waterfall” method (channels are checked sequentially), we need to reorder the default list.

![](https://3956158252-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1QhTbrMraNWciQeDvu1b%2Fuploads%2Fgit-blob-c65d6d6eb500f2cc30efcd7f3feb78868e15c1d9%2F8-reorder.png?alt=media)

Our newly created AI Traffic channel will be at the very bottom and we need to make sure it goes above (i.e. checked before) Referrals.

![](https://3956158252-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1QhTbrMraNWciQeDvu1b%2Fuploads%2Fgit-blob-7a5a204f0b5156f1709f38a47514140dbc0ab977%2F9-drag-and-drop.png?alt=media)

{% hint style="info" %}
Remember to always save your changes after applying them. This step is critical, especially since the Save button appears at the top of the screen, and it’s easy to miss after scrolling down to our new AI Traffic channel.
{% endhint %}

![](https://3956158252-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1QhTbrMraNWciQeDvu1b%2Fuploads%2Fgit-blob-b07fcb893e294edded1ccde387e8ccc58f37ae2b%2F10-apply-and-save.png?alt=media)

That’s it - you have your custom channels available in standard reports and Explorations, and this time AI Traffic is properly bucketed and ready to be analysed!

![](https://3956158252-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1QhTbrMraNWciQeDvu1b%2Fuploads%2Fgit-blob-47027e013052427e5d3d32f28a53b319993c9006%2F11-dimension-dropdown.png?alt=media)

## Conclusion

Not only the AI Traffic channel creation will make your GA4 reports future-proof, capturing all the incoming AI traffic, but it will cover retroactive data as well. Once we create the new channel, it will apply to previously captured AI traffic.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.littledata.io/google-analytics/behavior/ga4-channel-ai-traffic.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.