Media Tag Validation Guide

Organizations can integrate data from all their media-buying activities by integrating the SF DMP tagging infrastructure into their campaigns. This article describes the general process for verifying DMP Media Tagging.

Test for Impressions

Use Chrome developer tools, or the Firebug browser extension and use the Network or Net tab to check that:

  • The pixel is returning "204 no content" when viewing network status details.
  • The confIDs visible in response header parameters match the confIDs you were provided.
  • The following values are being returned correctly:
    AdvertiserID, kxbrand, campaignID, siteID, sitename, placementID, adID, creativeID.

If everything is set up correctly you should see a "204 no content" response for ad_impression.gif and controltag?confid= with corresponding IDs where the macros once were. (if Site served there wouldn't have been macros.)

Test for Clicks

Use Chrome developer tools, or the Firebug browser extension and use the Network or Net tab to check that:

  • The pixel is returning "204 no content" when viewing network status details for the click tracker.
  • The confIDs visible in response header parameters match the confIDs you were provided.
  • The following values are being returned correctly:
    AdvertiserID, kxbrand, campaignID, siteID, sitename, placementID, adID, creativeID.

If everything is set up correctly, you should see a "204 no content" response for click_tracker/track. If you received a "404" or a "504" there is something wrong with the click tracker and troubleshooting is needed.

Keys in the Impression and Click Trackers

All of the following keys should have values:
advertiserID, campaignID, siteID, sitename, placementID, adID, creativeID

If using Pointroll use creativeID for both creativeID and adID

If using Sizmek use adID for both adID and creativeID

Implementation Consideration: Even though Salesforce is approved on a number of publishers sites and on a number of networks, partner policies change from time-to-time, so please check work with those partners for the latest information.

It is also important to take note that while there are publishers who do not allow our tracking pixel, we have developed some creative ways to still collect partial and full data sets. Please work directly with the DMP Solutions team for additional information.

Troubleshooting

Site Served Placements

If you notice any issues during the validation process or the publisher that is Site-serving the tags notices an issue, request a test page from the publisher. The test page should include any of the placements in question in a straightforward testing environment. The test page can then be sent to Salesforce for further troubleshooting.

Common Server Issues

Click-tracker is firing in place of the impression-tracker:
During the validation process you will notice that the click api will be firing a “400” error and not be redirecting to the landing page URL. If this happens contact the publisher immediately.

Trackers are missing specified keys or values don’t match ad server Ids:
During the validation process it's important to check that all keys and values are present in the trackers that are firing.

Mandatory Keys:
AdvertiserID, campaignID, siteID, sitename, placementID, adID, creativeID. The IDs associated with these keys should not contain special characters. (Special characters are any non-alphanumeric characters like *, ! or %)

Need Help?

If you need help with Media Tag Validation, don't hesitate to contact the DMP Solutions team at kruxhelp@krux.com.

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk