Is this based on your knowledge or experience in the ad industry? Or just your intuition on how it should work? What I see in OP is UberEats loading a tracking pixel directly from TikTok servers, where the “pixel” is actually a full events.js analytics script that could send user data straight to TikTok.
On the other hand, you always have a choice to not use UberEats(or most others) and order by phone/walk-in and save your resources.
And it would be a bit of exaggeration to say targeting doesn’t work - It’s obviously far from perfect but it generates billions everyday for a reason.
I don't want to be targetted.
> So it’s just good karma to let them run ...
No. It's my machine, not theirs, they don't get to use it to track me. Not one single cycle. It certainly isn't "good karma" to allow advertisers free reign like that, it's letting the fox loose in the hen-house.
>> Don't open their website
Sure, or just don't allow them to load these things.
Honestly I'm moving in the direction of not visiting. Instead of a useless do-not-track header, I'd much rather send a "will-not-render" header. I'd be quite happy to tell your server that under no circumstances will my browser be participating in tracking or even rendering your ads. If you'd rather not serve me the page at that point then cool, lets go our separate ways.
I imagine a company like uber eats, who I am actually trying to pay when I visit their site, might still like to serve me the page. Ad-supported content less so.
Really? I thought Apple's newly-implemented ATT was exactly what made attribution impossible for things like app store purchases.
This is the specific thing I'm referring to.
> How does including interest-based tracking for a product make a commitment to privacy from unrelated companies' tracking "smoke and mirrors"? There's a difference between the privacy I expect from a direct service provider and from various random agents seeking to build a profile on me.