Documentation

URL/Cookie Destination [Custom] Debugging

Last update: Fri May 08 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

URL and cookie destinations fail to fire when segment qualification does not occur during an active website visit with real-time evaluation. These destinations trigger only after real-time trait qualification and a live page load with edge interaction. Offline-only segments do not activate destinations until a new site visit occurs after qualification.

To resolve the issue, validate real-time qualification and destination triggering behavior.

Description description

Environment

  • Adobe Audience Manager
  • URL destinations and cookie destinations (Custom)
  • Real-time website traffic with edge server interaction

Issue/Symptoms

  • URL or cookie destination does not fire during an active site visit
  • Network requests do not show destination pixel or partner endpoint calls
  • Browser does not create the expected destination cookie
  • Segment appears qualified, but the destination does not activate in real time

Resolution resolution

Steps to resolve

  1. Validate pixel firing or cookie creation

    1. Open the website.

    2. Press F12 (Developer Tools).

    3. Go to the Network tab.

    4. Filter for:

      • demdex.net
      • Partner endpoint
      • Pixel ID

    Alternative approach:

    Validate cookie creation

    1. Open the website.
    2. Press F12 (Developer Tools).
    3. Go to Applications and look for the cookie name.

    If the pixel is not firing or the cookie is not visible:

    • The user likely did not qualify.
    • The segment is not eligible for real-time evaluation.

  2. Check segment qualification via API

    For anonymous users:

    code language-none 
    https://<subdomain>.demdex.net/event?d_uuid=<UUID>&d_rtbd=json

    For authenticated users:

    code language-none 
    https://<subdomain>.demdex.net/event?d_rtbd=json&d_cid_ic=<integrationCode>%01<CustomerID>

    You should see destination-related information in the JSON response.

  3. Force trait qualification (testing)

    If the segment is not qualifying naturally, you can simulate qualification.

    Anonymous:

    code language-none 
    https://<subdomain>.demdex.net/event?d_sid=<traitID>&d_rtbd=json

    Authenticated:

    code language-none 
    https://<subdomain>.demdex.net/event?d_sid=<traitID>&d_rtbd=json&d_cid_ic=<integrationCode>%01<CustomerID>

    Documentation on the DCS API:

    https://experienceleague.adobe.com/en/docs/audience-manager/user-guide/api-and-sdk-code/dcs/dcs-event-calls/dcs-url-receive

  4. Verify data collection and partner configuration

    Website data collection issue

    • Data collection call is missing required signals.
    • Incorrect trait logic causes missing identity information for logged-in users.

    Check:

    • Data collection request (demdex / AA / interact call)
    • Identity parameters
    • Integration code configuration

    Partner-side configuration issue

    Some partners require:

    • Pre-created custom audiences
    • Specific pixel ID mapping
    • Activation approval

Verify prerequisites in the partner platform before expecting delivery.

  • Pre-create custom audiences
  • Specific pixel ID mapping
  • Activation Approval
  • Verify pre-requisites in partner platform before expecting delivery
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f