Skip to content
Kuraib Ali
Selected work

Relegance Properties

Strong project. Broken measurement. Cost per lead doubled in eight months.

Sector
Real estate brokerage · Dubai off-plan
Timeframe
47 days
Engagement
Tracking rebuild + campaign restructure, no budget increase

The situation

A Dubai real estate brokerage was marketing an off-plan project on Meta Ads and had been for eight months.

Leads were coming in, but cost per lead had climbed from AED 90 at launch to AED 184, and fewer than 6% of Meta leads were booking a viewing. The brokerage assumed audience saturation or creative fatigue. A Meta Events Manager audit put signal quality at 4.8 out of 10: the pixel fired duplicate lead events on some forms and none on others, and the server-side connection had no deduplication key, so the algorithm was optimising toward counted-twice leads.

The move

  1. 01

    I rebuilt the tracking layer before touching a single campaign: a GTM server container, the CAPI deduplication key set correctly, and signal quality taken from 4.8 to 9.1 in ten days. The algorithm received accurate lead data for the first time.

  2. 02

    I separated awareness and conversion objectives that had been sharing one campaign, rebuilt prospecting around verified buyer-intent signals — GCC residents with investment interest, Dubai property search behaviour, lookalikes from the top fifth of CRM leads by deal progression — and rebuilt the retargeting pool from qualified form engagements only.

  3. 03

    I introduced creative rotation with a minimum of six live creatives, frequency caps of 2.5 per week in prospecting, and bilingual English–Arabic copy across every segment. Then I let the algorithm exit its learning phase on clean data before judging anything.

What changed

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.

Before and after states for the Relegance Properties engagement.
BeforeAfter
Conversion signalDuplicate and missing lead events, no dedup keyServer-side CAPI, deduplicated, 9.1/10 signal quality
Campaign structureAwareness and conversion in one campaignSeparate objectives, separate learning
Retargeting poolAll website visitorsQualified form engagements only
CreativeThree ads for eleven weeks, frequency above 4.2Six or more live, capped at 2.5 per 7 days

Scroll sideways to compare →

What shipped

  • GTM server container + CAPI with deduplication
  • Signal quality 4.8 → 9.1 in Meta Events Manager
  • Campaign architecture: prospecting and retargeting separated
  • Intent-based audiences from CRM deal progression
  • Six-creative rotation, EN/AR, frequency-capped
  • Baseline and 47-day measurement against platform data

The scorecard

What this engagement was held to, and what the platform reported. Each figure names the source it was pulled from.

Cost per lead
AED 184 → AED 72 (−61%)
Total spend ÷ platform-reported lead events, Meta Ads Manager, 47-day period
Signal quality
4.8 → 9.1 / 10
Meta Events Manager event match quality score
Lead volume
+180%
Platform-reported lead events, same budget
Pipeline generated
AED 2.1M+
CRM deal value attributed to the period

✓ 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.

Full write-upMeta Ads Real Estate Dubai: AED 184 → AED 72 CPL in 47 Days | Case Study
Quick Answer

Reducing Meta Ads CPL without increasing budget usually comes down to signal quality, not creative or targeting, this case shows a Dubai real estate campaign where fixing broken conversion tracking, not changing the ads, cut CPL from AED 184 to AED 72 in 47 days.

01. The Situation

Strong product. Broken measurement. Rising CPL.

A Dubai off-plan developer had been running Meta Ads for eight months. Campaigns were generating leads but CPL had climbed from AED 90 at launch to AED 184 by the time the engagement started. The sales team was processing leads but booking rates from Meta were below 6%. The developer assumed the problem was audience saturation or creative fatigue.

The actual problem was infrastructure. A Meta Events Manager audit revealed signal quality of 4.8 out of 10. The pixel was firing duplicate lead events on some forms and missing events entirely on others. Server-side CAPI had been partially configured but the deduplication key was absent, meaning Meta was counting the same lead twice on a significant portion of conversions. The algorithm was optimising toward duplicated signals.

02. What Was Found

