How to set up GA4
conversion tracking.

Decide what actually counts

Before touching the interface, write down the small number of things that mean a real person wants to do business with you. For most small businesses that is: a form submitted, a phone number tapped, a booking made, and possibly an email link clicked.

What should not be on the list: page views, scroll depth, time on page, video plays, clicks on the navigation. These are useful diagnostics and they are not conversions. Marking them as key events is how accounts end up reporting hundreds of conversions a month while the phone does not ring.

Step one: make the event fire

There are three common routes, and the right one depends on how your site is built.

• Enhanced measurement. GA4 automatically collects some events, including outbound clicks and file downloads. Useful, but it will not know which of your forms matters.
• A tag manager. Google Tag Manager lets you define a trigger, such as a form submission or a click on a phone link, and send an event without editing the site. This is the usual answer for a site you cannot easily edit.
• Directly in the page. If you control the code, firing an event yourself is the most reliable option, because you can fire it at the exact moment you know the thing succeeded rather than inferring it from a click.

Give events clear, lowercase, consistent names: generate_lead, phone_click, booking_click. You cannot rename historical data later, so decide on a convention now.

Step two: mark it as a key event

In GA4, go to Admin, then Events. Find your event in the list and switch on "Mark as key event". If it does not appear yet, it is because the event has not fired since you created it, which brings us to the part that matters.

Test it before you trust it

This is the step that separates a working setup from one that quietly reports nothing for six months.

1. Open DebugView. In GA4 under Admin. With debug mode enabled, DebugView shows events arriving in close to real time, so you can watch your own submission land.
2. Submit a real enquiry. Fill in the form properly, from a phone if that is how most people arrive. Do not use a shortcut that skips the normal flow.
3. Watch for the event. Confirm it appears, confirm the name is right, and confirm it fires once rather than twice.
4. Check Realtime afterwards. A second confirmation that the data reached the main reporting stream.

Repeat this for every route an enquiry can arrive by. The most common failure is a form that works perfectly and an event that only fires on one of two possible success states.

Thank you pages versus events

Redirecting to a thank you page and counting views of that page is the old approach. It still works and it has one real advantage: it is hard to get subtly wrong.

Event based tracking is more flexible and works with forms that do not redirect, which is most modern forms. The risk is that a click on a submit button is not the same thing as a successful submission, so a click based trigger will count failed submissions as conversions. Where possible, fire on success, not on click.

Phone calls

A tap on a phone link is trackable and is not the same as a call being answered. It is a reasonable proxy for a small business, provided you remember what it is. If phone enquiries are a large share of your business, a call tracking service that records connected calls and their duration will tell you considerably more.

Connecting it to Google Ads

Once key events are working, link the GA4 property to Google Ads and import the key events as conversions. Two cautions.

• Do not double count. If Google Ads already has its own conversion tag for the same action, importing the GA4 version as well will count it twice and distort automated bidding.
• Choose the primary action deliberately. Google Ads optimises toward what you mark as primary. If both a phone tap and a form fill are primary, it will treat them as equally valuable, which they rarely are.

Why your numbers will never match exactly

GA4, Google Ads, Meta and your inbox will all report different figures, and people lose a lot of time trying to reconcile them. They use different attribution models, different time windows, and different rules about what counts. Pick one source as the one you make decisions from, note the others as directional, and move on.

A short checklist

1. List the small number of actions that mean real intent.
2. Make each one fire a clearly named event.
3. Mark each as a key event in Admin, then Events.
4. Test every route with a real submission, watching DebugView.
5. Confirm nothing fires twice.
6. Link Google Ads and import, without duplicating existing tags.
7. Choose which conversions are primary.
8. Re test after any change to the website or the forms.

That last line is the one that keeps a setup honest. Tracking does not break loudly. It breaks silently, usually the next time someone edits the site.