Let Your Agent Set Up GA4 Conversion Tracking

You find out which conversions your GA4 property really measures, where inquiries get lost on the way, and which event is still missing as a key event. Your agent reads everything, proposes the change, and only creates it after your "yes".

In GA4, key events used to be called conversions. A key event is an event you mark as important in GA4: an inquiry, a signup, a purchase. Only that mark turns a counted click into a number you can steer campaigns by. By the end of this tutorial you know which key events fire for you, which ones exist only on paper, and which event you mark next. We show every step on our own property for marketing-mcp.honeyfield.at, with real data from October 28, 2026.

What you need

• GA4 connected in your workspace (required). How to do that, and which role your Google account needs, is in Connect Claude to Google Analytics (GA4).
• The "Editor" role in GA4 and write permission in the workspace (for step 4). For reading, "Viewer" is enough. To create a key event, the connected Google account needs "Editor" on the property, and your workspace needs write instead of read for GA4. You set that permission in the portal (app.ads.honeyfield.at).
• A website that sends events (required). Your agent marks events as key events. It doesn't add tracking to your website code. What never arrives, it can't count.

1. Take stock: which key events fire?

First, look at what's already set up and whether it actually delivers data.

Which key events are set up in GA4 for [workspace]?
Show me counting method, creation date, and whether they fired in the last 30 days.

What you get back:

Excerpt
Key event             Counting method  created      firing (30 days)
lead_submit           once per event   2026-07-01   yes
sign_up               once per event   2026-10-22   yes
purchase              once per event   2026-07-01   no   (default, not deletable)

The key events for inquiries and signups deliver data. GA4 creates purchase on its own; it can't be deleted and does no harm. Watch for key events you created yourself that sit at 0: a key event that never receives an event stays at 0 forever.

✓ Checkpoint: You have a list of your key events, and each one shows whether it fires.

Doesn't work? If the agent reports that the workspace has no GA4 property, assign one in the portal first. If a key event shows "not firing" although you're sure there's data: the agent checks the 500 most frequent event names in the period. With a very large number of different events, a rare one can slip through. Then ask specifically for that one event name.

2. What actually arrives in GA4?

Now turn the question around: which events does your website send, marked or not?

Which events arrived in GA4 in the last 30 days?
Mark which of them are key events.

What you get back:

Excerpt
Event                 Key event
page_view
user_engagement
session_start
first_visit
video_play
lead_submit              ✓
sign_up                  ✓

Your agent also gives you the count per event. We leave the numbers out here. Every event we mean as a conversion arrives and is marked. What this list doesn't show: an event that never arrives in the first place. That's what the next step is about.

✓ Checkpoint: You know which events really arrive, and you see which of them are key events.

Doesn't work? If the list is empty, check the time frame and whether the workspace has the right property. The event list only needs read permission in the workspace.

3. Find the gap: the website sends, GA4 sees nothing

Now comes the part no GA4 screen shows you: events your website fires that never land in GA4. You know the event name from the website code, from your developer, or from Tag Manager's preview. On our site, the newsletter form on the blog sends the event newsletter_signup to Tag Manager after every signup. It didn't show up in step 2. So you ask:

Is there a GA4 event tag for newsletter_signup in Tag Manager for [workspace]?
List all GA4 event tags with their triggers.

What you get back:

GA4 event tags (container marketing-mcp.honeyfield.at, live version 9)
  GA4 Event - sign_up               Trigger: CE - sign_up
  GA4 Event - whitepaper_download   Trigger: CE - whitepaper_download
  GA4 Event - video_play            Trigger: CE - video_play
  GA4 Event - sign_up_click         Trigger: CE - sign_up_click
  GA4 Event - lead_submit           Trigger: CE - lead_submit

newsletter_signup: no tag, no trigger.

That's the gap. The website reports every newsletter signup, but nobody in Tag Manager is listening. A key event for newsletter_signup alone would change nothing: it would sit at 0 for good. So the order is always: first the event has to arrive in GA4, then you mark it.

✓ Checkpoint: You found an event your website sends that's missing in GA4, and you know why.

Doesn't work? If no Tag Manager container is connected in the workspace, the agent can't look here. Then check the tags yourself in tagmanager.google.com or connect the container in the portal.

4. Forward the event and create the key event

Now you close the gap in two steps. The agent writes nothing on its own: it shows you the proposal first.

Create a trigger and a GA4 event tag for newsletter_signup in Tag Manager
and publish the version. Then mark newsletter_signup as a key event in GA4,
counting method once per event. Show me the proposal first.

What you get back:

Proposal
  Tag Manager (container marketing-mcp.honeyfield.at)
    Trigger   CE - newsletter_signup          custom event newsletter_signup
    Tag       GA4 Event - newsletter_signup   GA4 event newsletter_signup to the web data stream
    then      create and publish a new version (replaces live version 9)
  GA4 (website property)
    key event newsletter_signup, once per event
Run it? (yes / no)

After "yes":
  Trigger created            ID 35
  Tag created                ID 36, fires on trigger 35
  Version 10 created         15 tags
  Version 10 published       live now
  Key event created          properties/…/keyEvents/…
                             newsletter_signup, once per event

