Click-to-WhatsApp ads tracking
Every CTWA lead keeps its ad id.
A click-to-WhatsApp ad drops the lead into a chat with nothing attached. Modus reads the ad reference off that first message, keeps it on the contact through qualification to the order, and — if you opt in — reports the sale back to Meta on your own WhatsApp token.
- The ad id captured off the first WhatsApp message, automatically
- Cost per paying customer for every CTWA ad, not cost per chat
- Optional Conversions API feed reports real sales back to Meta
Today
What it looks like right now.
Click-to-WhatsApp leads land in a chat with no campaign attached, so the trail ends at "hi".
Ads Manager counts the conversation started and stops — it never sees whether the buyer paid.
The cheap ad with 300 chats gets scaled; the one that quietly closed five deals gets cut.
Meta's optimiser is learning from conversation starts, not from customers, so it chases the wrong people.
Where the money went
Same ad spend. One closed nothing, one closed five.
Two click-to-WhatsApp creatives, the cost Ads Manager reports, and the cost per paying customer Modus computes because the ad id survived to the order. Figures are illustrative.
How the attribution worksAd campaign performance
Ad
Ad platform sees
Modus sees
Offer Reel
Reel · broad audience
₹27 / chat
“Most conversations”
300
chats
14
qual.
1
orders
₹1.2L
revenue
Case-Study Video
Video · interest-targeted
₹165 / chat
“Fewest conversations”
52
chats
28
qual.
5
orders
₹8.9L
revenue
300 conversations at ₹27 closed one order. 52 at ₹165 closed five.
The agent
What it does on every enquiry.
Ad reference capture
The click-to-WhatsApp ad id (and its referral payload) is read off the inbound message and written to the contact on the spot.
Carried to the order
The id rides the lead through qualification, scoring and the pipeline, so the closed order knows which ad started it.
Cost per paying customer
Read-only spend from the Meta API meets closed revenue from your CRM — real CAC and ROAS per CTWA ad and ad set.
Conversions API feedback
An opt-in feed reports paid orders (and, if you want, qualified leads) back to Meta on your own WhatsApp token — deduped, so a retry never double-counts a sale.
In practice
How it runs.
- 01
Connect Meta read-only
Modus pulls delivery and spend for your click-to-WhatsApp campaigns. No campaign changes.
- 02
The chat carries the ad
Every CTWA lead is tagged with its ad from the first message and worked by the agent.
- 03
Revenue joins back
Closed orders roll up to the ad — and optionally flow back to Meta's optimiser as real conversions.
Questions we get asked
How does Modus know which ad a WhatsApp lead came from?
A click-to-WhatsApp ad attaches a referral block to the first message, including the ad id. Modus reads it there and writes it to the contact before the conversation goes any further, so nothing depends on the customer remembering where they clicked.
Does this need the ads_management permission?
No. Reporting works on a read-only ads_read token. The optional Conversions API feedback runs on your WhatsApp token and is independent of the ad-account permissions.
What if the lead messages again weeks later?
The ad id is stored on the contact from first touch. Later orders from the same contact still attribute to the ad that originally produced them — first-touch credit, consistently applied.
Can it feed conversions back to Meta?
Yes, opt-in. Modus sends paid orders (and qualified leads if you choose) to Meta's Conversions API on your own token, with a dedupe key so a retried send is never counted twice.
Stop guessing which enquiries were worth it.
One agent works every lead on your own number and your website — and every deal it closes is traced back to what produced it. We handle the setup.