FREEFirst project with us? Your landing page design is on the house.See the offer

Chapter 4 of 6

Events that matter

Forms, booked calls, clicks, UTMs and an AI assistants channel group.

6 min readUpdated 2026-11-16
All chaptersChapter 4 of 6
  1. 01What to track and why
  2. 02Google Tag Manager and GA4 setup
  3. 03Consent done right
  4. 04Events that matter
  5. 05Clarity, Search Console and Bing
  6. 06Checking it works and a monthly report

The short answer

Track the moments that show intent, and fire each one from the most reliable signal you have. A lead fires generate_lead once, after the form is accepted. A booked call fires from the booking tool's own success signal, not from the click. Email, phone and button clicks are clicks, and you report them as clicks. Save UTM values with every lead. And give AI assistants their own channel in GA4, so that traffic stops hiding inside Referral.

The two detailed posts behind this chapter are tracking forms in GA4 with Tag Manager and tracking booked calls in GA4.

Form submits

Send the form once, with Tag Manager preview open, and watch what happens. That tells you which signal to use.

What you seeBest signal
You can edit the form codeA data layer push after the server says yes, picked up by a Custom Event trigger
A success message appears, no code accessAn Element Visibility trigger on the success message
Preview shows a Form Submit eventThe Form Submission trigger, with Check Validation on
A thank-you page loadsA Page View trigger on that URL, tested against reloads
The form sits in another service's iframeThat service's own callback or redirect

On Webflow, native forms show a success message on the same page, so the Element Visibility trigger is the usual route when you cannot add code. Point it at the success block with a narrow selector, fire once per page, and turn on Observe DOM changes. Test it at phone width, because a message below the fold may never enter the viewport.

On Astro, you write the submit code, so push the event in the success branch of your fetch call: dataLayer.push({event: 'lead_sent', form_name: 'contact'}). Then a GA4 Event tag named generate_lead fires on that custom event.

Then decide about GA4's own form_submit. If it confuses people or counts newsletter boxes as leads, switch off Form interactions in your stream's enhanced measurement settings. Report leads from generate_lead only.

Booked calls

A click on Book a call shows intent. Only the booking tool knows a call was booked. Use its signal.

  • Cal.com. Its embed events include bookingSuccessfulV2 for a new booking, rescheduleBookingSuccessfulV2 for a reschedule and bookingCancelled. Listen with Cal("on", {action: "bookingSuccessfulV2", callback: ...}) and push call_booked to the data layer. The docs say the booking "might not be confirmed", so decide whether a booking that needs approval counts.
  • Calendly. Its Google Analytics guide lists four events, and only calendly.event_scheduled is a booking. It says real-time data shows at once but full results can take 24 to 48 hours, and that visitors in some regions see a cookie banner inside the embed, so some activity may not be tracked if they reject it.

Decision rule One route per calendar. If the built-in connection and your own listener are both on, one booking shows as two.

Our own site's book_call event fires on a click on a booking link, so we read it as clicks, not calls. That is fine as long as nobody reports it as bookings.

Email and phone clicks

Email and phone links are easy to track and easy to overread. A click on an email address does not mean anyone wrote to you.

Use Tag Manager's Click trigger set to Just Links, which listens only to link elements. Under Some Link Clicks, add a condition on Click URL:

EventTrigger condition
email_clickClick URL starts with mailto:
phone_clickClick URL starts with tel:

You need the built-in Click variables switched on (Variables, Configure) before Click URL shows up. Send the page path as a parameter, so you can see which page the click came from. Never send the address or number that was clicked if it could belong to a person rather than your business.

Main button clicks

Track the handful of buttons that lead to a lead: Get a quote, Book a call, Start a project. One event, cta_click, with two parameters, the button text and the link, tells you which button did the work without a separate event per button.

Keep it to buttons that matter. If every link on the site fires cta_click, the report turns into noise. On a Webflow build, a shared class or a data attribute on the main buttons gives Tag Manager something stable to listen to. On Astro, the button component can carry the attribute, so every new page gets it for free.

UTM parameters on every campaign link

UTM parameters tell GA4 where a visit came from when the referrer cannot. Google's UTM guide says to always use utm_source, utm_medium and utm_campaign, and that values are case sensitive, so lowercase is the safe standard: linkedin and LinkedIn count as two sources.

  • Tag every link you control outside the site: emails, social posts, ads, partner links.
  • Never tag links between your own pages. Our advice: it starts a new source mid-visit and muddles the report.
  • Agree on a short list of mediums, such as email, social, cpc and partner, and keep it in the measurement plan.
  • Read the UTM values when a visitor lands, keep them for the session, and send them with the form, so each lead in your CRM shows its source.
  • If your form saves this data, say so in your privacy policy.

Build links with the free UTM builder so the format stays the same every time.

AI assistants as their own channel

Visits from AI assistants usually land in Referral, mixed in with every other site that links to you. GA4's custom channel groups help has an example for exactly this: create a channel called something like "AI assistants", with a matches regex condition on the source, and place it above Referral.

  1. Go to Admin, Data display, Channel groups, and create a new group. It starts as a copy of the default group.
  2. Add a channel named AI assistants. Set the condition to Source matches regex, with a pattern such as chatgpt|openai|perplexity|gemini|copilot|claude. That pattern is our starting point. Check your own source report and adjust it.
  3. Move the channel above Referral. GA4 assigns traffic to the first channel that matches, so order decides the result.
  4. Save, and use the new group in your acquisition reports.

Google's page says custom channel groups can be applied to reports retroactively, and that standard properties get two custom groups besides the default. It also says to update the pattern when the list of assistants changes.

Read the number as a floor. Some AI tools and apps do not pass a referrer, so some of that traffic will show as direct. For what makes pages worth citing in the first place, see the AEO Readiness Guide.

Takeaways

What to remember from chapter 4.

  • Fire generate_lead once, after the form is accepted.
  • Track calls from the booking tool's success signal, one route per calendar.
  • Email, phone and button clicks are clicks. Report them that way.
  • Lowercase UTMs on every outside link, saved with each lead.
  • Put an AI assistants channel above Referral in a custom channel group.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.