For Performance Marketers & Ads Agencies

Don’t let ad data vanish in chat.

Optimize your ad spend with automated Conversions API (CAPI) and smart WhatsApp tagging. Track every signal from ad click to chat closing.

Start free
  • Tell Meta who just asked for a price and who actually bought
  • Send conversion events server-to-server, de-duplicated with your Pixel
  • Build audiences from conversations, not empty clicks
4.5· Shopify App Store
Ads Performance

Feed the algorithm what happens after the click.

Meta optimizes on the signals it receives. Most WhatsApp outcomes never reach it. These three close that gap.

Accurate CTWA attribution for Meta — no more blind spots

Meta’s algorithm needs to know who just asks for prices and who actually buys. Smart tags written to the conversation — like Qualified or Purchased — go straight back to Ads Manager through CAPI, so the algorithm learns to find higher-intent leads.

  • Every CTWA chat is source-tagged with campaign, ad set, creative, and entry point
  • Lead, qualified-lead, and purchase events fire from the customer record as the chat progresses
  • Meta optimizes on closed outcomes, not just conversations started
Signalchat outcomes, back in Ads Manager

Anti-leak server-side CAPI

Bypass browser limitations and ad-blockers. Conversion events go server-to-server from the customer record, with a unique event ID per conversation so they de-duplicate against your existing Meta Pixel instead of double-firing.

  • Server-side events survive iOS, cookie, and ad-blocker signal loss
  • Shared event ID with your Pixel — run both, Meta combines them
  • Validate in Meta’s Test Events tool before going live
Server-sideno browser in the loop

Advanced retargeting & lookalikes

Build Custom Audiences from conversational intent, then seed Lookalikes from people who actually held high-intent conversations — not from everyone who clicked.

  • Tags and segments sync to Meta as Custom Audiences
  • Seed Lookalikes from qualified conversations, not clicks
  • Audiences refresh as tags on the record change
Intentaudiences built from real conversations

CAPI sends the conversation outcome back to Meta, de-duped against your existing events — see the Meta Conversions API integration. The full CTWA → tag → audience loop lives on WhatsApp Marketing.

Any Ad Source

Qualify leads from any ad source with prefilled messages.

Not every click comes from a Meta ad. Google Ads, TikTok, a landing page, a QR code, an influencer link — if the call to action opens WhatsApp with a prefilled message, the first message arrives in the thread carrying its own source.

One link per campaignhttps://wa.me/<your-number>?text=Hi%2C%20I%27m%20interested%20in%20the%20summer%20sale.%20Ref%3A%20GADS-SUMMERStandard WhatsApp click-to-chat link. Works with any WhatsApp number — no integration on the ad platform.
  1. 01

    Write a distinct prefilled message per source

    Put the campaign, ad group, or placement in the text — “Ref: GADS-SUMMER”, “Ref: QR-STORE-01”. One link per ad, landing page, or placement.

  2. 02

    The first message opens the record and carries the source

    When the customer taps send, the chat opens a customer record on their phone number, and your source code is the first thing in the thread.

  3. 03

    The agent qualifies in the thread

    The AI agent reads the opener like any inbound message and asks the qualifying questions you configured in AI Studio, writing the answers to the record.

  4. 04

    Tags group every lead by source

    Set your own tag values in AI Tagging so a source code or intent keyword lands as a tag — then filter, segment, and compare lead quality by ad source.

Meta ads get automatic CTWA attribution; every other source runs on the prefilled message. A customer can edit the text before sending, so treat the code as a strong signal, not a guarantee — and use one link per source. Build links with the free WhatsApp link generator.

FAQ

Ads performance FAQ.

No. Events carry a unique event ID per conversation and bitbybit matches it to your Pixel, so Meta de-duplicates server-side and browser events instead of counting both. Run the Pixel and CAPI in parallel and validate in Meta’s Test Events tool.

Lead, add-to-cart, and purchase events fire from the customer record as the conversation progresses. You choose which actions trigger an event when you connect your Meta Business account.

No. CTWA gets automatic source attribution because Meta passes the ad context into the chat. For any other source — Google Ads, a landing page, a QR code — use a WhatsApp link with a prefilled message that carries a source code, and the agent and your tagging rules take it from there.

Yes. WhatsApp lets the customer edit or delete the text before sending, so a prefilled code is a strong signal rather than a guarantee. Use a distinct link per source and put the code where it is hard to miss.

Replies from click-to-Messenger ads and Instagram DMs land on the same AI agent and customer record as WhatsApp, where they are tagged and routed like any other lead. The CAPI and prefilled-message mechanics on this page are built around WhatsApp conversations; ask us about your DM setup.

No. Your ad accounts, pixel, and Events Manager stay as they are. bitbybit adds the conversions that happen in the chat — the ones the browser never sees.
Get started

Show the algorithm what a good lead looks like.

Send chat outcomes back to Meta, tag every source, and build audiences from real conversations. Free trial — no credit card required.

4.5· Shopify App Store