A couple of questions

[#1]

1. Please explain in detail what Adobe Audience Manager sending to Google (SERVER TO SERVER) and Facebook (Pixel based URL Destination) that is matching these devices/customers?

2. What workarounds is Adobe is working on to tackle Safari Intelligent Tracking Prevention (ITP2)?

[#2 · Accepted solution]

Hello There,

Please find inline inputs below:

1. Data share between AAM and Google/FB involves a unique identifier at both ends which in general scenario is the deviceID. for AAM, it is AAM ID and similarly for Google/Facebook it is this Id which gets identified. As customerIds are linked with AAMUUID only, using this information a unique customer can be identified.

2. For ITP2, currently, Audience Manager team is evaluating workarounds for current and anticipated tracking prevention announcements. In the immediate term, we’re working on a scalable solution to capture full referer URL data for all customers. Further out, we’re exploring ways to leverage first-party cookies to track Safari users.

For more information about user identification in two systems, please follow this document.

[#3]

Hi mandeepkang1981

The Google/FB pixel call is an async call which is enabled in the audience manager backend which your audience manager consultant and client care will be able to add. There are no other changes required to make sure the order in which the pixel/id sync fires and audience manager code takes care of that.

Thanks,

Somya Mehta

[#4]

Thanks ASodhi-AAM​

In order for this to happen - Does this mean that Google/FB pixel must also fire at the same time as the AAM demdex call in order for the ids to reconcile and sync?

The synchronization process allows Audience Manager and a data vendor to reconcile these different IDs and identify users in their respective systems.