You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've reviewed the latest API docs, and have tested the following custom filters on a handful of domians that include FB widgets and like buttons. These updates should cover a majority of marketing and ad tracking that takes place in the latest versions of the embedded FB widgets and other FB measurements in the larger web.
There may be some legacy trackers from older/deprecated APIs and widgets, but these filters will cover off on the latest tracking with minimal webcompat and other breakage.
There may be some additional countermeasures (websockets, xhr using php), but those items need additional investigation, as they are closely linked with functionality that users would be opposed to breaking, based on user feedback.
The additional countermeasures mentioned above extend beyond the scope of the FB Ad and Marketing API documentation, so would be best handled in a separate issue if they are encountered.
The text was updated successfully, but these errors were encountered:
I've reviewed the latest API docs, and have tested the following custom filters on a handful of domians that include FB widgets and like buttons. These updates should cover a majority of marketing and ad tracking that takes place in the latest versions of the embedded FB widgets and other FB measurements in the larger web.
There may be some legacy trackers from older/deprecated APIs and widgets, but these filters will cover off on the latest tracking with minimal webcompat and other breakage.
There may be some additional countermeasures (websockets, xhr using php), but those items need additional investigation, as they are closely linked with functionality that users would be opposed to breaking, based on user feedback.
The additional countermeasures mentioned above extend beyond the scope of the FB Ad and Marketing API documentation, so would be best handled in a separate issue if they are encountered.
The text was updated successfully, but these errors were encountered: