2 ms·
Why not just scrap the IDFA and let the app save themselves a random uuid in their sqlite database then? Am I missing something?
by realusername 6y ago
Why not just scrap the IDFA and let the app save themselves a random uuid in their sqlite database then? Am I missing something?
- zepto 6y agoThe point of IDFA is to allow the user to express a system wide preference, and also to allow the identifier to persist across installs. Although the overwhelming majority of people distrust tracking, a significant minority >20% do not. Every time the discussion comes up here we see people who say they like targeted advertising. Apple wants to exclude other mechanisms and have an opt-in mechanism to support this 20%. They are one step away from making it opt-in but were delayed by political pressure from Facebook. If Ad Tracking companies improve their practices, perhaps they can persuade more people to opt-in. Apple has reached this point by slowly eliminating other sources of fingerprinting from their apis, and adding rules insisting that IDFA be the only identifier used. The only issue here is that IDFA is not yet opt-in. Otherwise, Apple is way ahead of the game. All other platforms allow some kind of fingerprinting.
- user-the-name 6y agoIt is shared across web and apps but only for one vendor. So you can track the performance of an ad campaign on getting installs of your app, for instance.
- Nextgrid 6y ago> So you can track the performance of an ad campaign on getting installs of your app, for instance. So in order for it to work you'd need to also be the developer (vendor) of the initial app which displays the advertisement for your second ad? Otherwise how would it work if let's say your ad is displayed in app from vendor A (and they get their own IDFA), now when your (vendor B) app is installed you see a different IDFA. How would you associate the two?