+6I noticed in the docs that the new Facebook Conversions API has the option to send events even when ATT content has not been given by the user. However, a few screens above the docs say that the iOS IDFA is still required.
We would prefer to skip using IDFA and asking for permission for UX reasons. Are we still required to try to collect the IDFA with Conversions API or can we completely ignore it?
+6Ok, so we tested this scenario and it appears that IDFA and ATT content are no longer required to send events to Facebook when using Conversions API (when the option for that is turned on ofc).
We’d still like an official confirmation on that issue though. 😅
+6Hi! I apologize for the confusion in the documentation. We just recently released the ability to use the Conversions API, and missed updating that aspect. Yes, you can not collect the IDFA or ATT content if you would like and the Facebook integration will still send the events when configured for the Conversions API.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
