CTWA ADS + CAPI... THERE MUST BE A BETTER WAY

Hi roverdrammen

If you want all your ads to redirect into a single flow without adding a separate CTWA trigger for each ad, you can use a Message Template with an autofill message.

For example:
"I'm interested to learn more."

Then, set your flow to trigger when a user sends this message. This way, all ads using that template will route leads into the same workflow.

​@AwaisToor thank you but this method isn’t compatible with CAPI. Conversions won’t return to Ads Campaigns because the CTWA trigger isn’t available as this is the only way ManyChat is getting the Ad ID the user is coming from, which is nuts, because in the new age of Meta Ads, the more ads you can test and add to your campaigns the better. This is unreliable at scale.

MANYCHAT NEEDS TO IMPROVE THIS, AS OTHER COMPETITORS ARE DOING.

​@roverdrammen 
After that point in the automation, add an action node and select + Action > Ads Optimizations > Send event to Meta Conversions API

To learn more about CAPI, follow this link:
https://help.manychat.com/hc/en-us/articles/14580897414300-Conversions-API-CAPI-integration

 

​@AwaisToor yes, I’m aware of that. But it won’t track the conversion because apparently the CTWA trigger is the only way ManyChat can connect the user with the Ad/Campaign in question. This is information I got from the official support team via a support ticket, when reporting that I was not seeing conversions in my CTWA campaigns.

And apparently none else from the team will ever comment on this subject. There is no a tiny piece of interest on improving this much needed feature.

Hi, I have the same issue. Is there any way to automatize an AdIdList in a google sheet for example? And sotre the data in fields to trigger CTWA ?

Hey! Im having the same issue! Did you found a workaround?

​@roverdrammen I agree with every word you say, what you are describing is indeed a real and existing issue :(

​@AwaisToor  it seems to me that you may be answering a different question and not fully addressing the essence of the problem.

I’m facing the same issue, and it is still unresolved in 2026.

Requiring users to manually create and maintain a separate CTWA trigger for every single ad is not scalable. Many businesses continuously test and launch multiple new ad creatives every week.

Using the same pre-filled message across all ads is not a real solution because it routes contacts into the workflow but does not preserve reliable ad-level attribution or the data required for CAPI.

Manychat needs:

1. A global “All CTWA Ads” trigger.
2. Automatic capture of source_id / Ad ID, campaign, ad set, ad name, and ctwa_clid.
3. These values exposed as system fields, workflow variables, and webhook/API parameters.
4. The ability to save the source dynamically into a contact field or use it for routing and CAPI events.

Other platforms already process the referral metadata provided by Meta without requiring users to configure every ad manually. This limitation makes Manychat difficult to use for businesses that continuously test and launch many different ad creatives.

Could someone from the Manychat product team please confirm whether this improvement is on the roadmap and provide an estimated timeline?