To measure click to WhatsApp ads, you need to follow more than the first conversation. A customer can message you from an ad, discuss their needs, and buy later. This guide explains the messaging costs, the data attached to that first message, and the steps that connect ad spend to revenue. You can use the measurement approach to plan your tracking, then see how it works with Kommo.
What are click to WhatsApp ads?
Meta calls this format ads that click to WhatsApp, often shortened to CTWA ads. In its developer documentation, the definition is an ad with a WhatsApp message destination. The person taps the ad, and a WhatsApp chat with your business opens.
For the customer, the next step is a conversation rather than a website visit. They can send a question, explain what they need, or ask about buying. Opening the chat is the start of that journey, not proof that an order followed.
You create these ads in Meta Ads Manager. Use Meta’s setup guide for ads that click to WhatsApp for the current instructions.
Before launching, decide what happens after someone writes. Who handles the inquiry? Where will the deal live? What counts as a sale? Those decisions make the later report useful.
What does WhatsApp messaging cost after an ad click?
Separate two costs: the ad spend and the WhatsApp message fees. You still pay for the ad in Ads Manager. The messaging rules below do not remove that advertising cost.
According to Meta’s WhatsApp Business Platform pricing documentation, a customer service window opens when someone messages your business through a CTWA ad from the WhatsApp Android or iOS app. Desktop and web apps are not supported for this entry-point condition.
If you respond within the customer service window, Meta does not charge for that response. Your response also opens a Free Entry Point, or FEP, window. That window starts at the time you reply and may remain open for up to 7 days.
While the FEP window is open, Meta does not charge for marketing, utility, authentication, or service messages. It tracks the window separately for each business and WhatsApp user pair.
Do not treat an ad click alone as confirmation that this window has opened. The customer’s message, supported mobile app, and your response within the customer service window are the relevant conditions.
What data comes with the first WhatsApp message?
A message from an ad can carry information about where the customer came from. In plain language, this can include the ad’s text, its link, its identifier, and details about its image or video. A separate click identifier can connect the conversation to the specific originating click.
This tracking needs the WhatsApp Business API connection. For AnyLinga’s ad tracking, numbers connected by QR code do not receive ad data. Check your connection type before expecting source details to appear on a deal.
In technical terms, Meta’s incoming text message webhook reference describes a referral object. It is included only when the message was sent through a Click to WhatsApp ad.
Its fields include source_url, source_id, source_type, headline, body, media_type, image_url, video_url, thumbnail_url, ctwa_clid, and welcome_message.
The click ID is not the ad ID. The ctwa_clid identifies an individual click. Meta omits it for messages from WhatsApp Status ad placements, so do not assume every ad-originated message contains one.
Why a conversation report does not tell you sales results
A conversation started answers one question: did the ad bring someone into a chat? It does not answer whether that person bought, what they spent, or which deal eventually closed.
The commercial outcome happens later in your CRM. A salesperson may answer questions, discuss the offer, and move the deal through stages before marking it won. Unless the ad source stays attached, that outcome becomes disconnected from the original inquiry.
This is why you should read conversation results and sales results separately. WhatsApp leads tell you how many people wrote. Won deals and their amounts tell you what revenue you recorded.
For Kommo users, AnyLinga’s Meta ads tracking for Kommo connects the originating ad with the deal and the resulting report. The aim is not to replace your ad report, but to extend the measurement through the sale.
Connect an ad to a sale in four steps
Build the measurement chain before you judge performance. You need a source, a deal outcome, a revenue amount, and the corresponding spend. Keep the comparison period clear so you know what the figures represent.
- Record the ad on the first message. Capture the available referral information when the customer writes. Preserve the originating ad’s identity rather than relying on someone to remember it later.
- Keep that source on the deal. Carry the ad information with the sales record as your team handles the conversation. You need to connect the eventual outcome to the original source.
- Mark the won stage and amount. Record successful deals consistently and enter the deal amount. A chat without a recorded outcome cannot tell you whether a sale happened.
- Compare results with ad spend. Review leads, sales, and revenue alongside spend for the ad and reporting period. Then calculate the ratios below.
The three calculations answer different questions:
- Cost per lead = ad spend ÷ leads. How much ad spend corresponds to each lead?
- Cost per sale = ad spend ÷ sales. How much ad spend corresponds to each recorded sale?
- ROAS = revenue ÷ ad spend. How much recorded revenue corresponds to each dollar of ad spend?
Illustrative example: these numbers are made up to show the calculation. An ad has $412.60 in spend, 148 leads, 21 sales, and $4,830 in revenue.
Dividing spend by leads gives $2.79 per lead. Dividing spend by sales gives $19.65 per sale. Dividing revenue by spend gives ROAS of 11.7×. These are calculations, not benchmarks or a prediction for your campaigns.
Read the measures together. Cost per lead describes the entry into the conversation; cost per sale and ROAS describe the recorded commercial outcome. Neither a low lead cost nor a large chat count is a substitute for checking won deals.
Send purchases back to Meta, not only chats
Recording a sale in your CRM helps you measure results. Sending the outcome back to Meta is a separate step. The Conversions API for business messaging lets your integration send events that describe what happened after the chat began.
Meta’s Conversions API documentation for business messaging lists supported events including Purchase, LeadSubmitted, QualifiedLead, InitiateCheckout, AddToCart, and OrderCreated. Choose an event that matches the actual outcome, rather than treating every message as a purchase.
These events use action_source set to business_messaging and messaging_channel set to whatsapp. Meta advises sending ctwa_clid whenever you have it because it identifies the originating ad click directly.
Meta also states that this API enables access to purchase optimization for ads that click to Messenger and WhatsApp only. That is a capability, not a promise of more sales or a particular ROAS. Your chosen CRM stage still needs to represent the event you intend to report.
How ad tracking works in Kommo with AnyLinga
AnyLinga’s Kommo integration for Meta ads records the ad text, link, and ad ID in the customer’s deal. It also puts UTM tags in the tracking fields, keeping source information alongside the sales record.
In your AnyLinga account, open Meta conversions → Report. The report shows ad spend, leads, cost per lead, sales, cost per sale, and revenue for each ad by month. Totals show ROAS.
A lead means a unique customer who wrote from the ad. A sale means a Kommo deal that reached the successful, or won, stage. Revenue comes from the deal amount.
Spend loads automatically from the connected Meta ad account once a day; you can also enter it manually. Revenue is converted to the report currency at the exchange rate for the sale day.
When a deal reaches the stage you choose, AnyLinga sends a conversion to Meta. This currently works with Kommo only and requires a WhatsApp Business API connection. The report is available on every AnyLinga plan.
The team can set this up for you. Standard setup is free when you pay for your first month. You can also start with a 7-day trial, with no credit card required.
Before you launch: a short tracking checklist
Check the full path, not just the ad destination:
- Confirm that WhatsApp uses a Business API connection, not a QR-code connection.
- Check that the originating ad information stays on the Kommo deal.
- Define the successful stage and record deal amounts consistently.
- Connect your Meta ad account for daily spend loading, or enter spend manually.
- Choose the deal stage that should trigger a conversion sent to Meta.
- Plan your response process around the customer service window and the mobile-only FEP entry condition.
With those pieces in place, you can compare conversations with recorded sales instead of stopping at the first message.