Ad posts: a scenario for every ad you run
Ad posts: a scenario for every ad you run
Add an ad’s ID once and two things happen — the bot starts answering leads from that exact ad, and the ad gets its own slot in automations for its own script
Most agencies don’t run one ad — they run five offers through five creatives into the same inbox. The Ad posts card is how you keep those five apart: add an ad’s ID to the list, and Chatfuel starts answering leads from that exact ad — with a script you can tailor to it. The whitening ad qualifies for whitening, the checkup ad for checkups, and nobody gets a generic “How can I help?” after clicking a very specific promise.
What adding an ad does
Adding an ad ID to the Ad posts card does two things at once:
- The bot picks up that ad’s leads. Messages arriving from that specific ad are now answered automatically — the ad is on the list, so its traffic is the bot’s job.
- The ad becomes an object in automations. Each ad on the list gets its own slot in the automations hierarchy — Main bot → Source → Object. Override only what this ad needs — its own AI instructions, its own follow-ups — and everything you don’t touch is inherited from the levels above. No duplicating the whole setup per campaign.
This isn't ads management
Campaigns, budgets, and creatives still live in Meta Ads Manager — Chatfuel doesn’t touch them and doesn’t need to. All it needs is the ad’s ID to own everything after the click: the instant answer, the qualification, the handoff.
Before you start
Two prerequisites:
- The channel is connected — the client’s Instagram or WhatsApp is already linked to their company in Chatfuel.
- The ad has a single messaging destination. In Ads Manager, tick only Instagram Direct or only WhatsApp under Messaging apps. An ad pointing at two destinations won’t route traffic reliably.
Get the ad ID from Ads Manager
Grab the right ID
The same URL also carries selected_campaign_ids and selected_adset_ids — those are the campaign and ad-set IDs, and they won’t work here. You want the number after selected_ad_ids.
Add the ad in Chatfuel
Open the Ad posts card
In the client’s company, open Automations and find the Ad posts card for the channel the ad clicks into.
Give the ad its own scenario
The moment an ad is on the list, it exists as an object in Automations — open it there and override whatever this campaign needs: the AI’s instructions, the qualification questions, the follow-ups. Or skip the hierarchy entirely and tell the Co-Worker in one sentence: “For the whitening ad, ask which clinic location is closer and hand off once budget and preferred date are collected.”
Everything you don’t override is inherited from the source and the Main bot — so a per-ad scenario is one or two changed settings, not a rebuilt bot. And because attribution pins every conversation to the ad that produced it, the right script runs even after the lead moves into a plain DM thread.
Meta-side gotchas
- Don’t crop the image in Ads Manager. Cropping makes Meta assign the ad a new ID — the one on your list stops matching. If you must crop, re-copy the new ID and update the list.
- One messaging destination per ad. Two ticked destinations is the most common reason an ad’s traffic never reaches the bot.
- Ad delivers but the bot stays silent? Walk the funnel like a lead — start with ads troubleshooting and bot troubleshooting.
Where to next
How conversations stay pinned to the ad that produced them — the model behind per-ad scenarios.
The same per-object trick for organic traffic — one trackable DM link per campaign.
Symptom → fix for every break point between the ad click and the qualified lead.
What the AI asks once the right per-ad scenario is running.