Documentation

Server-to-server device-based destinations don’t deliver segments

Last update: Tue May 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

Server-to-server (S2S) device-based destinations send segment data directly to partner endpoints without browser-based pixel firing. When delivery doesn’t occur as expected, destination mappings or audience visibility issues appear in the Audience Manager UI. To resolve the issue, validate destination mappings, audience population, and delivery status.

Description description

Environment

Adobe Audience Manager

Issue/Symptoms

  • The segment data doesn’t appear in the partner destination.
  • The destination mappings show no active delivery status.
  • The addressable audience shows a value of zero in the destination view.
  • The outbound files don’t appear or show an unexpected delivery status.

Resolution resolution

Follow these UI-level validation steps in Adobe Audience Manager. Since backend logs stay unavailable in the UI, confirm configuration and delivery indicators carefully.

  1. Remove the existing segment-to-destination mapping and re-add it to trigger metadata refresh. Allow up to 24 hours for metadata resynchronization to complete.
  2. Open the destination mapping and confirm the end date remains active. Ensure the mapping doesn’t include an expired or past end date.
  3. Verify the segment population and review the addressable audience value in the destination view. If the addressable audience shows zero, confirm identity synchronization and active merge rules.
  4. For batch or file-based destinations, navigate to Outbound File History and confirm file generation. Review the file status and confirm whether it shows success or failure. If files show successful delivery, coordinate with the partner to confirm file ingestion.

If the UI doesn’t show logs, file attempts, or expected delivery indicators, contact Adobe Support for backend log investigation.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f