Lahore property agency (confidential)
Hundreds of clicks a week in Ads Manager. Silence in WhatsApp.
- Sector
- Real estate · Lahore, Pakistan
- Timeframe
- 3 weeks
- Engagement
- WhatsApp campaign structure: objective, destination, opener, audience
Traffic
WhatsApp URL in the destination field · finds link-tappers
Engagement
WhatsApp as the conversion · finds message-likely users
Hi, I’m interested
Hi, I’m interested in the [property]. Can you send pricing and availability?
Greeting within 30 s · then a person
A Lahore property agency ran Facebook ads that collected link clicks consistently, sometimes hundreds a week, while the WhatsApp number in the ad received a handful of messages.
Budget went up; nothing changed; the agency concluded the audience or the creative was wrong. Neither was. The campaign was set to the Traffic objective with a WhatsApp link in the URL field, so Meta was finding people who click links, not people who message businesses. The WhatsApp Business number was not connected to Business Manager, the opener was Meta’s generic default, and the interest stack was too narrow for conversation optimisation.
- 01
Infrastructure first: I connected the WhatsApp Business number to Meta Business Manager, the prerequisite for any conversation-level signal to reach the algorithm.
- 02
Then a new campaign, not an edited one — Engagement objective with WhatsApp as the conversion destination — so it learned from a clean start instead of inheriting the Traffic campaign’s audience history.
- 03
Then the opener and the audience: a specific pre-filled message naming the property and asking for pricing, a greeting reply within 30 seconds, and the interest stack removed in favour of a city-wide audience the algorithm could actually search. No creative changes.
States of the system, not metrics — these are things that either were or were not true, so they can be stated without claiming a result.
| After | ||
|---|---|---|
| Objective | Traffic, with a WhatsApp URL in the destination | Engagement, WhatsApp as the conversion |
| Signal | None — link taps only | Conversation events returned to the algorithm |
| Opener | Meta default: “Hi, I’m interested” | Property named, pricing requested, greeting in 30 s |
| Audience | Narrow interest stack | City-wide, algorithm finds message-likely users |
- WhatsApp Business number connected to Meta Business Manager
- New Engagement campaign with WhatsApp conversion destination
- Contextual pre-filled opener + 30-second greeting
- Audience widened: city and age, interest stack removed
- Seven-day learning phase left untouched
What this engagement was held to, and what the platform reported. Each figure names the source it was pulled from.
- Cost per WhatsApp conversation
- −71%
- Spend ÷ platform-reported conversations started, after the learning phase
- Creative changed
- None
- Ads edited before measuring the structural fix
- Learning phase
- 7 days
- Days with no changes after launch
- Conversation-to-sale rate
- Separate system
- Determined after the message arrives — response speed and follow-up
✓ Every figure is sourced from platform reporting — Meta Ads Manager, Meta Events Manager, Google Ads or the client’s CRM — never modelled or estimated. The full write-up, as published, follows below.
Next project
Relegance Properties
Strong project. Broken measurement. Cost per lead doubled in eight months.
Working on something with a similar shape?
admin@kuraib.site