Why the algorithms need your deals
Meta, Google and the others optimize for the conversions they get back. If they only see form submissions, they look for more people who fill in forms, including those who never buy. If they learn which leads became meetings and deals, they look for more people like those.
TSO reports both: the lead on the website and the later steps from your sales process, such as sales call, deal won or payment.
The right method per platform
- Meta: Conversions API, page views server-side too. Deal created, won and lost go to Meta as CRM stages.
- Google Ads: Data Manager API for "import from clicks" actions with gclid, gbraid and wbraid, and enhanced conversions for leads with hashed contact details. Website actions are reported by the Google tag, Consent Mode included.
- TikTok: Events API with click ID, TikTok cookie and hashed contact details.
- LinkedIn: Conversions API with your own token, together with the Insight Tag if you like.
- Microsoft Ads: UET Conversions API with msclkid and UET visitor ID.
- Snapchat and ChatGPT Ads: Conversions API with click reference and hashed contact details.
One event, counted once
When the pixel loads in the browser and TSO also sends from the server, both carry the same event ID. The platform counts the event once, and conversions the pixel misses because of ad blockers or browser restrictions still arrive.
Lead IDs from lead forms
When a lead comes from a Meta Instant Form or a LinkedIn Lead Gen Form, its lead ID goes along with every later conversion of that person. So the platform can attribute the deal to the exact form.
Full control over delivery
Every delivery runs through a queue with retries. The delivery log shows per destination what was sent, what is waiting and why something wasn't delivered. You can withhold fields such as IP address or user agent per platform.