Optimise for serious buyers, not form fills
Property enquiries are cheap and bookings are not. Feed qualification, site visit and booking outcomes back so ad platforms find more buyers who close.
Why enquiries are a weak buyer signal
Form fills look identical
A casual browser, a broker and a serious buyer produce the same lead event.
Visits happen off-platform
Calls, WhatsApp, site visits and bookings live in the CRM, invisible to the ad account.
Long sales cycles
By the time a unit is booked, the campaign has already optimised on the wrong signal.
The four buying milestones worth reporting
- 1
Qualified buyer
Budget, timeline and intent were confirmed on a call.
- 2
Site visit
The buyer visited the project, a strong sign of intent.
- 3
Booking
A unit was booked with a token amount.
- 4
Revenue
The sale value recorded, the outcome that earns revenue.
Built for high-value property journeys
Stage-gated events
Only qualified, site-visit and booking stages are mapped. A raw enquiry is never treated as a win.
Project-level learning
Each project and location stays separate so campaigns learn from their own bookings.
Broker and walk-in outcomes
Visits and bookings logged by your sales team feed the signal, wherever the lead first came from.
Delay-tolerant delivery
A booking that lands weeks after the click is still attributed to the campaign that started it.
Which property stages get reported
Illustrative mapping. Your stages and event names are agreed during setup.
| CRM stage | Approved to send? | Reported as |
|---|---|---|
| Enquiry received | No | — |
| Qualified buyer | Optional | Qualified lead |
| Site visit done | Yes | Site visit completed |
| Booking | Yes | Booking made |
| Sale closed | Yes | Purchase, with value |
Form fills versus site visits that happen
Without RevenueSignal
- Campaigns reward cheap enquiries from browsers and brokers
- Site visits and bookings stay hidden in the CRM
- Budget follows volume, not bookings
With RevenueSignal
- Platform sees which leads reach a site visit
- Bookings flow back with their value
- Budget can follow booked units
What we need from your team
Project and location list
Site-visit and booking stages in the CRM
Meta and Google ad account access
Booking value fields
We don't fight your stack
We already have a CRM. Do we need to replace it?
No. RevenueSignal sits around your CRM. Your CRM already holds the downstream outcomes that matter; we analyse and activate the approved ones so ad platforms can learn from them.
We already send leads to Meta through the Conversions API.
That is a good start. The Conversions API is the delivery route; the open question is what you send through it. A lead event alone tells the platform very little about which leads turn into revenue.
Do you send all our CRM data to Meta or Google?
No. Only approved, eligible outcomes and permitted customer-match data are mapped, according to the configuration we agree with you.
Can you guarantee lower cost per lead or higher ROAS?
No responsible platform can. Results depend on your data, volumes and campaigns, so we set a baseline first and measure against it.
Can we start with one project?
Yes, where your data and account structure allow it. A focused pilot is often the best way to see real proof before expanding.
Give your ads a better signal to learn from
Start with a Readiness Review. We look at your data journey and tell you what is worth sending back.
Request a readiness review