Skip to content
Use cases

Tracking despite ad blockers and iOS

What server-side sending, first-party IDs and deduplication do against ad blockers and Safari's restrictions, and what they don't solve.

The problem

Ad blockers block pixels, Safari limits cookies, and in some situations click IDs disappear from links. The ad platforms see fewer conversions than actually happen and optimise on a fraction of the data.

How to do it

  1. Set up the conversion APICreate a destination for each ad platform. TSO sends conversions from the server, whether or not the pixel loaded in the browser.
  2. Load pixels through TSOWhen the TSO script loads the pixels, browser and server events carry the same event ID. The platform counts every event once.
  3. Capture contact dataForms are detected automatically. Email and phone connect visits on different devices and go to the platforms hashed.
  4. Connect server-side sourcesPayments from Stripe, Digistore24 and CopeCart and deals from your CRM come in by webhook or API, with no browser involved.
Destinations
  • Meta dataset
    Conversions API · Lead, deal won, purchase
    active
  • Google Ads
    Import from clicks · enhanced conversions
    active
  • LinkedIn
    Conversions API · own token
    active
  • Microsoft Ads
    UET Conversions API
    Test mode
DeliveryDeal won · €4,800
  1. Ad click · Meta
    Oct 12 · Sales call · Lookalike
  2. Lead · form detected
    Oct 12 · email and phone
  3. Deal won · webhook from the CRM
    Nov 3 · €4,800
  4. Sent to platforms
    Meta ✓Google Ads ✓LinkedIn ✓

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.

The result

Conversions the pixel misses in the browser still arrive through the conversion API, and deals from sales and payment providers arrive without a browser at all. You know where the remaining gaps are.

Common mistakes

Works with

  • Meta
  • Google Ads
  • TikTok
  • Stripe
  • Webhook

Frequently asked questions

Does TSO get around ad blockers?

No. Conversions go from the server to the platforms, which helps when their pixel is blocked. An ad blocker can block the TSO script too. A custom tracking domain is in preparation but not yet available.

What changes because of Safari?

Safari keeps cookies set by a script in the browser for seven days at most. People who come back later are recognised by email or phone once they enter it.

Does this help against iOS App Tracking Transparency?

ATT concerns tracking in apps. For conversions on your website, it helps that TSO sends hashed contact data and click IDs from the server instead of relying on the platforms' cookies.

Does TSO measure view-through conversions?

No, only clicks. Conversions after merely seeing an ad can only be estimated by the platform itself.

More use cases

Set it up in your project.

Hosted in Germany · Built in Austria