Some thoughts on the imminent departure of our old friend the third-party cookie
Our Blog See all posts Some thoughts on the imminent departure of our old friend the third-party cookie TL; DR I might
Is Apple concerned with fraud detection in iOS14 or not? Put in another way, are they aware of significant ad fraud blindspots in the upcoming iOS and planned discouragement of IDFA?
I started to think about the issue because an adtech noob friend asked me an interesting question recently: what is the difference between what Apple said about iOS14 and fraud detection in “User Privacy and Data Use” vs. what Ari Paparo said in an AdExchanger article “IDFA Apocalypse: What We Know (And Don’t)”? I assume others might be curious as well.

In User Privacy and Data Use, Apple states that “You may track users without obtaining user permission through the AppTrackingTransparency framework if… the data broker with whom you share data uses the data solely for fraud detection, fraud prevention, or security purposes, and solely on your behalf.”
But in an AdExchanger article “IDFA Apocalypse: What We Know (And Don’t),” Ari Paparo asks “How can fraud detection work with this little data to track down fake installs?”
Which one is correct, my noob friend asked. Didn’t Apple just say that fraud detection gets an IDFA pass?
Apple does allow the use of a different ID, Identifier for Vendors (IDV) to be used for fraud prevention, and that’s useful if you have someone trying to defraud the app itself or hack the corporate servers for the game manufacturer. But it’s not at all useful for stopping app install fraud, which is still common. It’s common enough to be an open secret in AdTech that many, if not most of the IDFAs coming through the bid-stream are not real; they are single occurrence IDs that we never see again. We also know that there are more downloads than there are devices per region to be real or healthy.
Publishers who generate more ad space get more ad revenue, and publishers who get click-throughs drive even more, yet again, publishers that actually drive installs get the most (because demand is higher for their property over time). So some cheat the algorithm and set up iOS emulators with constantly rotating IDFAs to play their games and click every ad to boost their revenue. When that brings the app install page, they download and launch the game, then shut it down and go back to what they were doing. It’s part of the reason that companies like Zynga and Machine Zone use in-app purchase as their key metric, not installation numbers.
We all know this is happening and try to fight it to an extent, but mostly we just price it into the cost of our bidding. My concern is that without transparency, the industry may see a significant increase in ad fraud precisely because SKAdNetwork is the new de facto standard measurement, and doesn’t allow user level attribution. If we can’t tell the exact user who installed, how can we know if they are a real user? The only way would be if Apple told us in the SKAdNetwork data feed. In theory, they could query their data and verify the install against an internal list of real iOS identifiers, but I’ve not seen anything about that in their public facing documentation.

So, yes, fraud as one might generally think about it gets a pass using IDV, but IDFA will still require consent to acquire, and therefore is not going to be able to be used to prevent ad fraud—a place where IDV is generally valueless.
It’s something for all parties (well, especially Apple) to consider.
Our Blog See all posts Some thoughts on the imminent departure of our old friend the third-party cookie TL; DR I might
Our Blog See all posts Will closing the door on IDFA open the door to Ad Fraud? Is Apple concerned with fraud
See all posts Perspectives on Cookie-less future Every day while scrolling on social media or reading news, we see articles about cookie-less
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-advertisement | 1 year | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement". |
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
| Cookie | Duration | Description |
|---|---|---|
| __cf_bm | 30 minutes | This cookie is set by CloudFlare. The cookie is used to support Cloudflare Bot Management. |
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
| Cookie | Duration | Description |
|---|---|---|
| _ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
| _gat_gtag_UA_72242259_1 | 1 minute | This cookie is set by Google and is used to distinguish users. |
| _gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.