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.
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.
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.
Up to nine hashed customer fields, plus click and browser IDs, attached to every event so Meta can match it to an account.
Counselled, applied and enrolled stages follow the lead from your CRM, so Meta learns from students who join, not from junk enquiries.
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.
Enquiries, campus visits and applications map to Meta’s standard events. Enrolment goes as a custom event with the fee as its value.
Most teams send their first test event within 20 minutes of signing in.
Sign in with Facebook and choose the business, ad account and dataset.
Your tracked course pages supply enquiries; LeadSquared, Zoho or Salesforce supply the stages after.
Confirm which events to send, their values and how they deduplicate with the pixel.
Send test events to Events Manager, check match quality, then switch on.
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.
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.
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.
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.
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.
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.
We’ll connect your dataset on a 30-minute call and send live test events together.