Sign in to Community
Sign in to view all badges
Expand my Community achievements bar.
There are two ways in which one can validate, if the URL destinations are triggered correctly or not:
1. To verify the URL destination is correctly triggered, you can easily check by performing a DCS call.
Below is the sample call you can use to force qualify for segment, here sample segment id is 12345678 :
Trait qualification key value pair
It is required if you want the DCS to return a response as JSON object
data provider ID%01user ID.
Contains one or more pairs of data provider IDs (DPID) and data provider user IDs (DPUUID) assigned by Audience Manager. For example: DPID%01DPUUUID.
AAM UUID. 38-digit device ID that Audience Manager associates to each device it interacts with. Audience Manager tries to save this ID as a cookie in the "demdex.net" 3rd party domain.
The response of the above call, would be something similar to below:
In the response, we can see that the URL destination is correctly returned.
2. The other way to validate the URL destinations is to verify the network calls:
To validate that a pixel is properly firing on site:
The step-by-step process to create URL/pixel destinations are already outlined on the public-facing documentation.