The SDK Runtime sounds like a major step in the right direction (separating advertising SDKs into its own process with distinct permissions, separate from a hosting app and with no app-to-app communication).
Also the ability to custom audiences from apps (in the fledge article) and control topics both sound good.
These things dont appear to have any current plans to be required, but in the future I hope they do.
If you’re familiar with the mobile advertising landscape, on device identifiers are either OS-provided and deterministic or are computed through a “signature” or “fingerprint” based on unique signals the app has access to.
This move is one where either of those will be removed/made universal so there is no way to identify uniquely, one user from another when they perform actions outside your app or for many scenarios within it as well (such as clicking on an ad that takes them to the app)
Lots of advertising companies (predominantly Facebook) have made an industry standard out of selling ads based on THEIR interpretations of users actions across apps and time leading to a conversion. For example, a 7day “click through conversion” means , if your ad is shown to a user through Facebook on any of their apps or partner apps with the Facebook ad network sdk, and a subsequent conversion occurs in the next 7 day window, that user is counted as 100% credit to Facebook.
Is this logical? Nope.
Advertisers pay for the nice looking metrics they can stick in a PowerPoint and be done with it.
Now, Facebook can’t use their “eye of Sauron” to put out numbers such as these and need to compete with companies such as google and Pinterest and Reddit and snap for where users are looking for things, not just “snipe” the attribution at the last minute when they know the user is about to pull the trigger and buy.
Looks like they are trying to create a distinct set of APIs for third-party advertising (and I think everything else) SDK libraries. Those libraries are submitted to Google independently from the app. The apps now have to declare they are using library X version Y and Google will deploy that library to the end user's device when the app installs.
jcranberry|4 years ago
https://developer.android.com/design-for-safety/ads/sdk-runt...
https://developer.android.com/design-for-safety/ads/topics
https://developer.android.com/design-for-safety/ads/fledge
https://developer.android.com/design-for-safety/ads/attribut...
The SDK Runtime sounds like a major step in the right direction (separating advertising SDKs into its own process with distinct permissions, separate from a hosting app and with no app-to-app communication).
Also the ability to custom audiences from apps (in the fledge article) and control topics both sound good.
These things dont appear to have any current plans to be required, but in the future I hope they do.
DisjointedHunt|4 years ago
This move is one where either of those will be removed/made universal so there is no way to identify uniquely, one user from another when they perform actions outside your app or for many scenarios within it as well (such as clicking on an ad that takes them to the app)
Lots of advertising companies (predominantly Facebook) have made an industry standard out of selling ads based on THEIR interpretations of users actions across apps and time leading to a conversion. For example, a 7day “click through conversion” means , if your ad is shown to a user through Facebook on any of their apps or partner apps with the Facebook ad network sdk, and a subsequent conversion occurs in the next 7 day window, that user is counted as 100% credit to Facebook.
Is this logical? Nope.
Advertisers pay for the nice looking metrics they can stick in a PowerPoint and be done with it.
Now, Facebook can’t use their “eye of Sauron” to put out numbers such as these and need to compete with companies such as google and Pinterest and Reddit and snap for where users are looking for things, not just “snipe” the attribution at the last minute when they know the user is about to pull the trigger and buy.
Jwarder|4 years ago
hericium|4 years ago