Meta Conversions API, without the engineering project.

Send every enquiry, campus-visit booking, application and enrolment to Meta from the server, with hashed contact data that lifts match quality and event IDs that stop double counting.

What changes when events come from the server.

Meta’s delivery system learns from every lead it can match to a person. Signals gets more of them there, and tells Meta which ones became students.

Leads the pixel missed

Form submissions are read on your own pages and confirmed from your CRM, so they reach Meta even when the browser blocked the pixel or the student filled the form inside Instagram’s browser.

Higher event match quality

Up to nine hashed customer fields, plus click and browser IDs, attached to every event so Meta can match it to an account.

Students, not form fills

Counselled, applied and enrolled stages follow the lead from your CRM, so Meta learns from students who join, not from junk enquiries.

Exactly what Signals sends to Meta.

Every field is normalised before hashing, the way Meta specifies, so nothing fails to match because of a capital letter or a missing country code.

{
"event_name": "SubmitApplication",
"event_time": 1761484931,
"event_id": "app_A2213",
"action_source": "website",
"user_data": {
"em": ["a3f1…9c2e"], // sha256
"ph": ["7d40…b81a"], // sha256
"fn": "e2b9…", "ln": "51ac…",
"zp": "0f6d…", "country": "79ad…",
"external_id": "c8e1…",
"fbc": "fb.1.1761…IwAR2x",
"fbp": "fb.1.1758…8812",
"client_ip_address": "203.0.113.24",
"client_user_agent": "Mozilla/5.0 …"
},
"custom_data": {
"currency": "INR", "value": 1500.00,
"order_id": "A-2213"
}
}
Customer field
Key
Sent as
Email
em
SHA-256
Phone, with 91 code
ph
SHA-256
First and last name
fn, ln
SHA-256
City, state, pincode
ct, st, zp
SHA-256
Country (in)
country
SHA-256
Lead ID
external_id
SHA-256
Click ID
fbc
As captured
Browser ID
fbp
As captured
IP address
client_ip_address
As captured
User agent
client_user_agent
As captured

Your admissions stages, in Meta’s language.

Enquiries, campus visits and applications map to Meta’s standard events. Enrolment goes as a custom event with the fee as its value.

Course page viewed
Tracked pages
ViewContent
On
Enquiry submitted
Enquiry form
Lead
On
Campus visit booked
LeadSquared
Schedule
On
Application submitted
Application portal
SubmitApplication
On
Seat fee paid
Razorpay
Enrolled (custom)
On
Duplicate enquiry
Enquiry form
Not sent
Held
Not interested
LeadSquared
Not sent
Held

Set up in four steps.

Most teams send their first test event within 20 minutes of signing in.

Step 1

Connect Meta

Sign in with Facebook and choose the business, ad account and dataset.

Step 2

Connect forms and CRM

Your tracked course pages supply enquiries; LeadSquared, Zoho or Salesforce supply the stages after.

Step 3

Review the mapping

Confirm which events to send, their values and how they deduplicate with the pixel.

Step 4

Test, then go live

Send test events to Events Manager, check match quality, then switch on.

Meta CAPI questions.

Will server events double count with my pixel?

No. Signals gives each event the same event ID the pixel uses, usually the lead ID, and Meta keeps one copy. Deduplication rates are shown per event in the dashboard.

We already have the Meta pixel on our forms. Do we need this?

Keep it. The pixel misses a large share of leads, especially from Instagram’s in-app browser. Signals sends the same leads from the server with a shared event ID, so Meta counts each once and matches more of them.

Can Meta optimise for enrolments instead of leads?

Yes. Enrolments from your CRM are sent as a custom event with the fee as value. Once there are enough of them, you can optimise campaigns for that event or use it to build lookalike audiences.

How quickly do events reach Meta?

Within seconds of the form submission or stage change. Events that fail are retried automatically for up to seven days, inside Meta’s attribution window.

Can we send counselling and campus visits?

Yes. Any CRM stage can be mapped, for example Schedule for a booked campus visit and SubmitApplication for a completed application, each with its own value.

What about consent and the DPDP Act?

Signals reads your consent platform and only includes customer data a visitor allowed, in line with India’s DPDP Act. Events without marketing consent can be skipped or sent without personal data, depending on your settings.

See your match quality before and after.

We’ll connect your dataset on a 30-minute call and send live test events together.

Book a demoGoogle Enhanced Conversions