They claimed that the Facebook Conversion API is the solution to overcoming iOS 14's privacy policies, however I still have two questions:
- I understand that the Conversion API is sent from the server to Facebook, but the event must still be triggered from the client side, correct? So, if adblock can block all existing tracking domains, would the conversion API, like pixel, become obsolete?
- If the event is sent from the server to Facebook, there is no way for the event to know the client's device information or anything else, so this information must be coming from the client, but iOS 14 has blocked those information access authority if the user selects "Not Allowed," so the conversion API should still be useless compared to pixel, right?
CodePudding user response：
The events are sent from the client to a conversions api service on the client domain, so they’re not blocked by cross-domain privacy restrictions.
The service can then relay those events over to facebook, server to server.
client => fb.mydomain.com => facebook.com
CodePudding user response：
The Facebook Conversion API, unlike the Facebook Pixel, does not rely on cookies for tracking and can be implemented in a way that complies with the iOS 14 privacy policies. The Facebook Conversion API uses server-side tracking, where events are sent directly from the server to Facebook, rather than client-side tracking, which uses cookies stored in a user's browser. This makes the Facebook Conversion API less vulnerable to the limitations imposed by the new iOS 14 privacy policies, which restrict the use of cookies and other tracking technologies on Safari.
However, it's important to note that even with the Facebook Conversion API, advertisers will still need to obtain user consent through the App Tracking Transparency framework in order to access the device's advertising identifier. This framework requires that users be given clear information about how their data will be used and have the option to opt-out of tracking.
In summary, the Facebook Conversion API can overcome the limitations imposed by the iOS 14 privacy policies because it uses server-side tracking, which is less affected by the restrictions on cookies and other tracking technologies.