In this episode of the MDM Podcast, I unpack a very specific, very important question with my guest, Thomas Petit: Why doesn’t Google have to show the ATT prompt?
This discussion was catalyzed by the enormous amount of confusion that was created when Google announced last month that it would not expose the ATT prompt in its owned-and-operated apps. This revelation seemed to fly in the face of Facebook’s announcement in December that it must show the ATT prompt in its owned-and-operated apps, and that ATT would govern not just app campaigns run on its platform but also mobile web campaigns. How can Google avoid showing the ATT prompt if Facebook seems to have been told very explicitly that it must show the ATT prompt?
In this podcast, Thomas Petit and I discuss this very confounding situation and attempt to provide clarity on when exposure of the ATT prompt is required, and why.
I ultimately had wanted to engage with this topic in a blog post, which I started writing. As I discuss in the podcast, 1000 words into the post, I had merely only finished providing background on the situation: about how Facebook had announced that it wouldn’t show the ATT prompt and then retraced its course, about how Apple ostensibly demands that all mobile advertising be governed by ATT, etc.
This is an abstruse topic, and it’s hard to parse, even for people that live mobile advertising and consume updates on a real-time basis. There are no easy answers as relates to ATT, but I hope that this podcast adds some clarity to the subject.
The Mobile Dev Memo podcast is available on: