Audience manager set up - demdex.net

[Franc_G]

hi all, have looked at the DIL.js documentation and its rather confusing. Can someone explain me in very simple terms how the DIL (audience manager) needs to work ?

When I look at the current set up, I can see numerous demdex.net request.

• https://dpm.demdex.net/id?d_visid_ver=
• https://fil.demdex.net/dest5.html?d_nsid
• https://dpm.demdex.net/ibs:dpid=

Need some sort of diagram or a rough idea of a flow. 

There is also this client side vs server side forwarding, which is not quite clear. My understanding is that the server side forwarding (when enabled on the reporting suite level) share all the data from reporting suite with the audience manager service. It would be good if someone could confirm it. Thanks. 

[akshaykapil23]

Hello @Franc_G ,

Thanks for posting your query.

In a very simple language, When AAM is implemented using DIL implementation. The data pass directly to AAM in form of signals. You may not be able to control the data as the data passes to AAM as and when any HIT or interaction done on the website. 

Whereas Server-Side Forwarding helps you to control the dataflow as the data 1st gets collected in Adobe Analytics Report Suite. From Admin section you may control which Traffic Variables can be shared across with AAM

Please refer to the link mention here : https://experienceleague.adobe.com/en/docs/audience-manager/user-guide/implementation-integration-gu...

[Franc_G · Accepted solution]

The DIL (Data Integration Library) library is not required if server-side forwarding is enabled between Adobe Analytics and Adobe Audience Manager. Server-side forwarding is designed to streamline data transfer between these two systems and eliminate the need for a separate DIL implementation on the client side.

Here’s a breakdown:

Why DIL Is Not Needed with Server-Side Forwarding

1. Direct Data Transfer: Server-side forwarding sends Adobe Analytics data directly to Adobe Audience Manager via Adobe’s backend servers. This means the same data collected by Adobe Analytics is automatically forwarded to Audience Manager without requiring additional JavaScript.
2. Simplified Implementation: By using server-side forwarding:
• No additional DIL JavaScript library is required on your website.
• Redundant client-side data collection processes are avoided, reducing page load times and complexity.
3. Data Consistency: Since Analytics and Audience Manager share the same data layer through server-side forwarding, the risk of discrepancies is minimized.

When You May Still Need DIL

You might need the DIL library if:

1. Additional Data Collection: You want to send data directly to Audience Manager that is not captured by Adobe Analytics. For example:
• Collecting custom signals or traits not tracked in Analytics.
• Sending mobile app data or other platform-specific data.
2. Non-Analytics Implementations: If you are using Audience Manager as a standalone DMP without Adobe Analytics, you would need to implement DIL for data collection.
3. Hybrid Setup: In cases where only some data is forwarded server-side, you might use DIL for supplemental data collection.

Best Practices

• Use Server-Side Forwarding if Analytics Is Deployed: If you're already using Adobe Analytics, server-side forwarding is the most efficient way to integrate with Audience Manager.
• Avoid Duplication: Do not enable both DIL and server-side forwarding for the same data, as this can lead to duplicate traits and inflated segment counts.
• Testing and Validation: Use tools like the Adobe Experience Platform Debugger to ensure data is being forwarded and processed correctly.

Summary

• Server-side forwarding enabled? No need for DIL.
• Additional or non-Analytics data? Consider DIL for those cases.

Focus on your use case to decide whether DIL is necessary, but in most Analytics-integrated implementations, server-side forwarding suffices.