Four structural problems identified in the first audit.

  1. 01

    Signal quality at 4.8/10 in Meta Events Manager, duplicate lead events and missing deduplication key on CAPI implementation

  2. 02

    Audience structure conflating awareness and conversion objectives in the same campaign, preventing the algorithm from calibrating correctly

  3. 03

    Creative rotation absent, same three ad creatives running for 11 weeks at frequency above 4.2 in the target segments

  4. 04

    Retargeting pool built on all website visitors rather than qualified intent signals, diluting the pool with low-intent traffic

03. What Was Done

Tracking first. Campaigns second.

Before touching campaigns, the tracking layer was rebuilt. GTM Server Container configured. CAPI deduplication key set correctly. Signal quality brought from 4.8 to 9.1 over 10 days. The algorithm stopped receiving duplicate signals and began receiving accurate lead data for the first time.

Campaign architecture was restructured with awareness and conversion objectives separated. Prospecting audiences rebuilt around verified buyer intent signals: GCC residents with investment interest, Dubai property search behaviour, and lookalikes from the top 20% of CRM leads by deal progression. Retargeting pool rebuilt from qualified form engagements only.

Creative rotation introduced with a minimum of six active creatives per campaign. Frequency caps enforced at 2.5 per 7-day window in prospecting. Bilingual EN/AR ad copy across all segments.

Days 1–10
Tracking rebuild
GTM Server Container, CAPI deduplication, signal quality 4.8 → 9.1
Days 11–20
Campaign restructure
Audience architecture, prospecting/retargeting separation, creative rotation
Days 21–47
Algorithm recalibration
Learning phase exit, CPL decline visible from Day 28, AED 72 confirmed at Day 47
04. The Result

AED 184 to AED 72. Verified from platform data.

CPL dropped from AED 184 to AED 72 over 47 days from the date tracking was fixed. No budget increase. The improvement was attributable to two factors: the algorithm receiving accurate signal and therefore optimising toward real conversions, and audience restructuring eliminating low-intent traffic from the conversion pool.

AED 72Final CPL
−61%CPL reduction
9.1/10Signal quality
47 daysTime to result
✓ All figures sourced from Meta Ads Manager platform reporting for the stated 47-day period. CPL calculated as total spend divided by platform-reported lead event count.
← All Case Studies E-Commerce ROAS → Healthcare Bookings → KSA Investor Leads → Google Ads Clinic →
What This Demonstrates

Tracking quality is the foundation of campaign performance

A 61% CPL reduction with no budget increase is not a campaign optimisation story. It is a measurement story. The algorithm cannot improve on data it does not receive accurately. This engagement demonstrates the CAPI-first methodology applied to a real account with real budget: fix the signal layer, allow the algorithm to exit the learning phase, then measure the output against a clean baseline. Every engagement follows this sequence, regardless of how urgent the campaign brief appears.

See Meta & Google Ads Service →
Frequently Asked

How was CPL reduced without increasing ad budget?

The drop from AED 184 to AED 72 came from fixing the tracking layer, not the campaign. A GTM Server Container was configured and the CAPI deduplication key corrected, bringing Meta’s signal quality score from 4.8 to 9.1 over 10 days. With accurate signal, Meta’s algorithm optimised toward genuinely qualified leads instead of duplicate or misattributed events.

Why fix tracking before touching the ad campaigns themselves?

If the platform is receiving inaccurate conversion signals, campaign changes are optimising against the wrong data. This engagement followed a measurement-first sequence: rebuild the tracking layer first, then let the algorithm exit the learning phase on clean data, then measure results against a verified baseline.

How long did it take to see results?

CPL dropped from AED 184 to AED 72 over 47 days, measured from the date tracking was corrected, not from the campaign’s original launch date. This distinction matters because the improvement is attributable to the tracking fix, not a gradual seasonal trend.

By Kuraib Ali, Search & Growth Consultant, Dubai · Meta Blueprint · Google Ads Certified  ·  Last updated: August 3, 2026

Next project

UAE skincare brand (confidential)

Reasonable CPM. Reasonable CTR. Return on ad spend stuck below 2× for eleven months.

Working on something with a similar shape?

admin@kuraib.site