Teach Meta and Google what an enrolled student looks like
Enquiries are cheap and enrolments are not. Feed counselling, application and enrolment outcomes back so ad platforms find more students who join.
Why enquiries are a weak admissions signal
Enquiries look identical
A curious browser and a serious applicant produce the same form fill.
Admissions happen off-platform
Counselling, applications and fee payment live in the CRM, invisible to the ad account.
Seasonal, long cycles
By the time a seat is confirmed, the campaign has already optimised on the wrong signal.
The four admissions milestones worth reporting
- 1
Counselled
A counsellor spoke to the prospect and confirmed interest.
- 2
Applied
The application form was submitted, a strong sign of intent.
- 3
Admitted
The application was accepted.
- 4
Enrolled
Fees paid and the seat confirmed, the outcome that earns revenue.
Built for long admission cycles
Stage-gated events
Only counselled, applied and enrolled stages are mapped. A raw enquiry is never treated as a win.
Course-level learning
Each programme or intake stays separate so campaigns learn from their own enrolments.
Counsellor outcomes
Counselling sessions and follow-ups logged in the CRM feed the signal automatically.
Season-tolerant delivery
An enrolment confirmed weeks after the click is still attributed to the campaign that started it.
Which admission stages get reported
Illustrative mapping. Your stages and event names are agreed during setup.
| CRM stage | Approved to send? | Reported as |
|---|---|---|
| Enquiry received | No | — |
| Counselled | Optional | Qualified lead |
| Applied | Yes | Application started |
| Admitted | Yes | Application approved |
| Enrolled | Yes | Purchase, with fee value |
Enquiries versus enrolled students
Without RevenueSignal
- Platform optimises for the cheapest enquiry
- Counselling and applications stay hidden in the CRM
- Budget follows volume, not enrolments
With RevenueSignal
- Platform sees which prospects enrol
- Applications and enrolments feed the signal
- Budget can follow enrolled students
What we need from your team
Your admission stages and what each one means
Access to the CRM or student-system export
Meta and Google ad account access
Programme and intake structure
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