Skip to content

How to read ROAS on Timi's Ads dashboard (WhatsApp CTWA, Kenya)

Use Timi's Ads page for ROAS, cost per qualified lead, funnel drop-off, and per-ad decisions — alongside Meta Ads Manager.

7 August 2026 · 7 min read · Timi Labs

A Nairobi furniture shop's owner wants to review the weekend drop: what did ads cost, which chats showed product interest, and what sales did the team record? Opening three apps and dividing the till total by ad spend mixes organic receipts with ad outcomes.

Timi's Ads page compares supported ad-chat outcomes with connected Meta spend. ROAS is recorded ad-attributed revenue divided by spend; it is neither profit nor proof the ads caused all that revenue. Complete the connection and sale records before using the number to make decisions. AI replies are optional.

This is the dashboard operating guide. For setup read Connect Meta Ads; for campaign-side reports read Ads Manager review. The Purchase guide covers recording the sale.

What the Ads page is for

Timi Ads answers one question Meta spend reports alone cannot: "Which Click-to-WhatsApp campaigns produced qualified interest and recorded sales on my WhatsApp line?"

Meta Ads Manager shows delivery, spend and credited conversions under Meta’s reporting rules. Timi adds recorded chat outcomes — who messaged from an ad, who engaged beyond a bare Hi, whose sale your team recorded — merged with spend when Meta Ads is connected.

You still create and edit campaigns in Ads Manager. Timi does not change budgets or creatives. Use the Ads page to review the funnel and choose the next bounded test. A short period with a few sales is not enough evidence for an automatic pause-or-scale rule.

If Meta is not connected or spend access is incomplete, finish Connect in Settings. Treat unavailable spend or ROAS as incomplete reporting, not a measured zero.

Five KPIs on the summary row

Pick a period (7d, 30d, 90d, or all) with the date picker. The top row shows five numbers:

ROAS (return on ad spend). Ad-attributed revenue divided by Meta spend in the period — For a hypothetical example, KES 42,000 in recorded ad revenue and KES 10,000 in spend gives 4.2×: KES 4.20 revenue per KES 1 spent. These are illustrative figures, not customer results. Use this as your headline health check. Below 1× means you spent more on ads than Timi recorded from attributed sales — investigate before scaling.

Cost / qualified. Meta spend divided by engaged ad leads — not raw chat count. Thin "Hi" openers are excluded from this denominator. Compare week over week; if it rises, inspect spend, sample size, the offer and chat responses before deciding why.

Cost / chat. Spend divided by all ad-attributed chats, including thin openers. The gap between cost / chat and cost / qualified shows how much budget buys curiosity vs interest.

Qualified rate. Percentage of ad chats that moved past thin openers, with counts for engaged leads and thin Hi shown below. A drop after a new Reel is a reason to review the conversations, not proof the creative caused it — see qualified vs thin Hi.

CPC and total spend. Context for whether Meta delivery got expensive independent of WhatsApp close rate.

Funnel: Ad chats → Qualified → Sales → Revenue

Below the KPIs, the funnel bar chart shows drop-off in the selected period:

  1. Ad chats — Click-to-WhatsApp conversations that started
  2. Qualified — chats that engaged beyond a bare greeting
  3. Sales — recorded purchases from ad-attributed chats
  4. Revenue (KES) — total sale value tied to those ads

Read conversion percentages between steps. Strong qualified count with weak sales often means pricing surprise, delivery zone gaps, or missing Purchase loop — team not confirming M-Pesa or marking sold.

Weak qualified with strong ad chat volume points to creative or first-reply mismatch — fix shop context before raising budget.

Per-ad table: pause vs scale

Scroll to per-ad performance when you run multiple creatives or ad sets. Each row typically shows spend, chats, thin openers, qualified leads, sales, revenue, and ROAS for that ad.

Investigate before pausing. Check ad source, sale confirmations, spend coverage and sample size when sales are missing. Then review the offer and conversations.

