How to set up conversion tracking you can trust
Build measurement that counts real enquiries rather than button taps so your bidding and your budget decisions rest on something you can reconcile.
Three systems and three different answers
Suppose Google Ads reports sixty-two conversions for the month. Analytics reports forty. Your inbox holds eleven enquiries you would recognise as real. Every one of those numbers is produced correctly by the system reporting it. They disagree because each counts a different event over a different window with a different idea of who the visitor was.
The cost of the disagreement is not confusion. It is that automated bidding spends your money chasing whichever event you declared a conversion. Declare the wrong one and the platform gets very good at buying it.
What it costs and what it will not do
Tracking does not increase enquiries. It changes nothing about your traffic on the day it goes live. It also cannot look backwards. Events are recorded from the moment the tag fires so a setup finished in October tells you nothing about September. And it will not fully resolve attribution. Calls taken on a personal mobile and walk-ins and a buyer who saw the ad on a laptop then bought on a phone stay partly unknowable.
The cost is a one-off block of configuration work plus a smaller permanent tax. Someone must retest the tags every time the site changes. You will need developer access or a tag manager container and permission to edit it. If the work is bought rather than done in-house then service fees raised in India attract GST at 18% on top of the fee. An analytics and measurement setup is published with a written scope so you can see which of these pieces sit inside the engagement.
Who can skip this
If you receive a handful of enquiries a month you do not need a measurement stack. You need a notebook. At that volume no statistical difference between two campaigns will ever be detectable and the tracking becomes a project that replaces selling.
Skip it also if every order arrives by one route you already understand. A business where the owner answers every call and knows every customer by name is already fully instrumented. Spending on dashboards there buys a worse version of what you have.
And skip it if nobody will own it. Tracking decays. Tags break silently when a developer ships a new form. An unowned setup produces numbers that are wrong without announcing it and a confidently wrong number is more expensive than no number.
How to build it so it holds
Pick one primary conversion and only one. The action that a salesperson would call a lead. A submitted enquiry form or a connected call or a started WhatsApp conversation. Everything else is a secondary event you may observe but never optimise towards.
Fire that event from the strongest available signal. A server-side confirmation or a CRM record beats a browser event because it survives ad blockers and reloads. Where you must rely on the browser then use a distinct thank-you page rather than a click listener. A click listener fires when someone taps. It has no idea whether the form passed validation.
Then make the records joinable. Consistent UTM parameters on every paid link. A hidden source field captured on the form and written into your CRM. Where sales close offline import the won deals back into the ad platform so bidding learns from revenue rather than from form fills. Test every tag with a real submission before you trust it and retest after each site release.
Judging whether the numbers are honest
The test is reconciliation. Once a week put the platform conversion count beside the CRM record count beside the number of enquiries a human would call real. A stable gap is fine. A gap that moves is a broken tag or a duplicated event.
The metric that flatters is total conversions and the conversion rate built from it. Both inflate the moment micro events are counted. A site reporting a twelve per cent conversion rate is usually counting scrolls. The metric that matters is cost per qualified enquiry and after that cost per won deal.
The common mistake
The expensive error is marking every click as a conversion. Phone icon taps and WhatsApp button taps and PDF downloads all get the conversion label because each one feels like interest. Smart bidding then optimises to the cheapest of them and the cheapest is always the accidental tap on a mobile. Spend drifts to placements full of people who tap and leave. The account reports a falling cost per conversion while the inbox goes quiet.
The second version is counting the same enquiry twice. A thank-you page that a visitor can reload and a form event that also fires will both report. Deduplicate on a transaction or lead identifier.
The consent question
India's Digital Personal Data Protection Act governs how personal data is collected and used and its framework rests on giving clear notice and obtaining consent for a stated purpose. Tracking setups that write identifiers or capture contact details sit inside that scope. The practical shape is a visible notice and a privacy policy that names what is collected and why and a mechanism for refusal that actually suppresses the tags. Rules are notified separately so a qualified professional should confirm what applies to your business before you rely on a particular configuration.
This guide explains how something works. It is not legal, tax or financial advice, and rules change. Confirm anything regulatory with a qualified professional before you act on it.