Analytics · ScoutX → Meta
ScoutX and the Meta Conversions API
Browser-side pixels miss conversions to ad blockers and tracking restrictions. The Conversions API reports the lead from the server instead — which is also the only place customer data can be handled safely.
How it works
- Lead events are sent from the server, so the raw email and phone number never enter the browser. Only SHA-256 hashes leave the server, which is what makes advanced matching usable without putting customer data in the data layer.
- Three gates all have to pass before an event is sent: the dealer has switched it on, a pixel and access token are configured, and the visitor has granted marketing consent without sending an opt-out signal. If consent cannot be confirmed, nothing is sent — it fails closed, not open.
- The server event and the browser event carry the same lead identifier, so Meta deduplicates them into one enriched conversion rather than counting the lead twice.
- It is off by default. A measurement feature that sends customer data should be a decision somebody made, not a default somebody inherited.
Other integrations
Lightspeed → ScoutX
Lightspeed DMS
Automatic unit sync from Lightspeed across every franchise you carry.
Motility → ScoutX
Motility
Unit sync from Motility, in either its XML or CSV export.
Your DMS → ScoutX
SFTP inventory feed
Any DMS that can drop a scheduled file — XML, CSV or pipe-delimited.
Questions
Meta Conversions API questions
Does this send customer data to Meta?+
It sends irreversible hashes of the email and phone, never the values themselves, and only when the visitor has granted marketing consent.
Will our conversions be double-counted?+
No. Both events carry the same lead identifier and Meta merges them.
Is it on by default?+
No. It is off until you enable it, deliberately.