Choose a bounded budget test. Use recorded outcomes, actual costs and your sales cycle; there is no universal percentage increase that is safe for every shop.

Compare placements indirectly — if one ad name maps to Reels-only and another to Feed, the table shows which creative story converts without guessing from Meta placement tabs alone.

Thumbnail and status help you match rows to live creatives in Ads Manager.

Timi ROAS vs Ads Manager: when numbers differ

Both can be correct at once:

Attribution scope. Timi ROAS uses sales recorded in Timi from CTWA chats. Ads Manager Purchase uses events on your dataset. If your team marks sold late, Timi and Meta lag differently.

Organic till. M-Pesa from bio link buyers inflates your till but never appears in Timi ad ROAS — expected.

Event naming. Renamed events in Settings still map to milestones; Ads Manager columns must match your preset — see track leads in Ads Manager.

Date windows. Align period picker in Timi with Ads Manager date range before arguing with your media buyer.

Use Timi for recorded outcomes (which ad chats have confirmed sales?). Use Ads Manager for campaign delivery and credited conversions. Cross-check one known sale weekly.

A 15-minute weekly review

Every Friday, same order:

  1. Open Timi Ads — note ROAS, cost / qualified, qualified rate
  2. Scan funnel — biggest drop-off step
  3. Choose one follow-up action after checking data completeness and margin
  4. Open Ads Manager with your saved column preset — confirm Purchase trend matches Timi sales direction
  5. Fix one operational leak — mark sold habit, delivery fee in shop context, or creative promise

Log one sentence for your team: "Reconciled ad-chat sales; checked missing spend; next test makes delivery pricing clearer."

Check the denominator and sales coverage

Start with the selected dates and connected ad account. Account spend can include campaigns or ads that do not have matched WhatsApp outcomes. Missing spend access and unmatched attribution can both distort the comparison. Inspect the per-ad rows before treating a summary ratio as a full-account verdict.

Then check recorded sales: did the team confirm all genuine ad-chat payments and record actual values? Missing confirmations can understate revenue. Organic receipts belong in the shop's broader finance review, not in an invented ad-source record.

Use ROAS with margin. Product costs, fulfilment, returns and other expenses still matter; a ratio above 1× does not establish profit. Seller-confirmed revenue is associated with tracked chats, not a controlled measurement of revenue caused by Timi.

For eligible product sellers already running Meta ads to WhatsApp, the ads overview and pricing explain the next step. Use Connect WhatsApp below. A website is optional and your team can handle replies manually.

Common mistakes

  • Judging ROAS before Meta connect — spend column empty until OAuth completes
  • Optimising on cost / chat alone — ignores thin Hi inflation
  • Expecting ROAS to include organic bio sales — CTWA only
  • Scaling budget when Purchase events flat — qualified without Purchase discipline misleads Meta
  • Ignoring unmatched ad spend — verify CTWA destination, not wa.me links
  • Comparing 7d Timi to 30d Ads Manager — align periods

Read the WhatsApp ads pillar guide for campaign structure and Audience Autopilot context.

FAQ

Where is the Ads page? Seller navigation → Ads (same account as Feed and Settings).

Do I still need Ads Manager? Yes. Timi does not publish or edit campaigns.

What if ROAS shows "—"? Check connection readiness and whether usable spend exists for the selected period. An unavailable ratio is not interchangeable with zero revenue; inspect spend and recorded revenue separately.

Can I export this data? Use Ads Manager for platform exports; Timi is for in-product weekly review. Internal till sheets remain separate.

Does Timi show Instagram vs Facebook split? Per-ad rows reflect Meta ad names; placement detail stays in Ads Manager.

How often does data refresh? Open the page for current period totals; trends chart by day or week depending on range.

How to read ROAS on Timi's Ads dashboard (WhatsApp CTWA, Kenya) | Timi