Want to Use WhastApp API?

Click-to-WhatsApp Ads (CTWA): The Complete Guide

Picture of Mumble Team

Mumble Team

May 25, 2026| זמן קריאה: 9 דקות

Click-to-WhatsApp Ads (CTWA): The Complete Guide

TL;DR

Click-to-WhatsApp Ads (CTWA) are ads on Facebook and Instagram that, when clicked, open a direct WhatsApp conversation with your business. Meta classifies a conversation that starts from CTWA as a Free Entry Point Conversation, meaning a free window that is wider than the standard 24-hour conversation window, under Meta’s current policy. This article explains how CTWA works, how to set up the ad in Meta Ads Manager, how Mumble captures the attribution data, how to use that data in automations and the chatbot, and the limits you need to know. If you market on WhatsApp, CTWA is the channel to understand before any other.

What CTWA Is

A CTWA ad is a regular Facebook or Instagram ad, but instead of a “Learn More” button that leads to a landing page, it has a “Send Message” or “Chat on WhatsApp” button. Clicking it opens WhatsApp on the customer’s device with a new conversation to you, sometimes with a pre-filled message or opening buttons (Icebreakers).

Why this channel is especially powerful:

  • Less friction along the way. Instead of: sees ad → lands on a page → fills out a form → waits for an email reply, the customer moves straight into a conversation with the business within seconds.
  • An extended free window. A conversation that starts from CTWA is classified by Meta as a Free Entry Point Conversation, so it gets a wider free window than a regular conversation, under Meta’s current policy. Eligibility for the extended window depends on the business responding quickly.
  • Higher conversion rates. Meta reports a significant improvement in conversion rates and cost per lead for marketers who use CTWA compared with driving traffic to landing pages. The reason: the conversation begins in a channel the customer is already in and familiar with.
  • Less dependence on iOS attribution. The conversation begins inside WhatsApp and does not require cross-app tracking, which iOS 14+ disrupted. “Conversation started” attribution holds for iOS as well.

How Billing Works

CTWA billing differs from regular conversations, and it pays to understand it.

Billing on the CTWA path
Stage Duration Payment to Meta
Paying for the ad Throughout the campaign The ad budget (CPC/CPM/CPL by campaign)
Customer clicks the ad A single moment Included in the ad cost
Free Entry Point window Per Meta’s current policy No charge for the conversation
After the window closes From the next message on Standard charge by conversation category

An important condition: the extended window only starts if the business replies to the customer within the standard 24-hour conversation window from the click. If the customer clicked and the business did not respond, the extended window does not open and the conversation is billed as usual. The length of the extended window is set by Meta, so verify the current value with Meta before planning budgets.

This makes the first response time central. An automation, chatbot, or Dolores AI that replies immediately ensures every click is used. A manual agent reply a day later hurts the campaign’s economics.

Setting Up a CTWA Ad in Meta Ads Manager

Setting up a CTWA campaign is done entirely in Meta Ads Manager. Mumble is not the platform that creates the ad, but it captures the conversations that arrive from it and stores the attribution data on the customer card.

Prerequisite: A Connection Between WhatsApp and a Facebook Page

Before you can set up a CTWA campaign, there must be a connection between the WhatsApp number and the business’s Facebook Page. This connection is done only once, through Meta Business Manager. Without it, the CTWA setup menu will not appear in Ads Manager.

Campaign Steps in Ads Manager

  1. Open a new campaign in Meta Ads Manager. Click “+ Create”.
  2. Choose an Objective. Three main objectives suit CTWA:
    • Engagement. The most common choice for CTWA and Meta’s recommendation. Optimized for reaching people likely to start a conversation.
    • Leads. Optimizes for higher-quality leads, at the expense of volume.
    • Sales. Optimizes for sales, if conversion tracking is set up.
  3. Set the Conversion Location: Messaging destinations.
  4. Select WhatsApp as the destination (not Messenger or Instagram, unless you want broad reach).
  5. Choose the WhatsApp number from the list.
  6. Define the audience, budget, and schedule as you would for any other ad.
  7. Choose an ad format: single image, carousel, or video. Video in CTWA tends to yield a higher CTR.
  8. Set up the initial message or the Icebreakers that appear in the conversation the moment the customer clicks. You can combine:
    • A pre-filled message that the customer sends automatically when they click.
    • 3-4 opening buttons (Icebreakers) that the customer can tap.
  9. Publish the campaign.

