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

Chapter 1 of 6

What to track and why

The three questions, the one-sheet plan, key events and naming rules.

6 min readUpdated 2026-11-16
All chaptersChapter 1 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

Before you add a single tag, write a measurement plan: the few questions your team needs answered, the event that answers each one, what fires it, and whether it counts as a key event. Keep it on one sheet. For most marketing sites, that is five to eight events, and only two of them are real outcomes: a lead sent and a call booked.

Everything in the rest of this guide hangs off that sheet. Tag Manager, consent, Clarity and the monthly report all get easier when you know exactly what you are trying to count. If you want the shorter version of the whole setup first, read Marketing site tracking: a setup you can trust. This guide is the longer, working version.

Start with three questions

Most marketing teams need the same three answers each month:

  1. How many leads did we get? Forms sent and calls booked.
  2. Where did they come from? Channel, campaign and, where you can see it, the search query.
  3. What did they read first? The pages people visit before they get in touch.

Write your own version down and share it with whoever reads the reports. Then test every event idea against it. If an event does not help answer one of these questions, and nobody will change a decision because of it, leave it out. Every extra event is one more thing to test after each site change, and one more number that can drift without anyone noticing.

Decision rule If you cannot name the person who will look at a number and the decision it feeds, do not track it yet. You can add an event later in ten minutes. Cleaning a year of confusing data takes much longer.

The one-sheet measurement plan

Here is the sheet we start from on a typical Webflow or Astro marketing site. Copy it into a spreadsheet and change it to fit. The example uses Kookies as the site.

Question it answersEvent nameFires whenKey event?True count lives in
How many leads?generate_leadThe form has been accepted by the serverYesInbox or CRM
How many calls?call_bookedThe booking tool confirms a bookingYesCalendar
Who wanted a call?book_call_clickSomeone clicks a booking linkNoGA4 only
Who wrote to us?email_clickSomeone clicks a mailto linkNoGA4 only
Who called us?phone_clickSomeone clicks a tel linkNoGA4 only
Which buttons work?cta_clickA main call to action is clickedNoGA4 only
What did they read?page_viewBuilt in, no setupNoGA4 only

Add two columns when you build it for real: parameters (for example form_name or button_text) and owner, the person who fixes it when it breaks. The owner column matters more than it looks. Tracking usually breaks quietly, when someone redesigns a form or swaps a booking tool, and an owner is the only thing that makes anyone notice.

Key events versus everything else

In GA4, a key event is an event you mark as important to your business. You mark it in Admin, under Data display, Events, by clicking the star next to it. You can also create one ahead of time, before the event has any data, and GA4 will treat it as a key event once it arrives. A standard property can have up to 30 key events, but you should need two or three.

The reason to keep the list short is honesty. If button clicks and email clicks are key events, your key event count looks three times bigger than your real lead count, and someone will put that number in a board slide. Clicks are useful steps. They are not outcomes.

  • Mark generate_lead and call_booked as key events.
  • Leave clicks, scrolls and page views as normal events.
  • If a newsletter signup matters to you, give it its own event and decide on purpose whether it is a key event.
  • Write the list in the plan, so nobody adds a key event without telling the people who read the reports.

Names that stay readable

Event names are hard to change later, because old data keeps the old name. Pick a style once and stick to it.

  • Use Google's names where they exist. GA4's recommended events reference lists generate_lead for a lead, such as a form. It also lists qualify_lead and close_convert_lead for later stages, but those usually belong in your CRM, not on the website.
  • Lowercase with underscores. call_booked, not CallBooked or call-booked.
  • One event, many forms. Send generate_lead with a form_name of contact, quote or guide. One event with a parameter is far easier to report on than ten events.
  • Say what happened, not where. email_click with a page parameter beats footer_email_click and contact_page_email_click.
  • No personal data. Google's policy does not allow names, emails or phone numbers in Analytics. Keep them out of event values and out of URLs.

The same reference lists value and currency for generate_lead, and says each is needed if you set the other. Leave them out unless you have a lead value your finance team would sign off. A made-up value makes the report look precise when it is not.

What GA4 already counts

GA4's enhanced measurement collects a set of events with no code, once it is switched on for your web stream:

EventWhat it means
page_viewEach page load or history change. Always on.
scrollThe first time a visitor sees 90% of the page height.
click (outbound)A click on a link to another domain.
view_search_resultsA site search results page, read from URL parameters such as q or s.
video_start, video_progress, video_completeEmbedded YouTube videos that support the JS API.
file_downloadA click on a link to a common file type, such as a PDF.
form_start, form_submitForm interaction and submission.

Do not rebuild these by hand. The one to think about is form_submit. A submit is not the same as a lead that arrived: it can fire on a newsletter box, a search field or a form that failed. We report leads from generate_lead only, and chapter 4 explains how to decide whether to keep form_submit switched on.

Where the true count lives

GA4 will almost always show fewer leads than your inbox. Some visitors reject cookies, some block scripts, and some events get lost when a page closes. That is normal, and it is not a bug to chase forever.

So set the rule up front: your inbox or CRM is the true count of leads, your calendar is the true count of calls, and GA4 is the tool for comparing channels, pages and trends. If GA4 shows 70% of your real leads every month, you can still trust it to tell you which channel grew. If the gap jumps from one month to the next, something broke, and chapter 6 shows how to find it.

Decision rule Never report a lead number from GA4 alone. Report the real number from the inbox or CRM, and use GA4 to explain where those leads came from.

Takeaways

What to remember from chapter 1.

  • Write the questions first, then pick events that answer them.
  • Mark only real outcomes, a lead sent and a call booked, as key events.
  • Use Google's names where they exist, such as generate_lead, with a form_name parameter.
  • Your inbox, CRM and calendar are the true counts. GA4 is for comparing channels and pages.

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.