Learn from appointments that actually happen
Enquiries are cheap and no-shows are expensive. Send back permitted, non-sensitive milestones so ad platforms find more patients who attend.
Why enquiries are a weak appointment signal
Enquiries look identical
A casual query and a patient ready to book produce the same lead event.
Appointments happen off-platform
Bookings and attendance live in the CRM or HIS, invisible to the ad account.
Sensitive data limits
Health information cannot be shared, so the signal has to use safe, non-clinical milestones.
The four appointment milestones worth reporting
- 1
Qualified enquiry
The enquiry was reached and confirmed as genuine.
- 2
Appointment booked
A slot was confirmed with the clinic.
- 3
Attended
The patient visited, a non-sensitive attendance milestone.
- 4
Follow-up booked
A repeat visit signals a lasting relationship.
Built with privacy in mind
Non-sensitive milestones only
Only permitted, non-clinical stages such as qualified enquiry, appointment and attendance are mapped.
No medical details shared
Diagnoses, treatments and health information are never sent to ad platforms.
Consent-aware matching
Customer-match data is shared only where your consent and platform policies allow it.
Clinic-level learning
Locations and service lines stay separate so each campaign learns from its own outcomes.
Which appointment stages get reported
Illustrative mapping. Only permitted, non-sensitive milestones are sent.
| CRM stage | Approved to send? | Reported as |
|---|---|---|
| Enquiry received | No | — |
| Qualified enquiry | Optional | Qualified lead |
| Appointment booked | Yes | Appointment scheduled |
| Attended | Yes | Visit completed |
| Medical details | Never | Not shared |
Enquiries versus attended appointments
Without RevenueSignal
- Platform optimises for the cheapest enquiry
- Bookings and attendance stay hidden in the CRM
- Budget follows volume, not visits
With RevenueSignal
- Platform sees which enquiries become visits
- Only non-sensitive milestones feed the signal
- Budget can follow attended appointments
What we need from your team
Your appointment stages and what each one means
Access to the CRM or booking system export
Meta and Google ad account access
Your consent and data-sharing rules
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