Why Timi doesn't send every WhatsApp ad chat to Meta (qualified leads vs thin Hi)

You boost a Reel for KES 12,000. WhatsApp shows 198 new chats by Sunday. Ads Manager celebrates conversations. Your qualified rate on Timi Ads is 28% — 142 chats were a lone "Hi" or empty tap-through. Meta's native conversation metric looks healthy; cost per qualified lead tells the real story. Sending every opener to Meta as a conversion would train the algorithm on curiosity clicks — people who wanted to see if you exist, not buy your KES 4,500 bundle.

This guide explains qualified leads vs thin openers — what you see in Timi, what reaches Meta, and what you can change without touching Ads Manager daily. For Purchase after qualification see when Timi sends Purchase. For attribution basics see how CTWA tracking works.

The problem with optimising on raw chat volume

Click-to-WhatsApp ads are cheap to start — KES 500/day gets conversations fast. Conversations feel like success until you reconcile the till. Many chats never ask for a product, price, or delivery pin. They opened WhatsApp because the creative was pretty or the CTA was vague.

If every chat counted equally toward Meta optimisation, the platform would hunt for more tap-and-ghost behaviour — low intent, low pay rate. That burns budget during weekend drops when three competitors run similar promotions.

Better signal: did the buyer engage beyond a bare greeting? Timi separates thin openers from qualified ad chats on your Ads dashboard and holds back low-intent openers from Meta conversion reporting until real interest shows.

What you see in Timi: thin openers vs qualified leads

Open Ads in your seller navigation after Meta is connected. You will see:

• Ad chats — total Click-to-WhatsApp conversations in the period
• Qualified rate — share that moved past thin openers
• Thin Hi count — openers that stayed at greeting-level (shown alongside qualified leads in the KPI row)
• Cost per qualified — spend divided by engaged ad leads, not raw chat count

In Feed, paid chats from CTWA show ad attribution labels. A thread can sit in Feed as an ad chat while Timi waits for substantive interest before sending qualified-lead events to Meta.

Thin openers are not failures — some convert on message three when Timi answers catalog questions. They simply should not pollute Meta's optimisation signal on message one.

What Timi sends to Meta (and what it holds back)

For Click-to-WhatsApp ad chats with conversion tracking on, Timi reports milestones as buyers progress — see connect Meta Ads for the default event ladder (Lead submitted, Qualified lead, Checkout started, Purchase).

Bare "Hi" openers are not sent to Meta as qualified conversions. Timi waits until the buyer shows real engagement — a product ask, price question, delivery pin, or similar — before qualified-lead events flow. That keeps Ads Manager focused on interest, not curiosity.

When a buyer pays, Purchase fires only if you complete the payment loop — see when Timi sends Purchase.

Organic bio and Status traffic is separate: those chats convert in Feed but do not carry campaign referral for ad optimisation.

What you can do: creative and shop context

You control more of qualified rate than any dashboard setting:

Ask a specific question in the ad. "Message us for Size 8 stock and CBD delivery fee" beats "Chat with us on WhatsApp." Specific CTAs pre-qualify before the first reply.

Match creative to shop context. If the Reel shows KES 3,500 incl. delivery, Timi's first reply must quote KES 3,500 — not a stale KES 4,000 from last month's catalog. Mismatch creates ghosting after message two.

Hand off on payment signals. When a buyer asks for till or sends a pin, take over — see how to spot serious buyers. Timi handles catalog noise; you close payers.

One offer per ad set. Mixed catalog ads attract browsers comparing ten SKUs. Split collections so qualified rate reflects intent for one product line.

Signal health in Settings

Open Settings → Ad conversion tracking. The Signal health panel shows events Timi sent to Meta in the last seven days — qualified leads, checkouts, purchases.

If events were skipped, the panel explains in plain language: organic chats and bare Hi openers are not sent. That is expected behaviour — not a fault code you need to decode.

Use Send test event after connect; use Signal health weekly alongside Ads Manager review.

Meta conversations vs Timi qualified rate

Use Meta for placement and spend delivery. Use Timi for whether those chats were worth the KES.

Common mistakes

• Optimising forever on conversation objective — switch toward Purchase or qualified events once CAPI is live
• Blaming CAPI when creative is vague — 70% thin Hi is often an ad copy problem
• Expecting every Feed ad chat to appear in Events Manager immediately — bare openers are held until engagement
• Comparing qualified rate across different offers — a KES 800 impulse item qualifies differently than custom furniture
• Ignoring thin Hi trend after a creative change — spike means the new Reel attracts browsers

Read the WhatsApp ads pillar guide for first-reply playbook and campaign structure.

FAQ

Does Timi still reply to thin Hi openers? Yes. Auto-reply runs; Meta reporting waits for engagement.

Can I force every chat to Meta manually? No — and you should not upload spreadsheets to override. Fix creative and qualification instead.

What counts as qualified? Product, price, delivery, or payment interest beyond a lone greeting — Timi applies consistent rules so your team sees the same labels in Feed and Ads.

Will qualified rate improve automatically over time? Meta may find better audiences if you optimise toward qualified or Purchase events — but stale shop context or vague ads cap improvement.

Does Instagram Reels behave differently from Feed? Destination matters (CTWA), not placement. Weak creative on Reels still produces thin openers.

Should I pause ads when qualified rate drops below 20%? Review creative and shop context first. Pause if spend is high and Purchase is zero for seven days — see track leads in Ads Manager.