The values after "yes" come from our run on October 28, 2026. Only after your "yes" does the agent write. Tag and trigger only take effect once the version is published. Until then, they sit in the Tag Manager workspace. So ask: "Which version is live in Tag Manager?" For us, version 10 came back. Keep the key event ID from the response: with it, you can delete exactly this key event later.

Once per event or once per session? "Once per event" counts every time it fires. "Once per session" counts at most one per visit, even if someone submits the form twice. For signups and inquiries, "once per session" is often the more honest number. For downloads, where every single one counts, use "once per event". Tell the agent in the prompt which one you want.

✓ Checkpoint: The agent showed you tag, trigger, and key event as a proposal and, after your "yes", reported the key event ID back. The list from step 1 shows newsletter_signup with today's date.

Doesn't work? If Google rejects the creation, the connected Google account usually lacks the "Editor" role on the property. If the agent says it isn't allowed to write, your workspace lacks write permission for GA4. You fix both outside the chat: one in GA4, the other in the portal.

5. Test: does the event arrive?

A new key event starts out as "not firing". That's normal. The GA4 interface then shows "No stream data detected". Now you check whether the chain holds.

How many users are on the website of [workspace] right now?

The agent answers with the number of active users in the last 30 minutes. Open your website in a second window, accept statistics in the cookie banner, and trigger the event yourself. If the number of active users goes up, your visit arrives. Whether your event came with it, you see in the GA4 "Realtime" report under event names. According to Google, a new key event can take up to 24 hours to appear in standard reports. The next day, ask for the list from step 1 again: now newsletter_signup should show "firing: yes".

Cookie banner first. On our website, Tag Manager loads on every visit, with Google's advanced consent mode. Until someone accepts in the banner, statistics and advertising are set to "denied", and the Google tags only send cookieless signals. So accept statistics for your test, or you won't reliably see your visit in Realtime. Visitors who decline are not counted by GA4 like regular visitors.

✓ Checkpoint: Your test visit shows up in Realtime, and the next day the new key event fires.

Doesn't work? If Realtime shows your visit but not the event, it's usually the trigger in Tag Manager: the event name must be spelled exactly the same, underscore included. If Realtime shows nothing at all, first check consent in the cookie banner, then whether an ad blocker is running in your browser.

Three counting traps

GA4 and your CRM never show the same number. In the same 30 days, our portal database stored one inquiry more than GA4 counts as lead_submit. A small gap is normal: anyone who declines in the cookie banner is missing from the regular GA4 numbers. A large gap means something in the chain is broken.

Double conversions from two key events for one action. A typical case: a download form fires two events on submit, such as lead_submit and file_download. If both are key events, a single request counts twice in the "key events" total. The same happens if you keep both sign_up_click (click on "Try for free") and sign_up (completed registration) as key events. So don't ask for the total, ask for the key events one by one, or pick one event per action. If you remove the mark from an event, that only applies to new data: key events already counted stay in the reports (Google Help).

Are there key events in [workspace] that fire together on the same action?
Compare the key events by page over the last 30 days.

The same event from two sources. Our portal also sends lead_submit directly from the server to GA4, as a backup. That lands in a different property than the website events. If both wrote to the same property, every inquiry would count twice. If you run a plugin, server-side tracking, or a second GA4 snippet next to Tag Manager, check exactly this.

Variations

• "Which of my key events never fired in the last 90 days?" (cleans up leftovers)
• "Show me the key events of the last 30 days by traffic source." (which channel brings inquiries)
• "Suggest which events I should mark as key events, but don't create anything yet." (proposal only)
• "Delete the key event [event name]. Show me which one you're deleting first." (ends double counting, after approval)

Honest limit

• Your agent doesn't build website tracking. It reads GA4 and Tag Manager and, after approval, changes tags, triggers, and key events there. It doesn't write code on your website. If the website sends no event, there's nothing to mark.
• Key events count from the moment you create them. Google applies the mark from the time you set it and doesn't change historical data (Google Help). So past events don't become key events retroactively.
• Realtime shows heads, not events. The realtime tool returns the number of active users in the last 30 minutes. Which event is arriving right now, you see in the GA4 "Realtime" report or in Tag Manager's preview.
• Today is incomplete. The tool numbers for "last N days" include today. For clean comparisons, use periods that end yesterday or earlier.
• No double check on creation. The tool doesn't check whether an event ever arrived before it creates a key event. So always have the agent do steps 1 and 2 first.
• Default key events stay. GA4 rejects deleting purchase and other default key events.
• Your approval is the safety net. That the agent asks before writing is its behavior. The server does not check each single change; it only steps in at an unusual number of writes (300 per workspace in 24 hours). Whether the agent may write is decided by your workspace permission and your GA4 role. Read the proposal before you say "yes".

What's next

Your conversions now count what they should. Next, you want to see them every week without asking: in the next tutorial you have a weekly report built that sums up visitors, sources, and key events. → Have Your Agent Build a Weekly Marketing Report

Paid campaigns depend on the same numbers: how clean tracking helps you find wasted budget is shown in Find Wasted Ad Spend and Set Negatives.