---
title: 'Click-to-WhatsApp ads: setup, cost and sales tracking'
description: 'Set up click-to-WhatsApp ads, understand current messaging charges, and connect confirmed chat sales to Meta with business-messaging conversion events.'
canonical: 'https://plainrouter.com/library/click-to-whatsapp-ads'
format: Guide
published_at: '2026-10-29'
last_updated: '2026-10-29'
---
# Click-to-WhatsApp ads: setup, cost and sales tracking
Click-to-WhatsApp ads are Meta ads that open a WhatsApp conversation with your business. Run click-to-WhatsApp ads when customers need a conversation before buying and your team can answer promptly, record completed sales, and connect those sales back to the originating ad.
If all you can report is clicks or new chats, you cannot yet tell which ads brought customers. Set up the sales record before scaling the campaign. A conversation is an opportunity to sell, not a completed sale.
## Key facts
- Click-to-WhatsApp ads can take people from Facebook or Instagram into a business chat without a website visit. [WhatsApp's ad overview, checked October 29, 2026]().
- Meta's current pricing documentation describes a qualifying click-to-WhatsApp free entry window of up to seven days, with conditions and a separate charge for Meta Business Agent messages. [Meta's pricing rules, checked October 29, 2026]().
- Meta's Conversions API for Business Messaging accepts recorded chat outcomes, including purchases and qualified leads. [Meta's onboarding guide, checked October 29, 2026]().
- The WhatsApp message webhook can supply ` ctwa_clid ` for connecting a conversion to an ad click; Meta says that field is omitted for WhatsApp Status ad placements. [Meta's webhook reference, checked October 29, 2026]().
## What are WhatsApp ads, and what does CTWA mean?
For a business buying Facebook or Instagram ads, “WhatsApp ads” usually means ads whose destination is a WhatsApp chat. CTWA means click-to-WhatsApp. The person taps the ad and can send your business a message instead of completing a website form.
The ad and the conversation are different steps. Opening WhatsApp does not prove the person sent a message, and a message does not prove they qualified or paid. Your reporting needs to keep those outcomes separate.
Ads displayed inside WhatsApp are a placement question, rather than simply a destination choice. Meta also documents [ads in WhatsApp Status](), separate from personal chats and calls. Those ads can themselves open a business conversation, so “inside WhatsApp” and “click-to-WhatsApp” are not mutually exclusive. Status availability is gradual, and its click-ID coverage differs from the Facebook and Instagram journey described below.
## How do you set up click-to-WhatsApp ads in Ads Manager?
Connect the business number first, then choose an objective and the WhatsApp destination. Meta's [current setup guide]() accepts either the WhatsApp Business app or a Business Platform setup, with the number connected to your Facebook Page or business portfolio and the necessary account access.
The following paths were checked against Meta's rendered Help Center on October 29, 2026. They were not tested inside a signed-in ad account. Meta changes setup flows and limits some messaging features by market, so use the controls actually available to your account.
| Objective in Meta's guide | Where to choose WhatsApp | Important distinction |
| --- | --- | --- |
| Traffic or Engagement | At ad-set level, Conversion → Message destinations → WhatsApp | Check the Performance goal; the objective does not establish that delivery is optimized for purchases |
| Leads | In the ad set's Conversion section, select WhatsApp | Meta's documented default is to maximize conversations, not confirmed customers |
| Sales | At ad-set level, Conversion → Message destinations → WhatsApp | Inspect the available performance goal; selecting Sales alone does not demonstrate purchase-event optimization |
| Awareness | At ad level, Destination → Messaging apps → WhatsApp | The destination is selected later in this flow |
For a typical Traffic, Engagement or Sales setup:
1. In Ads Manager, create a campaign with the chosen objective and name it.
1. At the ad set, select Message destinations as the conversion location, choose the relevant Facebook Page, and select WhatsApp.
1. Check the connected number, performance goal, budget, schedule, audience and placements. Do not leave another messaging destination selected unintentionally.
1. At the ad, add the creative and configure the Message template, including a useful greeting or suggested questions.
1. Review the destination and conversation experience before publishing. Confirm that the right team can answer and record the outcome.
A developer app is not listed as a prerequisite for this standard Ads Manager workflow. Building the conversion-reporting connection is a separate technical task. Meta's [Marketing API guide]() has its own app, token and permission requirements; do not confuse those with creating an ad in the interface.
## What do click-to-WhatsApp ads cost?
Budget for the ad, the messaging service you use, and the people or software handling the conversation. There is no universal cost per customer: that depends on your auction spend and how many conversations become real customers.
| Cost | What to budget for |
| --- | --- |
| Meta ad delivery | Your campaign's advertising spend; a free messaging window does not make the ad free |
| WhatsApp Business Platform messages | Applicable delivered-message charges by category and recipient market, subject to current exceptions |
| Inbox or service provider | Any separate subscription, seats, automation or message markup in your provider's contract |
| Handling the sale | The work required to answer, qualify, follow up and record the order |
The WhatsApp Business app and Business Platform are different products. The app is free to use; that does not make ads free or mean an API provider must charge nothing. WhatsApp's [business FAQ]() explains the distinction and notes that partners can charge for their services.
### What changed on October 1, 2026?
Meta's [current Platform pricing]() resumed per-message charges for service messages and for utility messages sent inside the customer service window. The change applies by Messaging account timezone. It is no longer safe to budget on the older rule that every service reply or in-window utility message is free.
For ordinary service-message pricing, each business phone number has a monthly allowance of 1,000 service messages, with charging starting at the 1,001st; unused allowance does not roll over. That is not an allowance of 1,000 marketing templates or 1,000 conversations. Messages from users to the business are not charged by Meta. Separate exceptions, including the qualifying free entry window, still apply.
For marketing, utility, authentication and service messages, use the current category and recipient-country rate rather than a single global WhatsApp price. Meta Business Agent has separate pricing. Check Meta's rate card and your provider's fees before setting a budget; the pricing rules here were checked October 29, 2026.
### Is the free messaging window 72 hours or seven days?
Meta's current pricing page says a qualifying click-to-WhatsApp free entry point window may remain open for up to seven days. Use that current rule, not an unconditional promise of seven free days for every click.
The documented sequence is:
1. The person sends your business a message through a click-to-WhatsApp ad using WhatsApp on Android or iOS; desktop and web are not supported for this entry-point rule.
1. A 24-hour customer service window opens. You respond within it with a marketing, utility, authentication or service message.
1. That response opens the free entry point window from the time of your reply. While it is open, those four message categories are not charged by Meta. Meta Business Agent messages remain charged.
The 24-hour service window is a separate permission to send non-template replies. If it closes, a still-open free entry window does not give you permission to keep sending free-form messages; use permitted templates. Messaging still needs the applicable opt-in. Neither window is a conversion-attribution window.
## How do you track sales from click-to-WhatsApp ads?
Keep the ad context with the conversation, record the actual lead or sale in your business system, and send the relevant chat event through Meta's Conversions API for Business Messaging. Compare that reported event with your own completed-order record; do not count every chat as a purchase.
A website Pixel cannot observe a purchase that happens entirely in a WhatsApp thread because your website's code is not running there. If the conversation instead sends someone to your website to pay, that purchase belongs to the website measurement path. Meta's [business-messaging guide]() explicitly separates in-thread interactions from website and app conversions.
The [Meta Conversions API overview]() covers that website path. A sale recorded in a CRM does not, by itself, determine which event source to use.
### Keep the conversation's ad click ID
The WhatsApp Business Platform's incoming-message webhook can include a ` referral ` object with ad context and ` ctwa_clid `. Store the actual value with the conversation when it is supplied, so your order record can retain the connection when the sale closes. A typed “I came from Facebook” reply is useful context, but it is not the same identifier.
This synthetic fragment illustrates the fields only; it is not a captured webhook or a complete payload:
```json
{
"source_type": "ad",
"source_id": "EXAMPLE_AD_ID",
"ctwa_clid": "EXAMPLE_CTWA_CLICK_ID"
}
```
Meta's [customer-information reference]() says to send ` ctwa_clid ` unhashed. Treat it as personal information, not a public label to put in a screenshot. Do not replace it with ` fbclid `, a UTM campaign name or your internal order ID.
Check coverage rather than assuming every message has a click ID. Meta's [text-message webhook reference]() says WhatsApp Status-originated ad messages omit ` referral.ctwa_clid `.
### Send the outcome through the business-messaging integration
Meta calls the product Conversions API for Business Messaging. Its onboarding guide describes a developer app, a WhatsApp Business Platform connection, authorized access and a dataset associated with the WhatsApp Business Account. It names ` whatsapp_business_management ` and ` whatsapp_business_manage_events ` as the token permissions for this WhatsApp event path. A website CAPI token or an inbox connection alone does not establish that those prerequisites are met.
For a conversion that happened in the chat, the documented mapping includes:
| Field | Meaning |
| --- | --- |
| ` event_name ` | The recorded outcome, such as ` Purchase ` or ` QualifiedLead `, not a purchase invented from a new conversation |
| ` event_time ` | When the outcome actually occurred |
| ` action_source ` | ` business_messaging ` for this integration |
| ` messaging_channel ` | ` whatsapp ` for a WhatsApp outcome |
| ` user_data.whatsapp_business_account_id ` | The business account associated with the messaging source |
| ` user_data.ctwa_clid ` | The originating ad click ID, when available, sent unhashed |
| ` custom_data.currency ` and ` custom_data.value ` | The real transaction currency and value for the purchase record |
The event is sent to the appropriate dataset's ` /events ` endpoint. Follow Meta's [onboarding requirements and current payload specification](), or confirm your provider implements that path. Do not send chat transcripts or invent a website URL to make the payload look like a web purchase.
### What if the click ID is missing?
Meta also documents a fallback using normalized, hashed customer information and ` page_id `. Matching is not guaranteed; that path is available in a subset of countries and attributes only to an ad interaction in the previous seven days. Meta says ` external_id ` alone is not used for matching on that path. An event can be accepted without being attributed, so a successful response is not proof that a missing click ID was recovered.
Use the real ` ctwa_clid ` whenever available and follow the field-specific rules for information you are permitted to send. Never fabricate an identifier to make an unmatched conversation look attributed.
### Verify receipt, duplicates and the sales record separately
Check the intended dataset in [Events Manager]() after sending an event. Retain a record of the business outcome and the submission result so you can distinguish a completed sale, an accepted event and an ad-attributed conversion.
Meta explicitly says it does not assist with deduplication for Conversions API for Business Messaging. Deduplicate in your own sending process; do not assume website Pixel/CAPI pairing rules will remove duplicate chat-sale reports. Choose one reporting owner for each outcome and avoid re-sending the same purchase as a new sale on every CRM update.
For campaign evaluation, compare ad spend with confirmed new customers or qualified outcomes over a consistent period, including message/provider costs where relevant. Count each customer and order according to a stated rule. Keep unmatched sales separate, account for delayed closing, and do not treat Meta's attributed total as proof that the ad caused every sale.
## What about click-to-Messenger and Instagram Direct ads?
They are sibling click-to-message formats with different chat destinations and identifiers. Meta's [business-messaging guide]() documents a Page-scoped identity for Messenger and an Instagram-scoped identity for Instagram Direct, rather than telling you to reuse a WhatsApp click ID.
The same guide describes purchase optimization through this API for WhatsApp and Messenger, while the Instagram setup supports conversation optimization rather than that purchase-optimization path. Do not assume identical setup, pricing or optimization across all three apps. Choose the destination your customers use, then verify its measurement route.
## Frequently asked questions
### Are click-to-WhatsApp ads worth running?
They fit sales that benefit from a conversation and a team that can respond and record the result. Judge confirmed customers and the cost of handling those conversations, not cheap clicks or a full inbox. If you cannot connect chats to outcomes, establish that record before expanding spend.
### Can I run click-to-WhatsApp ads without a website?
Yes. The ad can open a WhatsApp chat directly, and Meta's Ads Manager prerequisites allow the WhatsApp Business app or Business Platform. A website is not needed for that destination; programmatic sales reporting has separate Platform and conversion-integration requirements.
### Does the Meta Pixel track a WhatsApp sale?
It does not observe a sale completed entirely inside the chat. Use the business-messaging event path for an in-thread outcome; use the appropriate website or app integration when the purchase actually happens there.
### Does a click automatically start seven days of free messages?
No. Meta's qualifying sequence requires the person to message through the ad on a supported mobile app and the business to reply within the customer service window. The resulting entry window can last up to seven days, has message-category exceptions, and does not change what you pay for the ad.