As of 29 October, both iOS and Android Facebook apps ban user-level data transmission. Only aggregated data will be available (the hidden source user level).
FB starts transmitting encrypted data to Google Play alongside. To decrypt the data, you must obtain a key from FB.
AF already has a field where you can enter the key. The raw data is available as of 4 November. Appsflyer has investigated things to do and the deadlines so that you’ll be ready.
As of 4 November, considering a key introduction, things will operate in the same way as before, won’t they?
Not exactly. It only applies to Android OS and click-through attribution considering data decryption received from Google Play.
Will the data stay raw from now on, or should I wait for finished data at some point? If the latter, when will it happen?
- iOS FB attributed data will only be available as aggregated data
- For Android, the view-through data will only be available as aggregated data
- Android click-through data will be supported by Google Play Referrer for Facebook, and it will be available as raw data
To put it bluntly, the working principles will now be similar to the UAC?
Not exactly. Android UAC operates without change. On iOS, there are many limitations given that there’s no ATT in the Google apps and no Search channel.
And now, for the dummies, please. Please, correct my misunderstanding in the comments if there are any.
As of 4 November, naming should work ok. You only have to insert the key from the FB cabinet.
However, there is a chance that some data might be lost (because of FB). I hope I’m wrong. But, just in case, add deep links to work with FB and compare losses from now on. As I said, I might be wrong.
Source: Pro Mobile | Lukos Apps