To set up GA4 conversion tracking for a small business, first decide the three or four actions that genuinely mean "a possible customer contacted us", then make sure each one sends a clearly named event to GA4, mark those events as key events, and test them before you trust any report. Most broken setups I see are not technical failures; they are counting the wrong thing, counting the same thing twice, or never testing at all.
This guide is for services and lead-generation websites, not online stores. It walks through the setup in order and ends with a fifteen-minute monthly check. Platform details are as of October 2026; Google changes its interface often, so check the official Analytics Help pages for current steps.
First, the vocabulary: key events and conversions
Google renamed things, and the old tutorials still float around. In GA4 today:
- Event is any interaction GA4 records: a page view, a scroll, a click, a form submission.
- Key event is an event you have marked as important to your business. Google's help page describes it as an event that measures "an action that's particularly important to the success of your business". This is what older guides called a "conversion" inside GA4.
- Conversion now refers to a key event that is shared with a linked Google Ads account so both platforms count it the same way, mainly for measuring campaigns and guiding bidding.
So for most small businesses the job is: create the right events, mark them as key events in GA4, and, if you run Google Ads, turn the relevant ones into conversions there. Per Google's documentation, a standard GA4 property can have up to 30 key events. You will need far fewer than that, and you should.
Step 1: Write down what counts as a lead
Before opening GA4, list the actions on your site that a real buyer takes when they want to talk to you. For a typical services business, that list is short:
- Submitting the enquiry or quote form
- Clicking a phone number (tap-to-call on mobile)
- Clicking a WhatsApp chat link
- Booking a call through a scheduler
- Possibly, downloading a brochure or price list, if your sales team follows up on those
Then separate them into two groups. Primary actions are the ones your sales team would happily pick up the phone for. Secondary actions show interest but are not enquiries: a brochure download, a newsletter sign-up, a visit to the pricing page. Only primary actions should become key events at first. If you mark everything as a key event, your "conversion rate" becomes meaningless and any Google Ads bidding that uses those signals will chase cheap, low-intent actions.
Step 2: Check what GA4 already collects
When you install the Google tag, GA4 can collect several events automatically through enhanced measurement. According to Google's help page, these include page_view, scroll, outbound click, file_download, form_start, form_submit, site search and some YouTube video events. You find the toggle under Admin, Data streams, your web stream, Enhanced measurement.
I usually advise against relying on form_submit alone as your key event. In my experience it can fire when a visitor presses submit even if validation fails, it can miss forms that submit without reloading the page, and it lumps every form on the site together, including the newsletter box in the footer.
Step 3: Choose how each lead action will be detected
There are three common ways to detect a lead action. Pick the most reliable one available for each.
| Method | How it works | Good for | Watch out for |
|---|---|---|---|
| Thank-you page | The form sends the visitor to a unique confirmation URL; you create an event when that page loads | Most contact and quote forms | People bookmarking or revisiting the page; the page being indexed by search engines |
| Tag Manager trigger | Google Tag Manager listens for a successful submission, a click on a tel: link, or a click on a wa.me link | Phone clicks, WhatsApp clicks, forms that do not redirect | Triggers breaking silently after a website redesign |
| Code or plugin event | Your developer, form tool or CMS plugin sends the event directly when the submission succeeds | Schedulers, multi-step forms, custom forms | Plugins sending duplicate events alongside your own setup |
A thank-you page is the simplest and most robust option for a small site. If your form tool supports it, redirect successful submissions to a page like /thank-you-enquiry, keep it out of your sitemap, and add a noindex tag so it does not appear in search results.
Step 4: Name your events properly
Google publishes a list of recommended events, and for lead generation it includes generate_lead, plus later-stage events such as qualify_lead and close_convert_lead. Using Google's recommended names helps GA4 fill in its lead-related reports. Recommended events are not sent automatically; you have to implement them.
A practical naming plan for a small business:
- generate_lead for a successful enquiry form submission, with a parameter such as lead_source set to "contact_form" or "quote_form"
- phone_click for tap-to-call clicks
- whatsapp_click for WhatsApp chat clicks
- book_call for completed scheduler bookings
Use lowercase with underscores, keep names stable once they are live, and write the list down in a shared document. The same discipline applies to your campaign links; my UTM naming conventions guide covers that side, and the free UTM builder keeps tagging consistent.
One honest note on phone and WhatsApp clicks: they record intent, not a completed conversation. Someone may tap the number and hang up. Count them, but do not compare them one-to-one with form leads.
Step 5: Mark the events as key events
Once an event has started arriving in GA4, Google's current steps are: go to Admin, then Events under Data display, find the event, and click the star icon to mark it as a key event. You can also create a new event from an existing one (for example, a page_view where the page location contains your thank-you URL) and switch on "Mark as key event" while creating it. Google notes you need at least Editor access for the first route and Marketer access for creating events.
Two things catch people out. Marking an event applies only from that point forward; it does not rewrite history. And standard reports can take up to 24 hours to show the change, so do not panic if numbers are empty on day one.
Step 6: Test before you trust it
This is the step most setups skip. Testing takes half an hour and saves months of wrong decisions.
- Open GA4's DebugView (under Admin) or use Tag Assistant to preview your site.
- Submit your own form with a test name like "Test – please ignore". Confirm exactly one generate_lead event appears.
- Submit the form with a missing required field. Confirm no lead event fires.
- Tap the phone number and WhatsApp link on a real phone. Confirm each fires once.
- Check the Realtime report a few minutes later.
- Over the next two weeks, compare the GA4 lead count with actual enquiries received. They will rarely match exactly, because of consent choices, ad blockers and people who browse on one device and call from another, but a big gap means something is wrong.
Write down the date you tested and what you checked.
Step 7: Connect GA4 to Google Ads (if you advertise)
If you run Google Ads, link the accounts and decide which key events become conversions in Ads. Google's help pages explain that conversions created from key events are shared between the two platforms so they count the same way. Be selective: import only your primary lead actions as conversions used for bidding. Secondary actions can be tracked for observation but should not steer spend.
If you also run Meta ads, the same principle applies there with its own pixel and events. I compare the two channels for enquiries in Google Ads vs Meta ads for lead generation.
Step 8: Track lead quality, not just lead volume
GA4 can tell you a form was submitted. It cannot tell you the enquiry was a serious buyer rather than a student, a vendor pitch or spam. For many small businesses, that gap is where marketing money leaks.
The simple fix is manual: once a week, mark each enquiry in your CRM or spreadsheet as qualified or not, and note its source (taken from the UTM tags or the "how did you hear about us" field). The more advanced fix is to send qualify_lead and close_convert_lead events back to GA4 from your CRM, which Google's lead generation documentation supports. That usually needs developer help, so start manual and automate only once the manual process is consistent. My analytics and automation work often starts exactly here.
Settings worth checking while you are in there
- Data retention. For standard properties Google offers 2 months or 14 months. This setting affects explorations and funnel reports, not standard reports. Most small businesses should choose 14 months.
- Internal traffic. Define your office IP addresses as internal traffic and filter them, so your team's visits and test submissions do not inflate results.
- Personal data. Google requires that you do not send personally identifiable information, so never pass names, emails or phone numbers in event parameters or URLs.
A fifteen-minute monthly check
- Open the key events report. Does each key event still have data? A sudden zero usually means a website change broke a trigger.
- Compare GA4 leads with enquiries actually received in the month.
- Look at leads by session source and campaign. Are your UTM-tagged campaigns showing up with clean names?
- Check which landing pages produce leads, not just traffic.
- Note any website, form or campaign changes made that month, so next month's comparison makes sense.
If traffic is healthy but this check keeps showing few leads, the problem is usually the website, not the tracking. I cover that diagnosis in website traffic but no leads.
Frequently asked questions
Are key events and conversions the same thing in GA4?
Not exactly. A key event is an event you have marked as important inside GA4. A conversion, in Google's current terms, is built from a key event and shared with Google Ads so both platforms count it the same way. If you do not run Google Ads, key events are what you need.
Should I mark form_submit as a key event?
Only after testing it against real enquiries. It is collected automatically through enhanced measurement, but it can count every form on the site together and may fire in cases you would not call a lead. A dedicated generate_lead event from a thank-you page or confirmed submission is usually more trustworthy.
Can GA4 track phone calls?
GA4 can track clicks on a phone number link, which shows intent to call. It cannot tell you whether the call connected or how long it lasted. For that you need call tracking from a telephony provider, or a manual log kept by whoever answers the phone.
Why don't GA4 leads match my actual enquiries?
Some gap is normal: visitors who decline cookies, ad blockers, people switching devices, and spam submissions all play a part. A small, steady gap is fine. A large or sudden gap usually means a broken trigger, duplicate events, or a form that changed during a redesign.
How many key events should a small business have?
Usually three to five. Enough to cover each genuine way a buyer contacts you, and no more. Secondary actions such as downloads can stay as regular events you look at occasionally.
A low-pressure next step
If you would like a second pair of eyes on your GA4 setup, or want to decide what should count as a lead before anyone touches Tag Manager, a 30-minute strategy session (₹2,999 + GST) is usually enough to map it out. Bring access to your GA4 property and a rough count of last month's enquiries, and we will check whether the two agree.
