Skip to main content

Challenge:
Most people will opt-out of sharing their privacy info when iOS14 fully rolls out and sends those notifications. Once that happens, FB (and other paid channels) will underreport on its performance of how many people converted from their platform, and product analytics will begin to lose key visibility. What can we set up on the product analytics / attribution side to solve the lack of visibility?

Are there any formulas, or assumptions that could be in place to estimate actual FB conversions from the under-reported performance numbers FB shows?

Need to figure out:
Primary: Understanding how to make sure data integrity post-iOS 14 implementation is correct, and what specific actions we can take to solve for the data/attribution loss (assumptions? working with 1st party data sets? etc).

Secondary: we currently use reporting/data on Kochava. Once SKAN compatible campaigns are up and running, understanding what it can/can’t tell us.

Right now data flows to Kochava, and Amplitude. Also use Segment as inbound/outbound source of truth for events and parameters.

Hi @jchenn14 ! We at Amplitude hear you out on what will happen once iOS14 fully comes into play.  As such, we have address some of the concerns about iOS14 in this Help Center doc - https://help.amplitude.com/hc/en-us/articles/360047228311-FAQ-Apple-s-iOS-14-IDFA-Changes

This will cover how iOS14 will affect Amplitude! This should also cover your concern that “post-iOS 14 implementation is correct” at least on Amplitude’s end. 

Regarding to Kochava though, that is something that we at Amplitude might not be the best for since we are not experts of that product. If this is the attribution partner you use, it may be best to reach out to them directly to better understand how they are approach iOS14. Most of the major players that Amplitude have integrations with should have solidify their plans by now. 

Let us know how else we can help! 


Reply