When Timi sends Purchase to Meta from WhatsApp (M-Pesa, mark sold)
Close the loop between M-Pesa confirm and mark sold in Feed so Purchase events reach Meta Ads Manager — not just qualified leads.
7 August 2026 · 7 min read · Timi Labs
A Nairobi accessories seller sees M-Pesa receipts in the till book but no recorded sales against last week's WhatsApp ad chats. Before deciding that tracking failed, check whether the team confirmed those payments in Feed. A receipt outside Timi does not automatically create a recorded chat outcome.
Timi reports Purchase for a recorded sale when tracking is ready and supported CTWA attribution is present. Check your payment records, then confirm an M-Pesa suggestion or mark sold in Feed. A screenshot alone is not independent payment verification. Organic sales are not reported as ad conversions.
This guide owns the seller-confirmation habit. Use the Meta connection guide for setup and the ROAS guide for reviewing value against spend.
Why Purchase matters more than conversation count
Meta can optimise toward many signals — link clicks, conversations, leads. Kenyan WhatsApp sellers care about M-Pesa in the till. Compare recorded sales, spend and margin rather than conversation count alone. A hypothetical campaign with many greetings and few sales may need work, but its profitability cannot be judged without costs and complete records.
Purchase is the event that tells Meta which ad sets produced paying buyers. Qualified lead events show interest; Purchase shows money changed hands. Missing Purchase reporting leaves an incomplete view of sales. It does not prove the campaign found poor buyers; first check whether the sales were recorded and events were eligible to send.
Treat payment confirmation like inventory control: assign an owner, record actual amounts and reconcile against the shop’s accounts.
Record a confirmed sale in Feed
For supported Click-to-WhatsApp ad chats, Timi can report Purchase when tracking is ready and one of these records a sale:
- M-Pesa confirmed in chat — your team confirms the buyer's M-Pesa message or screenshot in Feed
- Mark sold in Feed — you mark the chat sold for cash, till, or any offline payment you record in Timi
- In-flight Paystack checkout paid — a buyer Paystack link already sent before checkout was retired can still mark paid
The Paystack path is historical compatibility, not a checkout option for new buyers. Each supported path records an outcome that can be reported; Meta controls whether the event is credited to a campaign. New sales close on Till / Paybill — Timi does not send buyer checkout links. Confirm or mark sold so Purchase fires.
For quoting totals and Till collection habits, see delivery fees and M-Pesa on WhatsApp. Purchase reporting still depends on you recording the sale in Timi — not only in your till book.
Team playbook: who does what
Assign one habit per payment type so Purchase is not orphaned:
Till and Paybill M-Pesa. The buyer pays; a confirmation SMS or screenshot lands in chat. Someone on the team reconciles the payment and confirms M-Pesa in Feed promptly. A pasted message or screenshot must be checked against your own payment records. If only finance sees the till notification and never opens Timi, Purchase stays zero.
Cash on delivery or walk-in handoff. Driver collects cash; chat started from an ad last week. Mark sold in Feed when dispatch confirms payment — link the chat to the sale even if payment happened offline.
Write a one-line rule in your team WhatsApp group: "Ad chat paid → confirm M-Pesa or mark sold before close of day." Keep a daily reconciliation so payment records and chat outcomes do not drift apart.
CTWA-only: organic sales do not feed ad optimisation
A buyer from your Instagram bio can pay KES 8,000 by Till. That is a win in Feed and CRM — Timi does not send that sale to Meta as an ad conversion. Only chats that arrived with Click-to-WhatsApp referral carry the data Meta needs to optimise paid campaigns.
This keeps the reported source honest. Do not assign an organic receipt to an active ad merely to make the campaign totals look complete.
Nurture organic in Feed. Use native CTWA ads for the supported attribution path. Campaign objectives and budget changes remain your responsibility in Ads Manager. Separate weekly reviews: ad ROAS on Timi Ads and Ads Manager; organic revenue in your internal sheet.
Cross-check one sale end to end
Pick one known sale from last week and walk the chain:
- Feed — chat shows paid / ad attribution label (from CTWA)
- Payment action — M-Pesa confirmed or mark sold recorded
- Settings → Ad conversion tracking — Signal health shows Purchase sent in the last seven days; event log row status Sent
- Meta Events Manager — inspect the destination and reporting period for the received event; processing can lag
If the chat and sale records are correct but the event failed or was skipped, inspect tracking readiness and attribution. If the event was sent but is missing from Meta’s view, follow its destination and reporting hints rather than assuming every event uses the setup-test pixel — see connect Meta Ads troubleshooting.
Purchase in Meta vs your ops record
| Record | Purpose | Purchase to Meta? |
|---|---|---|
| Till / M-Pesa business SMS | Cashflow and finance | No — until confirmed or mark sold in Timi |
| Timi Feed mark sold / M-Pesa confirm | Sales ops + ad loop | Yes — for CTWA chats |
| Friday spreadsheet upload | Legacy media buyer habit | Avoid if CAPI live — duplicates risk |
Till / M-Pesa business SMS
- Purpose
- Cashflow and finance
- Purchase to Meta?
- No — until confirmed or mark sold in Timi
Timi Feed mark sold / M-Pesa confirm
- Purpose
- Sales ops + ad loop
- Purchase to Meta?
- Yes — for CTWA chats
Friday spreadsheet upload
- Purpose
- Legacy media buyer habit
- Purchase to Meta?
- Avoid if CAPI live — duplicates risk
Record scenarios above.
Your accountant still needs till exports. CAPI Purchase replaces the Meta upload bridge — not your books.
A sent Purchase is not an identical Ads Manager total
Timi's sale record, the event received by Meta and the campaign's credited conversion are three different views. Matching, attribution windows and reporting dates can make the totals differ. Keep the same review period and inspect one sale end to end before changing settings or uploading duplicates.
Recorded revenue is not profit. It also does not prove Timi or the ad caused the purchase. Check margin, delivery costs and refunds in your finance records before making a budget decision.
If you sell products mainly through WhatsApp and already run Meta ads opening chat, review the ads overview and pricing, then use Connect WhatsApp below. You do not need a website or AI replies to record and review supported outcomes.
Common mistakes
- Qualified leads rising, Purchase flat — team collects M-Pesa but never confirms in Feed
- Comparing till total to Ads Manager Purchase without filtering CTWA-attributed sales
- Waiting for a checkout link to mark paid — buyer checkout is retired; confirm Till yourself
- Expecting Purchase from organic bio traffic — only CTWA ad chats report to Meta
- Blaming broken CAPI when ad destination was wa.me instead of Click-to-WhatsApp
- Duplicate reporting — CSV upload plus live CAPI for the same sale
Read the WhatsApp ads pillar guide for campaign structure and budget discipline.
FAQ
How fast does Purchase appear after I mark sold? Inspect the event log first. Sending and Meta reporting are separate steps; processing can lag and no exact arrival time is promised.
We only use Till — do we need a checkout link for Purchase? No. Confirm M-Pesa in chat or mark sold for every CTWA sale. Timi does not send buyer checkout links.
Purchase fired twice — is that bad? Timi deduplicates by event design for the same milestone. Do not also upload the same sale via spreadsheet.
Can my rider mark sold? Anyone with Feed access can — assign who owns ad-chat closes so nothing slips.
Does partial deposit count as Purchase? Purchase reflects how you record the sale in Timi when payment is confirmed or marked sold — align with your shop policy for deposits vs full pay.
What if a paid buyer has no ad-source label? Payment status and ad source are different. The chat may be organic or have incomplete attribution. Check both records; do not invent the source.
Share this guide