E1 · The key event
40 minPick the action that matters, fire the event with the source page, and mark it as a key event.
Done when: you clicked the button and the event showed up in the Realtime report, with the source page.
Lesson 7 · 18 min
Search Console shows who arrived from search. It doesn't say what the person did afterward, or who came from an AI assistant. That's what analytics is for: a conversion goal with the source page and a channel of its own for visits coming from ChatGPT, Perplexity, Copilot and the like. Some of them land in "Direct"; the lesson shows why.
Start the lesson
Goal: create a conversion goal with the source page and a channel of its own for visits coming from AI assistants in GA4.
Click each block.
The AI number in GA4 is a floor: what has a marked source. The rest is hidden in Direct.
Menu names change over time; look for the name of the function. Click each step.
Pick an action that shows real interest: joining the community, asking for a quote, downloading the material.
One well-chosen goal is worth more than ten events nobody looks at.
The method includes the "Join the community" event with the source page. In INEMA's analytics (Plausible), this goal was still listed as pending in October 2026. The goal is the part that most often gets pushed back; put it on your calendar.
Fire an event when the action happens, and mark that event as a key event in the GA4 admin.
Check in the Realtime report that it shows up when you click it yourself.
In the admin, look for Channel groups and create a custom group based on the default.
Add the "AI Assistants" channel with the source rule from the regex below, and place it above Referral; the order decides which rule catches the visit.
Cross channel and landing page with the key event. Ask: which page brings people who convert?
Don't compare your number with studies: ChatGPT's share of AI traffic ranges from 63% to 92% depending on the sample.
Templates to copy. Swap what is between < > for your own.
chatgpt\.com|perplexity|copilot|gemini\.google|claude\.ai
document.querySelector('<seletor do botão>').addEventListener('click', function () {
gtag('event', '<entrar_comunidade>', { pagina_origem: location.pathname });
});| month | channel | visits | conversions | top converting page | |---|---|---|---|---| | <mm/aaaa> | Organic Search | <n> | <n> | </pagina/> | | <mm/aaaa> | AI Assistants | <n> | <n> | </pagina/> | | <mm/aaaa> | Direct | <n> | <n> | </pagina/> |
| channel | visits | conversions |
|---|---|---|
| Organic Search | 420 | 9 |
| AI Assistants | 35 | 3 |
| Direct | 310 | 4 |
Made-up numbers to teach the reading. Few AI visits, but a high conversion ratio: it's worth looking at which pages they opened.
No GA4? The same applies to Plausible or another analytics tool: goal + source.
Pick the action that matters, fire the event with the source page, and mark it as a key event.
Done when: you clicked the button and the event showed up in the Realtime report, with the source page.
Create the custom channel group with the "AI Assistants" channel above Referral.
Done when: the group shows up in the acquisition reports; if there was already a visit from chatgpt.com or perplexity.ai, it is in the new channel, not in Referral.
The explanation appears after your answer.
Question 1 of 4
GA4 shows 35 visits from AI assistants in the month. Is that the total that came from AI?skill
Question 2 of 4
Why does the AI channel need to sit above Referral?
Question 3 of 4
One study says ChatGPT is 92% of AI traffic; another says 63%. Which one should you use as a target?
Question 4 of 4
Why does the goal need the source page?
Pick an answer. The explanation shows up after you try.