
You can now trigger the same journey across all your CTWA campaigns with the new “
All
” selection in the Lead from CTWA trigger component.🔧 What Problem This Solves:
Previously:
- You could use the CTWA trigger only once in a single bot journey.
- Users had to rely on an On Message triggerwith anIs CTWA conditionto start CTWA journeys for multiple campaigns.
- This approach lost critical metadatasuch as: Campaign ID, Campaign Name, Ad ID, Ad Name about a lead
✅ All of this is now fixed!
You can now
retain full ad-level metadata
while triggering journeys seamlessly.🚀 What’s New with the Updated CTWA Trigger
✅ Trigger multiple bot journeys after connecting your Facebook Ad Account to DoubleTick.
✅ Track campaign and ad performance accurately using the captured metadata.
✅ Use one single journey across all your campaigns with the new “All” selector.
Also, the Lead from CTWA Trigger (v2) could only be used once, and the bot studio used to throw the following error if the user tried using the component on another bot journey.
This is fixed now!
⚠️
Important Notes to Keep in Mind
🧹 If you're using the old CTWA component in any bot,
delete it before using the new one
—else it will throw a usage error.🧩 Your
Facebook Ad Account
must be mapped
to the same Business Manager
that your WhatsApp
Account
is linked with.👉 If your campaign list appears blank, this is likely the issue. Contact DoubleTick Support and the team will help you out with mapping it—it’s super simple!
🔄 If you've accidentally configured two bots for the same campaign and its subset, the one with the lowest trigger level will fire.
Example:
Let’s say you’re running a campaign called “
Diwali Sale
”It has two Ad Sets: “
Menswear
” and “Womenswear
”Inside each Ad Set, there’s one Ad: “
Menswear Ad
” and “Womenswear Ad
”Now, if you
accidentally
create journeys for both the entire “Diwali Sale” campaign and the specific “Menswear Ad”:👉
The journey for “Menswear Ad” will be triggered
🚫 If you configure two journeys for the same Ad (e.g., AA1), the bot will throw an error 'The trigger is being used in Another component.
Avoid duplicate setups.
Try this out now! 🚀