A reasonable time for a full setup: 1-3 hours the first time. After the first ad, duplicating it for the next campaign takes minutes.

Starting Budget and Learning

Meta’s standard guidance for optimization is to reach around 50 conversions per week to exit the Learning Phase and let the algorithm learn. Plan the daily budget so this event volume is achievable at the Ad Set level, not just at the campaign level.

Additional rules of thumb:

  • An initial run of 7-14 days before drawing conclusions. Meta needs time to exit the Learning Phase.
  • An A/B split between two ad versions from the start of the campaign to find what works.
  • Avoid frequent changes in the first days. Any significant change resets the Learning Phase.

How Mumble Identifies CTWA Conversations

This is the part that changes everything. When a customer clicks a CTWA ad and the conversation arrives in WhatsApp, Mumble receives the attribution data from Meta and stores it on the customer card. The data is also available as system variables in the chatbot and Dolores AI.

The Attribution Data Mumble Captures

  • fbclid, fbc, fbp. Standard Meta identifiers, important for sending Conversions API data back to Meta.
  • campaign_id. Which campaign brought the customer.
  • adset_id. Which specific Ad Set.
  • ad_id. Which specific ad. Especially useful when running several ads at once.
  • placement. Where the ad was shown (Instagram feed, Stories, Facebook).

The data is available on the customer card, and it is also available as system variables you can use in automations and chatbot flows.

Using Attribution Data in Automated Flows

This is where CTWA goes to real work in Mumble. Examples of flows:

  • Automatic assignment to a list by campaign. A chatbot that runs at the start of every new conversation can assign the customer to a list based on campaign_id, so you can later tell which customers came from which campaign.
  • A conversation tailored to the ad. If the ad presented a specific offer (“birthday sale”), the chatbot can identify it by ad_id and open with a relevant conversation.
  • Automatic routing to a team. An automation can check campaign_id and assign leads from a sales campaign to the sales team, and leads from a service campaign to the support team.
  • Conversion tracking back to Meta. Through the Conversions API (CAPI) you can send events that happened after the conversation back to Meta (for example, that the lead actually purchased), which improves the optimization of future campaigns.

A Message Template for an Automatic Greeting

We recommend creating a dedicated message template that is sent automatically, within seconds, to customers arriving from CTWA. Why this is essential:

  • Opening the extended window immediately. A reply within 30 seconds keeps the customer warm while they are still interested, and meets Meta’s condition for opening the Free Entry Point window.
  • Opt-in. CTWA approves the initial conversation, but not necessarily the ability to send Marketing-category message templates in the future. It pays to include a “Yes, send me updates” button in the greeting to capture consent for later.
  • Linking the customer to the campaign they came from. The message template can reference the content of the ad (“Did you see our offer on X?”) and continue the conversation in a relevant way.

How to build a CTWA greeting template:

  1. Create a message template in the Utility category (if it is a conversation confirmation) or Marketing (if it is an initial offer).
  2. Include the name of the sale or campaign in the message body, using a dynamic variable.
  3. Add 2-4 Quick Reply buttons with action options: “Tell me more”, “I want to buy”, “Just browsing”.
  4. Make sure one of the buttons requests future opt-in.
  5. Submit the message template to Meta for approval (usually approved within an hour).

Once the message template is approved, complete the flow with an automation: trigger on a new CTWA conversation → action: send the greeting message.

Limits, Best Practices, and Common Mistakes

Marketing Limit for US Numbers

Meta restricted the ability to send Marketing-category message templates to US numbers (+1 prefix) during 2025. The exact status of this restriction shifts with Meta’s decisions, so it pays to verify the current state with Meta before a campaign targeting a US audience. Even while the restriction is in effect, the initial CTWA conversation opens as usual, and you can send those customers message templates in the Utility and Authentication categories. See Messaging limits in Meta’s tier system.

