Skip to content

Track WhatsApp leads in Meta Ads Manager

Set up a WhatsApp reporting view in Ads Manager, align dates, inspect received events, and reconcile credited purchases with seller-confirmed outcomes.

17 June 2026 · 6 min read · Timi Labs

Imagine a Nairobi shop's Friday review: Ads Manager shows 240 conversations, while the till records 11 payments. Those hypothetical counts describe different stages and may include different sources. Neither tells you, on its own, how many recorded CTWA sales Meta credited to the campaign.

Use Ads Manager for campaign delivery and credited conversions; use Timi for ad chats and seller-recorded outcomes. Match date ranges, select the relevant event columns, and reconcile a known sale before changing spend. An event received in Events Manager is not automatically a purchase credited in Ads Manager.

This guide owns the weekly reporting review. Use the connection guide for Settings setup and the Timi ROAS guide for chat-side calculations.

Start with one question and one reporting period

Choose a question such as “Which ads produced recorded sales last week?” Set the same dates in Ads Manager and Timi, and note the account timezone. Keep the same saved view across reviews so a column change does not look like a performance change.

Finance totals include all receipts, while ad reporting covers a narrower source and reporting window. Keep organic Till payments separate. When results differ, inspect source, payment status, event status and credited conversion before deciding one system is wrong.

Events Timi reports (default mapping)

Timi sends CAPI events for Click-to-WhatsApp ad chats — see connect Meta Ads for the full milestone list (Lead submitted through Purchase). Rename in Settings if your media buyer uses custom conversion names — keep Timi and Ads Manager columns aligned.

Set up Ads Manager columns for WhatsApp funnels

After connecting Meta Ads:

  1. Open Ads Manager → Columns → Customize columns.
  2. Add spend, conversations, the available lead or custom-conversion columns matching your event mapping, Purchases, Cost per purchase, and Purchase conversion value where available. Column availability depends on Meta’s reporting view and account configuration.
  3. Add Checkout started if that event is mapped and available. Keep the label consistent with Settings; a handoff is not a paid sale.
  4. Save as a preset — "Timi WhatsApp weekly" — so every review uses the same view.

Where to verify events live

Events Manager (dataset / pixel view):

  • Use Test events only with a matching test code for the setup test; otherwise follow Timi’s hint to Overview
  • Use Overview for volume spikes when campaigns launch
  • Diagnose missing Purchase — are Lead events arriving but Purchase flat?

Ads Manager (campaign view):

  • Filter by date range matching your till reconciliation
  • Compare ad sets on Purchase and cost per purchase
  • Cross-check one known sale. Meta may credit it under its own attribution and date rules, so do not assume the campaign report uses the mark-sold date.

Timi Feed is the ground truth for chat — who paid, who stalled, who came from paid traffic. The Ads dashboard merges spend with qualified leads and revenue. Ads Manager is the aggregation layer for budget moves.

Weekly review ritual (15 minutes every Friday)

  1. Sort ad sets by Purchase — not spend, not Lead count.
  2. Investigate spend without sales. Check payment recording and reporting completeness before judging the offer or creative.
  3. Choose a bounded next test using recorded outcomes, costs and your shop’s margin. Avoid a universal budget rule based on a small sample.
  4. Check first-reply quality on top-spending ad set — open three paid chats in Timi Feed; did first reply match ad promise?
  5. Pick one stalled Purchase — pricing surprise, delivery zone, or slow handoff? Fix shop context or handoff rule, not just bid.

Log one sentence in your team chat: "Scaled Ad set A; paused B (Leads yes, Purchase no); fixed delivery fee in context." The habit of logging it matters more than which dashboard you read.

Reading common patterns

  • High Lead, low Purchase — Tyre-kickers or wrong price in chat. Fix shop context; tighten ad creative promise
  • Purchase concentrated on one placement — Compare spend, sample size and reporting settings before changing placement allocations
  • Lead drop after creative change — New ad misaligned with context. Revert creative or update context same day
  • Purchase strong, Lead flat — Check the event mapping and attribution window; different counts do not establish the cause

Connect Meta Ads in Timi (prerequisite checklist)

If events are missing entirely, re-run setup — do not debug columns first:

  1. Settings → Ad conversion tracking → Connect Meta Ads
  2. Correct business, dataset and ad account
  3. Send conversion events to Meta on
  4. Ads use Click-to-WhatsApp destination — see CTWA tracking
  5. Send test event → follow the test-code hint, then verify a genuine ad-chat outcome

Timi sends Purchase when you confirm M-Pesa in chat or mark sold in Feed — see when Timi sends Purchase.

Received events are not credited campaign sales

Events Manager helps verify receipt and diagnostics. Ads Manager applies matching, attribution windows and campaign reporting rules. A sent Purchase in Timi can therefore exist without an identical campaign count or value. Do not upload it again just to force the totals to match.

Keep a short reconciliation note: selected dates, source of the chat, confirmed amount, Timi event status and the Meta view inspected. This creates a repeatable review without treating association as proof the ad or Timi caused revenue.

If you sell products mainly through WhatsApp and already run Meta CTWA ads, review the ads overview and plans, then use Connect WhatsApp below. A website is not required and AI replies are optional.

Common reporting mistakes

  • Optimising on conversation count Meta shows natively without CAPI Purchase
  • Comparing Ads Manager Purchase to till total without date lag — events can batch
  • Scaling budget before Purchase column has 7+ days of data
  • Mixing organic till payments into ad-set decisions — filter on CTWA-attributed Purchase when testing ads
  • Changing event names in Timi without updating saved column presets

See the WhatsApp ads pillar guide for campaign creation and budget starting points.

FAQ

How long until Purchase shows after connect? Connection alone creates no Purchase. A real attributed sale must be recorded and reported; Meta processing and campaign reporting may lag. Inspect the event status rather than assuming an exact delay.

Should I still export chats to Excel? For internal ops yes; for Meta optimisation no — use live CAPI.

Cost per purchase looks too high — is CAPI broken? Compare three known sales to event timestamps first. Often creative or pricing is the issue, not tracking.

Can my media buyer access Timi Feed? Share screenshots of stalled chats weekly — connects reporting to conversation reality.

What if Purchase is zero but till has money? Check mark sold discipline, M-Pesa confirmation habit, and whether those buyers came from organic not ads.

Track WhatsApp leads in Meta Ads Manager | Timi