Track WhatsApp leads in Meta Ads Manager

Friday 4pm. Your media buyer asks: "Which ad set actually made money last week?" Ads Manager shows 240 conversations and 89 leads. Your till reconciliation shows 11 M-Pesa payments from WhatsApp. The gap is not Meta lying — it is measuring Lead when the business cares about Purchase. This guide is the weekly operating rhythm: where to click in Ads Manager, which columns matter, and how Timi's CAPI events map to decisions.

For OAuth setup see connect Meta Ads. For why CTWA beats spreadsheets see spreadsheet uploads fail.

Why manual tracking fails

Uploading lead spreadsheets weekly means:

• Events arrive too late for Meta to optimise in real time — Monday's winner cannot inform Sunday's spend
• Paid and organic chats get mixed in one export — noisy signals
• Finance and marketing disagree on what "converted" means — till vs uploaded row vs mark sold in Timi
• Your team spends Friday evening cleaning phone formats instead of shifting budget

Timi sends events automatically when milestones happen in chat. Your job shifts from data entry to decisions.

Events Timi reports (default mapping)

• Buyer first messages: Lead
• Checkout link sent or handoff: InitiateCheckout
• Paystack paid, M-Pesa confirmed, or mark sold: Purchase

Rename events in Timi 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 Leads, Purchases (or your custom Purchase name), Cost per purchase, Purchase conversion value if you pass values.
3. Add Initiate checkout if you use checkout links before till payment.
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 after OAuth connect
• 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 — buyer from ad X, marked sold Tuesday, Purchase on Tuesday?

Timi Feed is the ground truth for chat — who paid, who stalled, who came from paid traffic. 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. Pause ad sets with spend > 2× your target cost per purchase and zero Purchase in 7 days.
3. Scale ad sets with stable Purchase and acceptable cost — increase budget 20%, not 3× overnight.
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." Consistency beats perfect dashboards.

Reading common patterns

• High Lead, low Purchase — Tyre-kickers or wrong price in chat. Fix shop context; tighten ad creative promise
• Purchase on one placement only — Reels vs Feed split. Shift budget to winning placement
• Lead drop after creative change — New ad misaligned with context. Revert creative or update context same day
• Purchase strong, Lead flat — Retargeting or small audience. Expected — watch frequency caps

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 Manager and pixel
3. Send conversion events to Meta on
4. Ads use Click-to-WhatsApp destination — see CTWA tracking
5. Send test event → confirm in Events Manager

Timi sends Purchase when a lead pays via Paystack, M-Pesa confirmation in chat, or mark sold in Feed.

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
• Ignoring organic Purchase events mixed into totals — filter attributed campaigns 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? Test events are immediate. Live Purchase depends on buyers paying — often same day once ads run.

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.