When someone taps a click-to-WhatsApp ad on Facebook or Instagram and writes to your WhatsApp Business (WABA) number, Meta tells us which ad the message came from. TimelinesAI keeps that information on the chat and on the message, so you can see which chats each ad brought in, who is handling them, and what happened next.
Ad attribution is available through the Public API and webhooks. There is no separate screen for it in the inbox.
What you get
The ad behind each chat. Every WABA chat lists the ads and posts that reached it.
Chats by ad. Filter your WABA chat list by an ad and a date range.
The ad on each message. A message that came from an ad carries that ad's details.
Real-time notifications. The new-chat and new-message webhooks include the ad details.
Meta Ads Manager already shows how many conversations an ad started and what it cost. TimelinesAI adds the chats themselves. The ad ID is the same in both places, so you can match them.
Prerequisites
✅ A WhatsApp Business (WABA) number connected to TimelinesAI. Ad attribution does not work for numbers connected by QR code. → Check your WABA numbers
✅ The Pro plan.
✅ A click-to-WhatsApp ad in Meta Ads Manager that sends people to that number.
✅ A Public API token, or a webhook subscription.
No WABA number yet? See WhatsApp Business Accounts (WABA) integration with TimelinesAI to connect one.
What is saved for each ad click
Field | What it holds |
|---|---|
| The Meta ad ID. Empty when Meta does not send one |
| The ad's headline |
| The link to the ad or post |
|
|
| When the message arrived |
| The message that carried it |
One person can tap several ads over time. Each tap that leads to a message adds a new entry to the same chat. The first entry stays.
Find the chats from an ad
Add these filters to the WABA chat list (GET /waba/chats):
ads_source_id— chats that received a message from this adads_source_after— the message arrived at or after this timeads_source_before— the message arrived at or before this time
You can combine them with the filters you already use: WABA number, assignee, open or closed, and phone number.
Example: open chats that received ad 1234567890 between 20 and 27 November:
GET /waba/chats?ads_source_id=1234567890&ads_source_after=2026-11-20&ads_source_before=2026-11-27&closed=false
Each chat in the answer has a referrals list. A chat that was opened by one ad and later reached by another is returned for either ad. These filters match ads only, not organic posts.
See the ad on a chat or a message
Chat — the WABA chat list and the single chat return
referrals, oldest first. The list is empty when no message in the chat came from an ad or a post.Message — the WABA chat history and the single WABA message return
referral. It isnullwhen the message did not come from an ad or a post.
Get notified by webhook
New Incoming WABA Chat (
waba:chat:incoming) now includes the first message of the chat. When that message came from an ad,message.referralholds the ad details.New Incoming WABA Message (
waba:message:received) includesmessage.referralfor a message that came from an ad.
When an existing contact taps another ad, no new chat is created. You get a new-message notification with the new ad details.
Good to know
Important: Ad details are saved for messages that arrived on or after 19 November 2026. Earlier messages have none.
TimelinesAI saves ad details on every plan, and shows them on Pro. If you upgrade to Pro later, the ad details saved since 19 November 2026 appear right away.
The ad ID is the ad, not the campaign. Campaign names and spend stay in Meta Ads Manager.
Only new fields were added. Existing API calls and webhook subscriptions keep working.
Troubleshooting
What you see | What it means | What to do |
|---|---|---|
| Your plan does not include ad attribution | Upgrade to Pro. The other chat filters keep working |
| Your plan does not include ad attribution, or the message arrived before 19 November 2026 | Check your plan and the date of the message |
A chat from an organic post does not appear for an ad filter | The filters match ads only | Read the chat's |
The ad's campaign name is missing | Meta sends the ad ID only | Look up the ad ID in Meta Ads Manager |
FAQ
Can I see ad details in the TimelinesAI inbox?
Not at the moment. They are available through the Public API and webhooks.
Does it work for numbers connected by QR code?
No. Meta sends ad details only for WhatsApp Business (WABA) numbers.
Will my older chats show the ad they came from?
No. Ad details are saved from 19 November 2026 onwards.
The same person tapped the same ad twice. Is it counted twice?
Each message that came from the ad adds an entry to the chat. The chat itself is returned once.
Where is the full API reference?
See Get WABA chats in the API documentation.
