Skip to main content

Currently for the CAPI to work properly, we need to ad CTWA trigger for every single ad we use on our campaigns. This is simply not sustaible at scale, what happen when we use dozens of ads per campaign, adding more variations and angles every day or week.

I’ve seen in other competitors that this is not the case, CAPI works just fine with leads coming from ads. Having no need to add a CTWA trigger to get workflow working as expected.

Please, we need ASAP. It’s vital in the new age of Meta Ads.

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.


Reply