{"id":8528,"date":"2020-08-19T07:47:00","date_gmt":"2020-08-19T07:47:00","guid":{"rendered":"https:\/\/tenjin.com\/?p=8528"},"modified":"2024-02-27T10:55:39","modified_gmt":"2024-02-27T10:55:39","slug":"ios-14-mmp-free-publisher-guide","status":"publish","type":"post","link":"https:\/\/tenjin.com\/ja\/blog\/ios-14-mmp-free-publisher-guide\/","title":{"rendered":"iOS 14\u3078\u306e\u6e96\u5099\uff1aElixir\u306e\u958b\u767a\u8005Kevin Bravo\u306b\u3088\u308bMMP\u30d5\u30ea\u30fc\u30d1\u30d6\u30ea\u30c3\u30b7\u30e3\u30fc\u30ac\u30a4\u30c9"},"content":{"rendered":"

One month before the\u00a0release of iOS 14<\/a>, there are still many speculations around what\u2019s happening next for MMP<\/a>s. How much will their role change? Are advertisers still ok paying 1-5 cents for each paid tracked install on iOS, even though it no longer has user-level granularity? \u00a0Will Apple allow MMPs to validate Conversion Values though it wasn\u2019t mentioned in any Apple documentation? While those questions are unclear, we decided to tackle things that developers can do today, without the involvement of MMPs.<\/p>\n\n\n\n

We sat down with the co-founder of the mobile growth agency 2ndPotion<\/a>, Kevin Bravo<\/a>, to talk about things that developers can utilize right now that are documented by Apple. Kevin created the first open-source solution that interacts with Apple\u2019s SKAdNetwork called Elixir<\/a>, so we know he\u2019s perfect for this sort of conversation.<\/p>\n\n\n\n

Here is what we will cover today with Kevin.<\/p>\n\n\n\n

1) For developers and game designers<\/strong>, iOS pop-up asks for consent to share the user\u2019s IDFA \u2013  AppTrackingTransparency<\/em> method.<\/p>\n\n\n\n

2) For developers<\/strong>, an overview of the new attribution framework from Apple \u2013  SKAdNetwork<\/em>.<\/p>\n\n\n\n

2.1) For developers<\/strong>, attribution of installs \u2013  integrate registerAppForAdNetworkAttribution()<\/em>method<\/p>\n\n\n\n

2.2) For developers<\/strong>, attribute post-install events \u2013 integrate updateConversionValue(_:)<\/em>method<\/p>\n\n\n\n

2.3) For UA managers<\/strong>, understand how Apple reports installs and post-install events to ad network \u2013  Postbacks and timers<\/p>\n\n\n\n

3) For the whole team to brainstorm<\/strong>, what could be better \u2013 <\/strong>Best Practices & Current Pain points<\/p>\n\n\n\n

1) Asking users to share their IDFA \u2013 Integrating ApptrackingTransparency<\/a><\/h2>\n\n\n\n

Kevin: <\/strong>AppTrackingTransparency is a framework available for iOS 14 that allows app developers to ask permission to track the user. This permission is required to access the user\u2019s IDFA for attribution purposes.<\/p>\n\n\n\n

Integrating it and using it will require you to prompt the user to access their IDFA with this popup:<\/p>\n\n\n\n

If the user accepts tracking, you\u2019ll have the ability to request their IDFA. Otherwise, the IDFA will be 0000-0000-0000-0000.<\/p>\n\n\n\n

Keep in mind that you won\u2019t be able to ask permission if the user is LAT (Limited Ad Tracking) ON.<\/p>\n\n\n\n

Q: How many times can I show native popup?<\/strong><\/p>\n\n\n\n

Kevin: <\/strong>You can only show itonly once per device.<\/p>\n\n\n\n

Q: Can I ask for user consent again if it\u2019s rejected initially?<\/strong><\/p>\n\n\n\n

Kevin: <\/strong>If the user already saw this popup, you won\u2019t be able to display it again.<\/p>\n\n\n\n

Q: Can I show my custom popup before the native one?<\/strong><\/p>\n\n\n\n

Kevin: <\/strong>You can decide when you will display this pop-up, which means that you\u2019re allowed to post an additional pop up before.<\/p>\n\n\n\n

This way, you can decide to show the permission popup only if the user said yes to your custom one.<\/strong><\/p>\n\n\n\n

This strategy is already used by many companies to push notifications requests and will help allow you to have a 2nd opportunity to ask for permission.<\/p>\n\n\n\n

Q: What happens if an app developer does not integrate AppTrackingTransparency?<\/strong><\/p>\n\n\n\n

Kevin: <\/strong>If you don\u2019t want\/need to request the IDFA, you can decide not to display this popup.<\/p>\n\n\n\n

This means that you won\u2019t have access to their IDFA (it will display as 0000-0000-0000-0000) and that ad networks won\u2019t have access to it as well.<\/p>\n\n\n\n

2) Overview of the new attribution framework from Apple \u2013  SKAdNetwork<\/a><\/h2>\n\n\n\n

Kevin:<\/strong> Apple provides an anonymized attribution solution called SKADNetwork<\/strong>, enabling apps to keep tracking installs coming from different ad networks, without compromising users\u2019 anonymity.<\/p>\n\n\n\n

When using SKADNetwork, a signature is attached to each ad click. When the user opens your app for the first time, Apple will be able to verify if they\u2019re coming from a specific ad with this signature.<\/p>\n\n\n\n

Then, a postback is sent back to the ad network to attribute a new install.<\/p>\n\n\n\n

The signature doesn\u2019t contain any identification data, keeping privacy at maximum by making it impossible to attach an install to a specific user.<\/p>\n\n\n\n

To integrate SKADNetwork, you need to call two methods:<\/p>\n\n\n\n