How to track the WhatsApp enquiries that come from ads
Connect click-to-WhatsApp conversations back to the campaign that paid for them using methods that range from a prefilled code to the full API.
A hundred chats and no idea where they came from
Click-to-WhatsApp ads are the most natural paid format in India. The buyer taps and lands in an app they already live in. Then your phone fills with messages that say Hi and nothing else and you have no way to tell which campaign bought each one.
The gap matters because the budget decision depends on it. Three ad sets are running and one of them is producing the enquiries that close. Without a link between conversation and campaign you are left scaling on gut feel or on the conversation counts the platform reports which are not the same thing as business.
What this costs and what it excludes
No method here gives perfect attribution. Someone can save your number from an ad and message a week later from a different device and that chat will look organic. Treat the exercise as recovering most of the picture rather than all of it.
The free WhatsApp Business app excludes the hooks that proper tracking needs. It has no API and no way to receive a campaign identifier. Moving to the WhatsApp Business Platform means a provider in between and that introduces two separate costs. Meta charges per conversation on its own published schedule and the provider charges a platform fee. Service fees raised in India attract GST at 18% on top. A scoped WhatsApp marketing engagement publishes what is covered so you can see which pieces you would still be buying directly from Meta or a provider.
Who should not build this
If you run one campaign to one number then you already have attribution. Every chat came from the one place. Build nothing.
If you receive a handful of chats a month the honest instrument is asking. Add a line to your first reply that asks where they found you and write the answer in a sheet.
Do not move to the API if nobody will maintain it. The platform brings template approvals and opt-in records and a twenty-four hour window rule that governs when you may message first. A business that cannot keep that tidy will have its sending restricted and will have replaced a working phone with a broken system. Retail counters and clinics where staff reply from a shared handset are usually better off with separate numbers per channel than with an API.
Four ways to do it in rising order of effort
The simplest is a prefilled message. A click-to-WhatsApp ad lets you set the text the user sends first so give each campaign its own wording or a short code. The code arrives with the message and costs nothing to implement. Buyers do sometimes delete the text before sending so expect leakage. Next is separate numbers. One per channel or per major campaign. Crude and completely reliable and it works on the free app. Numbers are scarce so the method does not scale past a few.
Third is a landing page in the middle. Run traffic to a page carrying UTM parameters and put a wa.me link on it. The page records the source and passes it into the chat text or your CRM. You gain full campaign detail and lose the conversions that abandon at the extra step. Fourth is the API route. Meta passes a click identifier with conversations that originate from an ad and a provider on the Business Platform can capture it against the contact and report conversions back. This is the only method that joins a closed sale to an ad set automatically. It needs the migration described above and someone to own it.
Judging the results
Count qualified conversations and nothing else. A qualified conversation is one where the person stated a need. Everything before that is a tap. Then track cost per qualified conversation by campaign and cost per closed sale once your pipeline is long enough to show it.
The metric that flatters is conversations started. It is reported generously and it is cheap to buy. Message volume flatters too since a confused buyer sends more messages than a convinced one.
The common mistake
The expensive error is letting the campaign optimise towards conversations started. Meta will do exactly as instructed and find the audience most likely to tap a green button. Those people are reachable very cheaply and most of them will send one message and vanish. The cost per conversation drops and the report looks like progress while your team spends its day answering nobody. Feed qualified conversations back as the conversion event instead even if that means a manual upload each week.
The quieter error is tracking the source and then not using it. A campaign field in the CRM that nobody reports on is a cost with no return.
Consent is part of the design
WhatsApp is a permission channel by policy and by law. Meta's business rules require an opt-in before you initiate messages and India's Digital Personal Data Protection Act governs how the contact details and chat records you collect may be used. The mechanism to build is a record of when and how each number consented and a working way to stop. A qualified professional should confirm what applies to your business before you use ad-sourced contacts for later marketing.
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.