Triplelift is an SSP in the advertising technology space, one of many responsible for ultimately rendering ads on publisher sites through Header Bidding. In order for us to record an ad as “won” and “rendered”, we fire a number of pixels on-page, which tells our systems that we did indeed serve an ad on page, also called an impression. This is common across all SSPs in the space.
For Triplelift specifically, the most important pixel is our /notify, which follows the following structure:
Via Header Bidding (Prebid, etc):
https://tlx.3lift.com/header/notify?...
Via server-side connections:
https://tlx.3lift.com/s2s/notify?...
This pixel does not track users in any way.
With the release of Samsung Browser v17, where Smart Anti-Tracking was auto-enabled for all users, we saw a large drop in recorded impressions, despite the fact that we were in fact, still winning the impression, as the Smart Anti-Tracking feature blocks our /notify pixel.
Our team has been told that the behavior of Samsung’s Smart Anti-Tracking is meant to mimic Safari’s behavior, which it does not right now, so we are looking to get this unblocked. Below, you’ll see screenshots displaying this.
Samsung Browser, Smart Anti-Tracking Enabled:
Samsung Browser, Smart Anti-Tracking Disabled:
Safari, cross-site tracking disabled, cookies blocked:
Triplelift is an SSP in the advertising technology space, one of many responsible for ultimately rendering ads on publisher sites through Header Bidding. In order for us to record an ad as “won” and “rendered”, we fire a number of pixels on-page, which tells our systems that we did indeed serve an ad on page, also called an impression. This is common across all SSPs in the space.
For Triplelift specifically, the most important pixel is our /notify, which follows the following structure:
Via Header Bidding (Prebid, etc):
https://tlx.3lift.com/header/notify?...
Via server-side connections:
https://tlx.3lift.com/s2s/notify?...
This pixel does not track users in any way.
With the release of Samsung Browser v17, where Smart Anti-Tracking was auto-enabled for all users, we saw a large drop in recorded impressions, despite the fact that we were in fact, still winning the impression, as the Smart Anti-Tracking feature blocks our /notify pixel.
Our team has been told that the behavior of Samsung’s Smart Anti-Tracking is meant to mimic Safari’s behavior, which it does not right now, so we are looking to get this unblocked. Below, you’ll see screenshots displaying this.
Samsung Browser, Smart Anti-Tracking Enabled:
Samsung Browser, Smart Anti-Tracking Disabled:
Safari, cross-site tracking disabled, cookies blocked: