ManyChat Not Tracking WhatsApp Ads? Here's Why (And What to Do)

You launched a Click-to-WhatsApp ad campaign. Money is going out, messages are coming in, but when you open ManyChat you cannot tell which ad sent which person. The conversations just appear in your inbox with no source attached. If that sounds familiar, you are in good company.

This is one of the most common complaints in ManyChat's own community forum right now. Users spend thousands on ads, then struggle to figure out which creative actually worked. Some conversations show up in ManyChat, many do not. Some flows trigger, others silently fail. And ManyChat support is slow or unresponsive.

We pulled the actual community threads (with dates, usernames, and exact quotes), compared them to Meta's official WhatsApp documentation, and laid out what is really happening and what to do about it.

What Users Are Reporting (Real Quotes)

Here are verified complaints pulled from ManyChat's own community forum. Every quote below links to the original thread.

That is 1,900 ad clicks and 4 bot conversations. The user had flows wired up with CTWA triggers tied to each Ad ID and keywords. It still did not work. A support ticket was filed and went unanswered.

The only reply on that last thread was a suggestion to "refresh permission again." That was it. No fix, no follow-up, no explanation.

There are more threads like this. A pattern is obvious: the problem has existed since at least mid-2025, users keep reporting it, and there is no consistent fix from ManyChat.

Why This Keeps Happening

To understand why attribution breaks, you need to know what Meta actually sends.

When someone clicks your Click-to-WhatsApp ad and sends their first message, Meta attaches a piece of data to that message called the referral. It contains everything you need to know:

• The exact ad ID (matches your Ads Manager)
• The ad headline the user saw
• The ad body copy
• Whether the ad was an image or video
• A unique click ID for tracking conversions

Here is the catch that causes most of the problems: Meta only sends this data once, on the very first message. If anything goes wrong during that first webhook, the data is gone forever. Meta does not resend it.

So anything that causes the first message to be dropped, delayed, or processed incorrectly means you lose the ad source permanently. That includes:

• Webhook timeouts
• Platform errors on the first message
• Permission issues between ManyChat and Meta
• Ads Manager setups that use the wrong CTA type
• FAQ or default-response templates that intercept the click
• Race conditions where the message arrives before the user record exists

Any one of these can silently drop attribution on a chunk of your ad traffic. Stack a few together and you get the kind of loss cata_rendon reported (1,896 missing conversations out of 1,900).

What Actually Helps (Verified Community Workarounds)

These are fixes that real users in the ManyChat community reported as helpful. None of them solve the problem completely, but they reduce the damage.

1. Set the CTA to "Send WhatsApp Message" (not FAQ)

This was AwaisToor's fix on the 1,900-click thread. In Meta Ads Manager, when you build a CTWA ad, you have multiple CTA options. The FAQ default response template intercepts clicks before they reach your bot. Set the CTA to "Send WhatsApp Message" instead.

"In Ads Manager, make sure the CTA is set to 'Send WhatsApp Message.' FAQ default responses often break the user journey." AwaisToor, ManyChat Community

2. Simplify your first ad message

Gustavo Boregio (a ManyChat Community Expert) suggested that "text + image + text with button may be more than what's allowed" in CTWA initial messages. If your first message template is complex, the ad click might fail to route correctly. Start with plain text and a single button. If that works, add complexity back in one piece at a time.

3. Rebuild the campaign under matching account ownership

The user who reported 1,900 clicks eventually resolved their issue by "setting up again the campaign from the Meta owner's account and ManyChat owner's account" and adding instructions telling users to click the button. The fix took roughly eight months from initial post to resolution. That is a long time to be flying blind.

4. Use Meta Ads Manager reporting as a fallback

Meta's "Messaging Conversations Started" metric inside Ads Manager tells you how many WhatsApp conversations each ad generated, at the campaign and ad set level. You lose the ability to tie a specific conversation to a specific ad, but you can still see aggregate performance. Use this to sanity-check whether your ads are actually getting clicks when ManyChat says they are not.

5. Test with a single ad and a distinctive keyword first

Before scaling a multi-ad campaign, run one ad with a unique keyword like "TESTAD2026." Click your own ad. See if the conversation lands in ManyChat with the attribution you expected. If it does not, fix that before spending real money.

What to Do If You Lose a Lot of Data

If you are already running CTWA ads and losing significant attribution, here is the order of operations that tends to recover the most data fastest:

1. Pause the campaign. Every dollar spent while attribution is broken is a dollar you cannot evaluate.
2. Switch your ad CTA to "Send WhatsApp Message" if it is set to FAQ or anything else.
3. Simplify the first message to a single-button text response.
4. Test with one ad and one keyword. Click it yourself. Verify the conversation reaches ManyChat with source data attached.
5. If testing works, slowly relaunch additional creatives.
6. If testing still fails, the problem is at the platform layer, not the campaign. Consider the platform-level options below.

The Platform-Level Fix

Workarounds help, but the underlying problem is that attribution depends on whether your automation platform correctly captures Meta's one-shot referral data on the first message. Platforms that capture it reliably do not have this problem. Platforms that miss it even occasionally leak data, and the leak rate scales with ad volume.

When evaluating any WhatsApp automation platform, ask these five questions:

1. Does every ad-driven conversation show the ad ID, headline, and body copy in the inbox?
2. Can I filter my inbox to see only ad conversations vs organic conversations?
3. Does the platform give me the full 72-hour messaging window on ad conversations (Meta's policy allows this)?
4. What happens if the very first webhook fails? Is there retry logic to recover attribution?
5. Can you show me, with a real account, what an attributed ad conversation looks like in your inbox?

If the answer to any of those is no, or the sales rep dodges the last one, keep looking.

ChatGenius Captures Every Referral Field Meta Sends

We built ChatGenius natively on Meta's WhatsApp Cloud API, without a middleman. Every CTWA conversation shows the ad ID, the headline, the body copy, and gets the full 72-hour messaging window automatically. There is a dedicated filter in the inbox for "CTWA Ads vs Organic" so you can instantly see which ads are driving volume.

We also built in retry logic for the race condition where the first message can arrive before the user record exists. That single detail recovers a meaningful chunk of the attribution other platforms lose.

Bottom Line

ManyChat's WhatsApp ad tracking has been broken for months, and the community has documented it in detail. Users report 1,900 ad clicks producing only 4 bot conversations. Trigger failures go unresolved. Support tickets sit unanswered. The workarounds (cleaner CTAs, simpler first messages, rebuilding campaigns from the right account) help, but they do not fix the underlying fragility.

If you run Click-to-WhatsApp ads, attribution is not a nice-to-have. It is the difference between scaling what works and throwing money at what does not. Try the workarounds first. If they do not hold, it is probably time to look at a platform that was built for this from day one.

Sources

• ManyChat Community - Click to WhatsApp campaign, no leads showing in ManyChat (cata_rendon, Aug 2025)
• ManyChat Community - Identify from which ad is the message in WhatsApp (psicocentro, Apr 2026)
• ManyChat Community - User Clicks a CTWA Ad trigger not working (Gabriel Nascimento, Jul 2025)
• ManyChat Known Issues - WhatsApp Keyword Trigger failing for ad-initiated conversations
• Meta for Developers - WhatsApp Cloud API Webhook Components (referral object reference)
• WhatsApp Business - Conversation Pricing (72-hour CTWA messaging window policy)
• ManyChat Help - WhatsApp Ads Trigger documentation