Conversion Tracking & Goals

Defining what counts as a conversion for the business

Before opening GA4's settings, answer a simpler question on paper: what action, taken by a visitor, actually moves your business forward? For most small businesses this is a short list — a contact form submitted, a WhatsApp or phone click, a quote request, a booking completed, a newsletter signup that feeds a sales pipeline, or a purchase. It is rarely "a pageview" or "time on site" — those describe attention, not outcome, and no amount of attention on its own pays a bill.

It helps to separate conversions into two tiers. Primary conversions are the direct business outcome — a booking, a purchase, a signed enquiry. Micro-conversions are meaningful steps toward that outcome that are worth watching but are not the finish line on their own — a pricing page view, a calculator used, a brochure downloaded. Tracking both is fine, but never let a micro-conversion get reported or discussed as if it were equivalent to the real thing. A hundred brochure downloads and zero enquiries is not a hundred conversions; it is a leak somewhere between interest and action, and worth investigating precisely because the micro-conversion number looks healthy while the primary one does not.

Different businesses will land on genuinely different answers here, and that is expected — a professional services firm might treat a booked consultation call as the primary conversion, an e-commerce store treats a completed purchase, and a SaaS product might treat a free trial signup as primary with an eventual paid conversion as a second, longer-term outcome tracked separately. The exercise of writing this down explicitly, rather than assuming everyone on the team already agrees, is often more valuable than the technical setup that follows it — it is common for a business owner and their marketing person to have quietly different ideas of what "success" means until the question is asked directly.

Setting up key events in GA4

Once you know what you are tracking, there are two ways to get it into GA4 as a key event. The simplest is when the action is already an automatically-collected event, or close to one — in GA4's admin area, under Events, you can toggle "Mark as key event" on any existing event without touching any code.

For anything more specific — a particular form, a particular button, a particular link — you will generally set up a custom event through Google Tag Manager, triggered by the specific click, form submission, or page visited (for example, a "thank you" page that only loads after a successful form submission is a reliable, code-free way to fire a conversion event, since it does not depend on correctly detecting the form submission itself, only on the visitor reaching a page that can only be reached by completing it). Once that custom event exists and is firing correctly (verify it in Realtime before moving on), mark it as a key event the same way.

Keep the list short. A handful of clearly defined key events that map directly to real business outcomes is far more useful than a long list where some are conversions, some are engagement signals, and nobody can say for certain which is which without checking. A good practical target for most small businesses is somewhere between two and five key events total — enough to cover the genuine paths to conversion (form, call, WhatsApp, booking) without turning every minor interaction into something labelled a "conversion."

Connecting GA4 conversions to Google Ads

If you are running Google Ads campaigns, linking your Google Ads account to GA4 (done from GA4's Admin settings, under Product Links) lets you import key events directly as Ads conversions. This is one of the highest-leverage connections in the whole analytics stack: it means Ads' own bidding algorithms can optimise toward actual business outcomes — enquiries, bookings, purchases — rather than just clicks or landing page visits, which is what happens by default without this link in place.

After linking, import only the key events that represent genuine conversions, not every event in the account. Importing something like a scroll event as an Ads conversion will actively mislead the bidding algorithm into optimising for people who scroll rather than people who buy — a subtle mistake that quietly degrades campaign performance without an obvious symptom pointing back to the cause, since the campaign will still show "conversions" happening, just the wrong kind.

It is also worth deciding, once conversions are imported, whether to count each key event once per visitor session or every time it fires — GA4 offers both counting methods per conversion, and the right choice depends on the action. A purchase should generally be counted every time it happens, since each one represents separate revenue; a newsletter signup is usually more sensible counted once per user, since submitting the same form twice does not represent two separate leads.

Keeping conversion data trustworthy

Conversion value is worth a brief separate mention. GA4 lets you attach a monetary value to a key event, which is straightforward for an e-commerce purchase (the actual order value) but less obvious for a lead-generation business, where a "conversion" is an enquiry rather than a completed sale. A reasonable approach for lead-based businesses is to assign an estimated average value based on typical deal size and close rate, and treat it explicitly as an estimate rather than a precise figure — it is still far more useful for comparing channels against each other than leaving every conversion valued at zero, which makes it impossible to tell a cheap, low-value lead apart from an expensive, high-value one in any report.

• Test every new key event before trusting it. Trigger it yourself, confirm it appears in Realtime, and check it again a day later in the standard reports to make sure it survived the transition from live data to processed reporting correctly.
• Watch for duplicate firing. A poorly configured trigger can fire the same conversion event twice for one action (for example, once on form submit and again on the thank-you page load) — inflating your conversion count without any real change in outcomes, and making every downstream report that relies on that number quietly wrong.
• Revisit the list periodically. Business priorities change — a key event that mattered a year ago may no longer represent real value, and a new one may be missing entirely. A quarterly check-in on the key event list, alongside the monthly dashboard review covered in Chapter 6, is usually enough to keep it current.
• Never treat a micro-conversion as proof of a working funnel. Always check the primary conversion number alongside it — a rising micro-conversion count next to a flat or falling primary conversion count is a warning sign, not a win.