Audience Manager Segment Onboarding Fails Due to Destination Configuration
A global media company uses Adobe Audience Manager (AAM) to create a segment of users who have viewed at least 3 articles about electric vehicles (EV) in the past 30 days. The segment is called 'EV Enthusiasts' and is used in Adobe Target to personalize homepage hero banners. The company also wants to onboard this segment to a third-party demand-side platform (DSP) for programmatic advertising. The AAM destination for Target is configured as a server-to-server (S2S) destination using the Adobe Target destination type. The DSP destination is a cookie-based destination with a partner ID. The segment has 250,000 qualified users in AAM. However, after 2 weeks, the Target activity using this segment shows only 12,000 users matched, and the DSP reports only 8,000 users matched. The company uses the Adobe Experience Platform Identity Service (ECID) and has declared IDs in AAM. The AAM trait for EV articles uses a rule-based trait with a 30-day recency. The Target implementation uses at.js 2.x with the Adobe Experience Cloud ID Service. The DSP requires a 1:1 ID sync and has a rate limit of 1000 requests per second. The company's data governance policy requires that all data transfers be encrypted and that user consent be obtained for advertising use.
1. What are the likely reasons for the low match rates in Target and the DSP, and how should the architect diagnose them?
Read the worked answer
Low match rates in Target (12,000 out of 250,000) and DSP (8,000) indicate issues in segment qualification, ID sync, or destination configuration. For Target: 1) Check the AAM-to-Target destination status: ensure the destination is active and the segment is mapped to the correct Target mbox/audience. 2) Verify that the AAM segment is being evaluated in real time: the trait uses a 30-day recency, but if the trait's data source is not receiving real-time signals, users may not qualify. 3) Confirm that the Target implementation is passing the AAM segment ID via the mbox (e.g., using the 'aam' parameter or the Experience Cloud ID Service). 4) Check for ID sync issues: AAM uses the ECID to match users, but if the ECID is not consistent between AAM and Target, matches fail. 5) Review the segment population in AAM: 250,000 may be the total qualified, but only those with a recent ECID and cookie may be matchable. For DSP: 1) The cookie-based destination requires a 1:1 ID sync; if the ID sync is not firing or is rate-limited, matches will be low. 2) Check the DSP's rate limit (1000 req/sec) and whether AAM is throttled. 3) Verify that the segment is shared with the DSP destination and that the destination is active. 4) Ensure the DSP's partner ID is correctly configured. 5) Check consent: if users have not consented to advertising, they may be excluded. Diagnostic steps: use AAM's Audience Lab or segment reports to see match rates; check the destination's delivery reports; use browser debug tools to verify ID sync calls; review AAM's onboarding status for the DSP.
2. What steps should the architect take to improve match rates while ensuring compliance with data governance and consent requirements?
Read the worked answer
Improve match rates: 1) For Target: ensure the AAM segment is mapped to a Target audience and that the mbox call includes the AAM segment data. Use the 'setCustomerIDs' method to pass declared IDs if available. Consider using the Adobe Experience Platform Web SDK to unify identity and data collection. 2) For DSP: increase ID sync coverage by implementing the AAM ID sync on all pages, especially where users are most active. Optimize the ID sync by using the 'dpm' (Data Partner Match) or server-to-server sync if the DSP supports it. 3) Work with the DSP to increase their rate limit or batch requests. 4) Expand the segment definition to include users with a longer recency or broader behavior to increase pool size. 5) Use AAM's look-alike modeling to expand reach. 6) Ensure that the AAM trait is firing correctly by validating data collection. Compliance: 1) Implement consent management: only onboard users who have opted in to advertising. Use AAM's consent flags or integrate with a consent management platform (CMP) to pass consent status. 2) Encrypt all data transfers: use HTTPS for all destination calls and ensure the DSP supports secure ID sync. 3) Review the data governance policy with legal to confirm that the segment data can be used for advertising and that the DSP's data usage meets requirements. 4) Document the data flow and obtain necessary approvals. 5) Monitor for any privacy violations and provide an opt-out mechanism.