Hi BotSailor team,
Many businesses on your platform acquire customers through Click-to-WhatsApp (CTWA) ads on Meta. Today, BotSailor can receive and automate those conversations, but it gives no visibility into which ad or campaign produced them, and it cannot report outcomes back to Meta. For anyone running paid ads, this is a significant gap. We’d like to request the four improvements below.
1. Ad and campaign attribution on CTWA conversations
Current behavior: BotSailor does not track which ad or campaign generated a WhatsApp conversation. As a result, attribution details can’t be passed through webhooks as labels (label_names) or custom fields.
Request: When a conversation starts from a CTWA ad, capture the referral data Meta provides with the first message (ad ID, ad name, campaign, ad set, source URL, ctwa_clid, headline/media where available) and:
- Store it on the subscriber record as system custom fields.
- Include it in webhook payloads.
- Make it usable in flows (conditions, auto-labels, custom field assignment).
- Show it in the inbox and contact profile.
2. Attribution for ads created in Meta Ads Manager
Current behavior: Conversations from ads created directly in Meta Ads Manager are received and automated, but the specific ad or campaign isn’t identified.
Request: Apply the same attribution capture (point 1) to every CTWA conversation, regardless of where the ad was created. Most advertisers and agencies build campaigns in Ads Manager, so attribution must not depend on ads being created inside BotSailor.
3. Read-only Meta ad account connection
Current behavior: The CTWA Ads integration requires the ads_management permission, which lets BotSailor create and manage ads. A read-only connection isn’t supported.
Request: Offer a read-only option using ads_read so users can connect an ad account just to view and attribute performance, without granting write access. Many agencies and security-conscious businesses won’t grant ads_management to a third party only for reporting. Keep ads_management as an optional upgrade for users who want to create ads from BotSailor.
4. Native Meta Conversions API (CAPI) for Business Messaging
Current behavior: There’s no native way to send conversion events such as Lead or Purchase to Meta.
Request: Add a native CAPI integration for Business Messaging that:
- Sends standard events (
Lead,Purchase,InitiateCheckout,AddToCart, etc.) with the storedctwa_clid, WhatsApp Business Account ID and dataset ID. - Can be triggered from a flow action, a label change, a custom field update, or an order event.
- Supports event value and currency.
- Includes an event log with delivery status and errors for debugging.
Why this matters
- Reporting: Without ad-level attribution, advertisers can’t tell which campaigns produce real conversations and sales, so ROI can’t be measured.
- Ad optimization: Meta’s delivery depends on conversion signals. Without CAPI, Meta only optimizes for conversation starts, not qualified leads or purchases, which raises cost per result.
- Competitive parity: Other WhatsApp automation platforms already offer CTWA attribution and CAPI, and users are asking for it.
- Retention: A good share of BotSailor customers run Meta ads, and missing this is a reason to move to or add another tool.
Even a phased release would help, with attribution capture (points 1 and 2) first, then CAPI (point 4), then read-only access (point 3).
Thank you for considering this. We’re happy to test a beta or share more details about our setup.