Choosing the few events that matter, naming campaign traffic consistently, and fixing the settings that quietly break small-business reporting
Key takeaway: Most small-business GA4 properties collect plenty of data but measure the wrong outcomes. Picking three to six key events that map to real revenue steps, tagging every campaign link consistently, and fixing two default settings (data retention and consent) will tell you more than any dashboard redesign.
Below: which events to mark as key events, how to name campaign traffic so channel reports stay clean, and the settings that quietly break reporting.
Google Analytics 4 records almost everything as an event: page views, scrolls, outbound clicks, form interactions. That is useful raw material, but it is not a measurement plan. A key event is an event you have told GA4 is important to your business, and it is what the acquisition reports use to show which channels actually lead people to take that action. Google's own documentation describes the purpose plainly: key events let you "measure actions that are important to your business and evaluate the marketing channels that lead users to take those actions" (Google Analytics Help: Mark events as key events).
If you skip this step, your reports default to traffic and engagement metrics. You will know which channel sends the most sessions, but not which one sends enquiries, bookings, or sales. For a small team deciding where the next month's budget goes, that is the difference between a guess and a decision. If you are already comparing channels, our guide to SEO vs paid ads ROI assumes exactly this kind of outcome tracking is in place.
Before you mark anything, list the steps a customer actually takes with your business. Keep it to what you can observe on your website or app. A typical service business might look like this:
An e-commerce store will have a different list: product view, add to cart, begin checkout, purchase. The point is to separate micro actions (signals of interest) from macro actions (outcomes that are worth money). Only the macro actions, plus perhaps one strong micro action, should become key events.
GA4 lets you name events almost anything, but Google publishes a list of recommended events with standard names and parameters. Using those names where they fit keeps your data consistent with Google's reporting and makes the property easier for anyone else to understand later. For lead-generation businesses, the relevant recommended events include:
For online stores, the e-commerce events (view_item, add_to_cart, begin_checkout, purchase) follow the same logic. The later-stage lead events usually happen in a CRM rather than in the browser, so they are sent from your server or CRM integration rather than from a website tag. If that is beyond your current setup, start with generate_lead and add the others when you have the plumbing.
GA4's enhanced measurement collects some events automatically when it is switched on, including form_start (the first time a user interacts with a form in a session) and form_submit (when a user submits a form), plus scrolls and outbound clicks (Google Analytics Help: Enhanced event measurement). These are convenient, but test them on your own forms before you rely on them. Forms built with third-party embeds, multi-step widgets, or AJAX submissions do not always behave the way an automatic listener expects. A dedicated generate_lead event fired on your thank-you page or form success callback is usually more dependable.
Once the events exist, marking them is simple: in Admin, under Data display, open Events and click the star next to the event. You can also create a new key event ahead of time so GA4 treats it as a key event as soon as it starts arriving. Google caps standard properties at 30 key events (50 for Analytics 360), per the key events documentation.
That limit is generous for a small business, and that is the trap. If you star page_view, scroll, and every button click, your "key events" total becomes meaningless and your channel comparisons become noise. A workable rule:
Two details from Google's documentation are worth knowing. First, marking an event affects reporting from that point forward; it does not rewrite history. Second, allow up to 24 hours for a newly marked key event to show in standard reports, although Realtime updates within minutes. So if you set this up on a Monday, do not judge it on Monday afternoon.
Also be aware that if you link Google Ads and enable Ads Personalization, GA4 automatically marks several additional events as key events, including add_to_cart, begin_checkout, session_start, and view_item. If your key-event totals suddenly jump after linking Ads, check the Key events list before assuming performance improved.
When you create a key event you can set a default value and a counting method. Purchases carry real revenue. Leads do not, but you can still assign a planning value based on your own numbers: if roughly one in ten enquiries becomes a customer and an average first order is worth a known amount to you, the expected value of an enquiry is a tenth of that. Use your own CRM data, keep the assumption written down, and revisit it quarterly. The value does not need to be perfect; it needs to be consistent so that channels are compared on the same basis. Our content marketing ROI guide goes deeper into turning these values into return calculations.
On counting method: "once per session" usually suits lead forms, because a user who submits twice in one visit is still one enquiry. "Once per event" suits purchases, where every transaction matters.
Key events tell you what happened. UTM parameters tell GA4 where the visit came from when the source is not automatically detected, such as email newsletters, social posts, QR codes, and partner links. Google's help documentation lists utm_source, utm_medium, and utm_campaign as the parameters you should always include, with utm_term, utm_content, and utm_id as optional extras (Google Analytics Help: Collect campaign data with custom URLs).
The same page recommends a standardised approach: one unique source value per platform, one unique medium value per channel, and a campaign name that matches the actual campaign. In practice, the biggest source of messy reports in small businesses is inconsistency, where one person writes Facebook, another writes facebook.com, and a third writes fb. GA4 treats those as three different sources.
A simple fix is a shared naming sheet that everyone uses before a link goes out:
Do not add UTM parameters to internal links on your own site. Doing so starts a new attribution trail mid-visit and makes your own website look like a traffic source. Google Ads traffic is normally attributed through auto-tagging, so check that setting in your Ads account rather than adding manual tags on top.
GA4's data retention setting controls how long user-level and event-level data is kept for explorations and funnel reports. For standard properties the options are 2 months or 14 months, and Google notes the setting does not affect standard aggregated reports, only explorations and funnel reports (Google Analytics Help: Data retention). If you ever want to build a year-on-year funnel exploration, the shorter setting will stop you. Most small businesses should review this in Admin under Data settings Admin → Data collection and modification → Data retentionrarr; Data retention (the path Google's help page gives), and decide deliberately, taking your own privacy commitments into account.
If your site uses a cookie banner, Google's consent mode passes each visitor's consent choice to Google tags so they adjust their behaviour. When consent is denied, tags do not store cookies and instead send limited cookieless pings; Google Analytics can then use modelling to help fill measurement gaps (Google Analytics Help: Consent mode). Consent mode does not provide a banner itself; it works with your consent management platform. The practical implication: if you added a banner but never connected consent mode, or connected it incorrectly, your key event counts may drop or behave inconsistently, and it will look like a marketing problem when it is a configuration problem. Which consent approach is legally required depends on where your customers are, so take advice specific to your jurisdiction.
Before trusting the numbers, submit your own form, complete a test booking, or place a test order, and confirm the key event appears in Realtime and in DebugView. Then use these reports:
If you are planning campaigns around these numbers, our lead generation tactics guide covers which channels to test once your measurement is trustworthy.
Usually three to six. Google allows up to 30 key events on a standard property, but marking every click or scroll makes channel comparisons meaningless. Mark only the actions that represent real value, such as a lead form submission, a booking, or a purchase.
GA4 records user interactions as events. A key event is an event you have marked as important to your business, which lets GA4 report which channels and campaigns lead users to take that action.
No. According to Google, marking an event as a key event affects reporting from that point forward and does not change historic data. Allow up to 24 hours for it to appear in standard reports.
Google recommends always including utm_source, utm_medium and utm_campaign on campaign links. Use a shared naming list so the same platform and channel are always written the same way.
Vega Marketing helps small and growing businesses set up measurement that ties marketing spend to real enquiries and sales.
Talk to Our Team