A practical conversion tracking setup guide: the events to track, how GA4, Google Ads and Meta fit together, and how to send real sales outcomes back to your ad platforms.
Search and explore the blog
Explore the blog
Category
Suggested reading
- Conversion Tracking
Meta Conversions API for CRM: Send Site Visits and Bookings Back to Meta for Better Leads
8 min read
- Digital Marketing
MahaRERA QR Code Advertisement Rules: Where It Must Appear and the Penalty
9 min read
- Business Automation
DLT Registration for SMS in India: Headers, Templates and Why Messages Get Blocked
8 min read
Conversion tracking setup is the work of recording each action that matters to your business, such as a form fill, a call or a booked site visit, and tying it to the ad or channel that produced it. Build it in three layers: browser tags, server-side events and outcomes from your CRM. Without them, ad platforms optimise for clicks instead of customers.
The old line about half of advertising spend being wasted, with no way to know which half, lasts because many accounts are set up the same way. They count page views or button clicks, call it tracking, and then judge a campaign on cost per click. This guide shows what to track, how to wire up GA4, Google Ads and Meta, and where data usually goes missing.
What is conversion tracking setup and which events should you track?
A conversion is any action that moves a visitor towards becoming a customer. Tracking it means three things: an event fires when the action happens, the platform records which campaign sent the visitor, and the count reaches a report you trust. Page views and scroll depth are useful context, but they are not conversions.
Start by writing down your funnel in plain words. For a service business it might be enquiry, qualified conversation, quote, booking. For a builder it might be enquiry, call connected, site visit, booking. Each stage you want an ad platform to find more of becomes an event. Keep the list short, because ten events with no clear priority just confuse bidding.
| Event | Where it fires | Why it matters |
|---|---|---|
| Form submit | Thank-you page or form success callback | The main lead signal for most sites |
| Click to call | Tap on the phone number on mobile | Captures buyers who skip the form |
| WhatsApp click | Tap on the chat button | Common for Indian buyers, so count it separately |
| Qualified lead | CRM stage change, sent from the server | Tells the platform which leads are worth finding more of |
| Booking or site visit | CRM stage change, sent from the server | The outcome you actually pay for |
How do you set up conversion tracking in GA4 and Google Ads?
Google Analytics 4 records events, and it calls the ones you care about key events. Google renamed GA4 conversions to key events in 2024, so older guides that say "mark as conversion" describe the same toggle. In Google Ads, a conversion is the measurement that can steer bidding, so the two terms are not interchangeable any more.
The sequence below works for most small sites. Google documents each step in its Analytics Help pages on key events and on how to create or modify key events, so check the current menu names there.
- 1
Install the Google tag once
Add the tag through Google Tag Manager or directly, and confirm it loads on every page including the thank-you page.
- 2
Create the events
Use recommended event names where they exist, such as generate_lead, and make a custom event for click-to-call and WhatsApp clicks.
- 3
Mark the right events as key events
Turn on the key event setting only for the actions that count. Too many key events dilute your reports.
- 4
Link Google Ads and import
Link the Analytics and Ads accounts, then import the key events you want to bid on as conversions.
- 5
Turn on auto-tagging
Auto-tagging adds the click identifier that lets Google match a later outcome back to the original click.
Why does Meta need both the Pixel and the Conversions API?
The Meta Pixel runs in the visitor browser, so ad blockers, browser privacy settings and slow pages can stop an event from reaching Meta. The Conversions API sends the same event from your server. Meta recommends using both, which its documentation calls a redundant setup.
Running both creates a new risk, which is counting one lead twice. Meta handles this through deduplication: the Pixel and the server send the same event name and the same event_id, and Meta keeps one and discards the other. According to Meta developer documentation, the matching event_id needs to arrive within 48 hours of the first event.
If your leads land in a CRM, the server side is also where you can send later stages. Our guide to the Meta Conversions API for a CRM shows how site visits and bookings go back to Meta so the ad system learns from them.
Why should conversion tracking setup not stop at the lead?
A form fill is cheap to count and easy to inflate. Fake enquiries, wrong numbers and duplicate leads all look like conversions to an ad platform, so campaigns that bring many poor leads can look like winners. The fix is to send the later stage, the one that costs you time and money, back to the platform.
For Google Ads, Google says advertisers new to offline import should start with enhanced conversions for leads, which matches outcomes using details such as email rather than relying only on the click identifier. Its help pages also note that offline conversion uploads are moving to the Data Manager API from 15 June 2026, so check which method your tool uses.
The practical requirement is the same on every platform: keep the click or lead identifier with the lead record, and update it when the status changes. A CRM that stores the source and stage on each lead makes this possible. Without that record, you are back to judging campaigns on the form fill alone.
What are the most common conversion tracking mistakes?
Most broken setups fail quietly. The campaign keeps spending, the dashboard keeps showing numbers, and nobody notices that the numbers stopped matching reality. These are the mistakes that appear most often.
- Counting the wrong thing, such as every visit to a thank-you page, including repeat visits and bookmarks.
- Firing the same event from both a tag and a plugin, so each lead is counted twice.
- Skipping consent and privacy handling, then losing data when browsers or banners block tags.
- Relying on last-click attribution only, which gives all credit to the final touchpoint and hides the ads that started the journey.
- Forgetting to retest after a website redesign, a form change or a new landing page.
- Tracking enquiries but never sending site visits or bookings back to the platforms.
How do you check that your tracking works?
Do not trust a green tick in a tag tool. Submit a real test lead from a phone on mobile data, then follow it through every system. In GA4, use DebugView to see the event arrive with the right name. In Google Ads, check the conversion status. In Meta Events Manager, confirm the event shows as received from both browser and server and that deduplication is working.
Then compare three numbers for one week: leads in your CRM, conversions in each ad platform and form submissions on the website. They will not match exactly, because platforms attribute differently and blocked tags drop events, but a gap of more than a small margin is a signal to investigate. Write the check into a monthly routine, because tracking breaks whenever the site changes.
How long does a conversion tracking setup take and what does it cost?
A basic conversion tracking setup for one website, covering the Google tag, GA4 key events and a Meta Pixel, usually takes a day or two of focused work. Adding the Conversions API, a CRM connection and a proper test plan stretches that to one or two weeks, mostly because of waiting for developers and for enough test leads to check. These timelines are rough planning estimates, not fixed figures.
The tools themselves are free to start. GA4, Google Tag Manager and Meta Events Manager cost nothing. The spend is in the time of whoever builds and checks the setup, plus any paid server-side hosting or CRM plan you choose. Treat the work as a one-time build plus a short monthly check, because a conversion tracking setup that nobody reviews tends to drift out of date after a few site edits.
| Stage | What gets done | Rough effort (estimate) |
|---|---|---|
| Basic tags | Google tag, GA4, Meta Pixel on all pages | 1 to 2 days |
| Events | Form, call and WhatsApp events marked as key events | 1 day |
| Server side | Meta Conversions API with a shared event_id | 2 to 5 days |
| CRM outcomes | Qualified, site visit and booking events sent back | 3 to 7 days |
| Testing | Test leads in GA4, Google Ads and Events Manager | 1 to 2 days |
What does a good conversion tracking setup look like in a lead report?
A good conversion tracking setup lets you answer four questions without guessing: how many leads each campaign produced, how many were qualified, how many reached a site visit or sale and what each one cost. When your report can show cost per qualified lead next to cost per lead, budget decisions change quickly. A campaign with a cheap lead and a poor qualified rate loses to a dearer one that brings buyers.
Build the report from your CRM, not from the ad platforms alone. Platforms count what they can see and take credit generously. Your CRM holds the final status of each lead. When the two disagree, trust the CRM and use the gap to find what is broken in the tags.
What should you do next?
Pick one campaign and fix its tracking end to end before touching the others. Define the three events that matter, mark them in GA4, import them into Google Ads, set up the Pixel and Conversions API with a shared event_id, and make sure your CRM stores the source on every lead. After two weeks of clean data, move the next campaign over.
If you want help with the build, Vistrow offers conversion tracking services as part of its digital marketing work, and you can contact the team to talk through your setup. For related reading, see our guide to fake leads from Facebook ads, which shows why counting leads is not the same as counting buyers.
Frequently asked questions
What is conversion tracking setup?
It is the work of recording the actions that matter to your business, such as form fills, calls, WhatsApp clicks and bookings, and linking each one to the ad or channel that caused it. A good setup uses browser tags, server-side events and CRM outcomes, so ad platforms can optimise for real customers instead of clicks.
What is the difference between a conversion and a key event in GA4?
Google renamed GA4 conversions to key events in 2024. A key event is a reporting setting in Analytics. The word conversion now belongs to Google Ads, where it is a measurement that can drive bidding. You mark an event as a key event, link the accounts, then import it into Google Ads.
Do I need the Meta Conversions API if I already have the Pixel?
Meta recommends running both, which it calls a redundant setup. The Pixel can miss events when browsers block it, and the server event fills the gap. Send the same event_id from both so Meta keeps one copy. Advertisers who never send an event through both channels do not need deduplication for it.
How do I track leads that turn into sales?
Store the click or lead identifier with the lead in your CRM, then send the outcome back when the lead reaches a stage such as site visit or booking. Google offers enhanced conversions for leads for this, and Meta accepts server events through the Conversions API. This lets each platform learn which ads bring buyers.
How do I test that tracking works?
Submit a real test lead and watch it appear in GA4 DebugView, Google Ads conversion status and Meta Events Manager. Confirm the event name, the value if you send one and that it counts once. Repeat after any website, form or tag change, because those changes are the usual cause of silent breaks.
Comments