Browsers block the pixel
iOS limits, ad blockers and in-app browsers stop lead events from firing or being matched to the click.
When the outcome doesn’t reach the platform, the algorithm optimises for cheap form fills instead of students who join. Three things cause most of the gap.
iOS limits, ad blockers and in-app browsers stop lead events from firing or being matched to the click.
Counselling, applications and seat-fee payments happen in your CRM, weeks after the click, where no pixel can see them.
A fake number from a contest form and a student who pays the seat fee send the same signal, so bidding can’t tell them apart.
Connect each ad account once. Signals formats, hashes and delivers events in the shape each platform expects.
Leads, campus-visit bookings, applications and enrolments from the server, matched with hashed contact data and deduplicated against the pixel.
em · ph · fbc · fbp · event_idAdds hashed email and phone to the enquiries your Google tag already records, so more of them match a Google account.
sha256 email · phone · addressSends counselled, applied and enrolled students from your CRM, matched by GCLID, GBRAID or WBRAID, with the fee as value.
gclid · gbraid · wbraid · valueMatches CRM outcomes with hashed form data when no click ID was captured.
sha256 email · phoneLead and application events from the server with the Snap click ID and hashed contact details, for undergraduate campaigns.
sc_click_id · em · ph · event_idLead and enrolment events for MBA, executive and working-professional programmes, matched on hashed email.
li_fat_id · sha256 emailChoose which stage counts and what it’s worth. The platform then bids harder for people who look like your enrolled students.
Applications are sent with the fee paid, so the platform learns from students serious enough to apply.
Sending events is the easy part. Getting them matched, counted once and tied to real admissions outcomes is what moves results.
Hashed email, phone, address and click IDs on every event so more conversions match a real person.
Shared event IDs deduplicate server events against browser pixels automatically.
Send the application or first-year fee instead of a flat lead count.
Counselled, applied and enrolled flow back weeks after the click, inside the attribution window.
Duplicate, fake and unqualified enquiries are held back so campaigns stop learning from them.
Built around India’s DPDP Act and Google consent mode, sending only what each visitor allowed.
No tag manager work and no developer tickets. If you already run VelocitAI Attribution, your sources are connected.
Your enquiry forms, LeadSquared, Zoho CRM, Salesforce, HubSpot or a webhook.
Sign in to Meta and Google and choose the pixel and conversion actions.
Pick which lead stages to send, such as counselled, applied and enrolled, and what each is worth.
Match quality, delivery and dedup rates per destination, with alerts when anything drops.
Yes, keep it running. Signals sends the same events from the server with a shared event ID, and the platform keeps whichever copy arrives with the best data and drops the duplicate.
Yes. Send only the stages you trust, such as counselled or applied, and leave raw form fills out. Duplicate enquiries from the same student are sent once.
Email, phone (with +91), name and pincode are normalised and hashed with SHA-256 before they leave Signals. Click IDs, IP and user agent are sent as the platforms require. Only data your visitors consented to is included, in line with India’s DPDP Act.
Yes. Connect your CRM and choose the stages to send, such as counselled, applied or enrolled. Signals matches each one back to the original click ID and uploads it when the stage changes.
It replaces the server-side part: no GTM server container, no custom endpoints and no separate CAPI setup per platform. Keep your existing browser tags if you like.
No, Signals works on its own. Teams that run both can send enrolments valued and credited by attribution.