What server-side sending solves
- Blocked pixels: conversions go from TSO's server to the platform. Whether the pixel loaded in the browser doesn't matter.
- Sales and payments: deals from the CRM and payments from Stripe, Digistore24 or CopeCart don't happen in the browser at all and always arrive.
- Double counting: pixel and server send the same event ID, and the platform merges both.
- Matching without platform cookies: hashed email addresses, phone numbers and click IDs help the platform find the user.
What it doesn't solve
To be honest, gaps remain:
- If an ad blocker blocks the TSO script, that visitor's page views and website forms are missing. Leads from funnel tools and deals that arrive by webhook still count.
- Safari keeps browser cookies for seven days at most. After that, TSO recognises returning visitors only by their contact data.
- In private tabs and in links from Mail and Messages, Safari removes known click IDs. The source then comes from the UTM parameters.
- TSO doesn't measure view-through conversions.
TSO uses a first-party ID without third-party cookies and shows conversions it can't attribute to a campaign as their own row. So you see how big the gap is instead of overlooking it.