How to track WhatsApp campaigns and identify which ads actually drive sales
Investing in paid traffic for WhatsApp is relatively straightforward. The challenge begins when a company tries to answer questions such as:
- Which campaign did this lead come from?
- Which ad started this conversation?
- Which creative is bringing in the most qualified leads?
- How many conversations actually became opportunities?
- Which campaign generated the most sales?
Without a reliable WhatsApp campaign tracking system, these answers are usually scattered across Meta Ads, Google Ads, analytics tools, and the CRM.
The good news is that there are effective ways to connect this data.
When a company uses the official WhatsApp API, especially for Click-to-WhatsApp campaigns (CTWA), the WhatsApp integration can receive information about the origin of a conversation.
When an ad sends the visitor to a website or landing page first, the strategy changes: the business can track UTMs, page visits, user events, and later identify that visitor inside the CRM.
This guide explains how both approaches work.
Why track WhatsApp campaigns?
Imagine that your company spends $30,000 per month on advertising.
During the month, 2,000 new WhatsApp conversations begin.
Meta Ads can show how many clicks or conversations the campaigns generated. For a sales operation, however, that is usually not enough.
What matters is what happened after the conversation started.
For example:
Campaign A
- 500 conversations
- 80 qualified leads
- 20 sales
Campaign B
- 700 conversations
- 30 qualified leads
- 5 sales
If you look only at cost per conversation, Campaign B may appear to perform better.
Once WhatsApp data is connected to the CRM, however, Campaign A proves to have generated much more qualified demand and four times as many sales.
That is why tracking WhatsApp campaigns through to the final conversion can completely change how a company optimizes its media budget.
How to track WhatsApp campaigns with the official API
People can reach a business on WhatsApp in several ways.
One of the most important paths for paid media teams is through Click-to-WhatsApp Ads, commonly abbreviated as CTWA.
The flow is simple:
Facebook or Instagram ad → WhatsApp → conversation
In this scenario, the user does not visit your website.
They click the ad and open a WhatsApp conversation with the business directly.
This creates a problem for traditional tracking methods based on cookies, pixels, or UTM parameters.
The WhatsApp Business Platform provides another way to identify the source.
Tracking Click-to-WhatsApp campaigns (CTWA)
When a conversation starts from a Click-to-WhatsApp ad, the WhatsApp Cloud API can send referral information with the incoming message, as shown in Meta’s webhook payload reference.
A message that originated from an ad can include an object called referral.
The information documented by Meta can include:
- ad ID;
- source URL;
- source type;
- ad headline;
- ad body;
- media type;
- an image or video related to the ad.
This means the CRM receiving the information can identify that the conversation did not start organically. It came from a specific ad.
A simplified flow looks like this:
Meta Ads
↓
Ad #12345
↓
User clicks “Send message”
↓
↓
Official API receives the message and referral data
↓
CRM records the lead source
From that point on, the attribution data can follow the contact throughout the sales journey.
What is ctwa_clid?
Another important identifier for advanced attribution is the Click-to-WhatsApp Click ID, usually called ctwa_clid.
It identifies the click that started the WhatsApp interaction and can be stored with the contact or opportunity in the CRM.
When it is available in the payload, this identifier can also be stored and later used in Meta Conversions API integrations, helping close the loop between media, conversation, and conversion.
The business can begin building a chain such as:
Ad click → conversation → lead → opportunity → sale
Instead of measuring only:
Ad click → conversation
That difference is critical for companies that use WhatsApp as a sales channel.
Can you identify the campaign, ad, and creative?
Yes, but there is an important technical distinction.
The WhatsApp Cloud API webhook can directly include details such as the ad ID (source_id), headline, description, and creative media.
Using that ID, a CRM or marketing platform can enrich the record through integrations with Meta’s advertising ecosystem.
This can support reports that show:
- campaign;
- ad set;
- ad;
- creative;
- number of conversations;
- qualified leads;
- opportunities;
- sales;
- revenue generated.
The analysis moves beyond media delivery and toward revenue by campaign.
Why the official WhatsApp API matters for tracking
Some businesses still use WhatsApp solutions based on unofficial connections or automations that simulate WhatsApp Web.
These connections do not provide the same integration structure as the WhatsApp Business Platform.
With an official integration, communication runs through Meta’s infrastructure and messages are delivered to the platform through webhooks.
That is where additional information, including CTWA ad referral data, can be captured and stored in the CRM.
For companies making a significant investment in paid WhatsApp acquisition, the official API is not only an operational decision. It is part of the marketing data, attribution, and measurement strategy.
What if the ad sends the visitor to a website first?
Now consider a different journey:
Google Ads → landing page → WhatsApp
or:
Meta Ads → website → product page → WhatsApp
The lead does not move directly from the ad to the conversation. They browse the website first, creating additional tracking opportunities.
Tracking with UTMs
One of the most established ways to identify a visitor’s source is through UTM parameters.
For example:
utm_source=google
utm_medium=cpc
utm_campaign=whatsapp_crm
utm_content=ad_01
These parameters can identify:
- traffic source;
- medium;
- campaign;
- creative;
- keyword;
- marketing tactic.
Google recommends campaign parameters for identifying the campaigns that send visitors to a website and makes these values available in Google Analytics acquisition reports. In its campaign URL documentation, Google recommends using at least utm_source, utm_medium, and utm_campaign, along with the other parameters relevant to the analysis.
But the journey can be tracked further.
Tracking lead behavior on the website
With a tracking layer installed on the website, the business can create an anonymous profile for each visitor.
Imagine someone arrives through this campaign:
Google Ads → “WhatsApp CRM software” campaign
The system can record:
Anonymous visitor #84721
Source details:
- Source: Google
- Medium: CPC
- Campaign: whatsapp_crm
- Term: whatsapp crm software
It can then record the visitor’s behavior:
10:31 — visited the landing page
10:33 — visited the pricing page
10:35 — viewed the official API page
10:37 — started the demo form
10:38 — submitted the form
These events can be sent through tools such as Google Tag Manager and the dataLayer, or directly to a customer data platform or CRM.
Google Tag Manager can use the dataLayer to pass events and variables, including clicks, login events, searches, purchases, and other user interactions.
From an anonymous visitor to a known contact
While someone is browsing the site, the system may know them only as:
Visitor #84721
It does not necessarily know who that person is.
Now imagine they submit a form:
Name: John Smith
Phone: +1 555 010 1234
Email: john@example.com
The company can now identify the visitor.
This association should follow the applicable legal basis, the company’s privacy policy, and its consent and data-retention controls.
The anonymous profile can then be associated with a real CRM contact.
Instead of creating a lead with no context, the CRM can store:
John Smith
Source: Google Ads
Campaign: whatsapp_crm
First page: /whatsapp-crm
Visited pricing: Yes
Requested a demo: Yes
Phone: +1 555 010 1234
If John later speaks with the company on WhatsApp using the same phone number, the CRM can connect the two histories.
The business now knows not only who is having the conversation, but also how that person found the company.
Login can also identify a user
Forms are not the only way to identify a visitor.
Consider an ecommerce business or SaaS platform. A visitor arrives through a campaign, browses anonymously, and later signs in.
At that point, the system knows who the user is and can associate the earlier history with the known profile.
A journey might look like this:
Instagram Ads
↓
Product A
↓
Product B
↓
Pricing page
↓
Login
↓
↓
Purchase
Marketing can now understand the journey that happened before the sale.
The challenge with a website-to-WhatsApp click
There is a more complex scenario:
Ad → website → WhatsApp button → conversation
The user visits the website but does not submit a form or sign in before clicking the WhatsApp button.
The website knows that person only as an anonymous visitor. WhatsApp, on the other hand, knows the phone number.
A mechanism is needed to connect those two identities.
One option is to associate an anonymous identifier with the WhatsApp-button click.
For example:
Visitor: #84721
When the visitor clicks the WhatsApp button, the system can create a reference related to that session and later use it to associate the conversation with the original visitor.
The CRM can then join:
Visitor #84721
WhatsApp phone number
=
Identified contact
This approach is particularly useful for companies that receive substantial website traffic before WhatsApp conversions.
CRM + WhatsApp + marketing data
The full value becomes clear when all this information lives in the same system.
A CRM contact is no longer only:
Name + phone number + conversation
It can also include:
- first source;
- latest source;
- campaign;
- ad;
- creative;
- pages visited;
- events completed;
- WhatsApp conversation;
- qualification status;
- opportunity;
- sale;
- order value.
WhatsApp becomes part of a broader customer data and marketing automation strategy.
How to measure WhatsApp campaign ROI
Once the lead source is connected to the CRM, the business can create much more useful reports.
For example:
| Campaign | Conversations | Qualified leads | Sales | Revenue |
|---|---|---|---|---|
| Campaign A | 450 | 120 | 32 | $96,000 |
| Campaign B | 680 | 75 | 18 | $54,000 |
| Campaign C | 320 | 140 | 41 | $123,000 |
The question changes from:
“Which campaign generates the most messages?”
to:
“Which campaign generates the most revenue?”
That is one of the main benefits of connecting paid traffic, WhatsApp, and CRM data.
WhatsApp campaign tracking with Hootspy
Hootspy is designed to connect these different stages of the customer journey.
With campaign tracking, WhatsApp and Instagram CRM, automation, and official WhatsApp integrations in the same structure, companies can better understand where conversations come from and what happens after they begin.
For Click-to-WhatsApp campaigns, source information can be associated with the contact. For campaigns that send the user to a website, events, UTMs, and browsing behavior can complement the lead’s history.
The result is a more complete view:
Campaign → visitor → conversation → lead → opportunity → sale
The better this journey is tracked, the better the decisions about where to invest the marketing budget. Explore Hootspy campaign tracking.
Frequently asked questions about WhatsApp campaign tracking
Can I identify which ad generated a WhatsApp conversation?
Yes. For conversations that originate from Click-to-WhatsApp ads, the WhatsApp Cloud API can send ad referral data with the message, including the ad ID and information about the creative.
Do I need UTMs for Click-to-WhatsApp campaigns?
Not necessarily. In a direct CTWA journey, the user leaves the ad and enters WhatsApp without visiting your website. Attribution can use the information related to the CTWA interaction instead of relying exclusively on UTMs.
What are UTMs used for in WhatsApp tracking?
UTMs are particularly useful when an ad sends the visitor to a website or landing page first. They can identify the source, medium, campaign, and differences between ads or creatives.
Can I see which pages a lead visited before contacting the business on WhatsApp?
Yes. A tracking solution can record page views and other events while the visitor browses the site. If that visitor is later identified through a login, form, or another identity-resolution method, the earlier history can be associated with the contact.
Can I connect WhatsApp to a CRM and identify which campaigns generate sales?
Yes. This is one of the main goals of integrating paid-media data with WhatsApp and the CRM: following the journey beyond the first conversation and measuring qualified leads, opportunities, sales, and revenue by campaign.
Conclusion
Knowing how to track WhatsApp campaigns goes far beyond counting how many people started a conversation.
There are two main scenarios.
When an ad sends the user directly to WhatsApp through Click-to-WhatsApp Ads, the official API can capture information related to the origin of that interaction.
When an ad sends the user to a website first, UTMs, visitor identification, page views, and events can help track the journey before the conversation.
The next step is connecting that information to the CRM.
That integration answers the question that matters most:
Which campaigns are generating customers—not only messages?
Sources
Ready to automate WhatsApp with chatbots and Artificial Intelligence?
Professionalize your WhatsApp workflows today
Talk to a specialist