Best Practices

  • Respond immediately. 30 seconds is excellent. 5 minutes is reasonable. An hour is the edge. A day is a failure of the extended window. Use Dolores AI or the chatbot for an automatic first response.
  • Use Icebreakers, not an empty message. An empty conversation loses a significant percentage of customers who do not know what to write. Icebreaker buttons (“How can we help?”, “Tell me about the sale”) lead the conversation.
  • Assign every CTWA lead to a list. A general list like “CTWA leads” plus a more specific list by campaign. This lets you analyze performance later.
  • Make the most of the extended window. This is the opportunity to take the customer through the important stages: introduction, questions, product presentation, closing. After the window closes, every message costs money and stops if the customer has not replied.
  • Request future opt-in within the conversation. At the right point, after building trust, ask: “Would you like to receive updates from us about new offers on WhatsApp?” with “Yes” and “No” buttons.
  • Monitor the real cost per lead. Meta shows Cost per Conversation, but that figure does not include all the customers who never replied after the first message. Track real conversion rates from the campaign in your CRM or in Mumble.
  • Connect the Conversions API to improve your campaigns. Sending events back to Meta (for example, “lead became a customer”) helps Meta’s algorithm find higher-quality customers. The connection is possible through Mumble via a custom integration.

Common Mistakes

  • You did not connect WhatsApp to the Facebook Page in advance — and the CTWA setup menu does not appear in Ads Manager. The fix: go to Meta Business Manager and verify the connection exists.
  • A manual reply with no automated support. A small team can handle a few daily leads manually; high volume requires automation. Plan an automation before a large-scale campaign.
  • An empty or generic first message. “Hello, how can we help?” after the customer clicked a very specific ad is a poor service experience. The message should reference the ad and its content.
  • Wasting time in the extended window. A conversation that stops after 2-3 messages wastes the window’s potential. Plan a structured sequence.
  • Not requesting future opt-in. After the window closes, you cannot reach out to the customer without explicit consent. One request at the right time opens the door for the long term.

Troubleshooting Common Issues

Customers Click the Ad but I Don’t See New Conversations in Mumble

Check the connection between WhatsApp and the Facebook Page. In Meta Business Manager → WhatsApp Manager, verify the number is connected to the correct Page. If the connection breaks (this sometimes happens after a configuration change), conversations from the ad will not arrive.

I See a New Conversation, but There’s No Campaign Attribution Data

This can happen in rare cases, especially when the customer starts the conversation through WhatsApp Web rather than the app on their device. iOS with strict privacy settings can also reduce the attribution data. Most conversations will arrive with the data, but not all of them.

I Replied Within 5 Minutes but Meta Charged Me for the Conversation

Make sure the reply is an approved message template or a regular message (and not an automatic WhatsApp confirmation message). If Meta charged you anyway, contact Mumble support with the conversation details for review.

My CTWA Ads Aren’t Getting Clicks

This is a problem with the campaign itself, not with Mumble. Check:

  • Is the audience relevant?
  • Is the creative clear and engaging?
  • Is the budget enough to exit the Learning Phase (a target of 50 conversions per week at the Ad Set level)?
  • Does the message in the ad match the call to action?

How Do I Know Which Campaign Drove the Most Sales?

You need tracking across the whole journey: click → conversation → qualified lead → sale. The standard approach: assign every lead with its campaign_id on the customer card via an automation, and when they become a customer (a status change or being added to a “Customers” list), you can analyze the data backward. A deeper connection with Meta through the Conversions API requires dedicated setup.

The Campaign Is Running but Sending Marketing Messages to CTWA Customers Doesn’t Work

Check the date of the customer’s last message. If the extended window has closed, sending a Marketing-category message template requires explicit opt-in from the customer. The customers who tapped “Yes, I want to receive updates” on a Quick Reply button in the greeting message are the only group you may send free Marketing to after the window closes.

When Not to Use CTWA

CTWA is not right for every business. It is not the solution if:

  • The audience is mostly in the US and a Marketing restriction is in effect for the +1 prefix.
  • There is no ability to respond first within 24 hours (no Dolores AI, no chatbot, no large enough team of agents).
  • The product requires an experience that cannot happen in chat (for example, a complex visual product experience that needs a website).
  • The business is in a category prohibited by Meta’s policy (gambling, alcohol, weapons, and more). See WhatsApp Business Account bans and restrictions.

Related Articles

The Bottom Line

CTWA requires three things: a fast response, a structured greeting message, and tracking of your campaigns through the attribution data. Without all three, the budget burns for nothing.

Picture of Mumble Team

Mumble Team

מאמבל מתמחה בשינוי תקשורת עסקית באמצעות פתרונות וואטסאפ חדשניים. עם התמקדות באופטימיזציה של מכירות, ניהול לידים ואוטומציה של אירוסי לקוחות, Mumble מעצים עסקים לצמוח בצורה חכמה ומהירה יותר. עם תשוקה ליעילות וחדשנות, הצוות ממשיך להגדיר מחדש איך חברות מתחברות עם הלקוחות שלהן.