Troubleshoot legacy DART tags with TagShooter

DoubleClick for Publishers will no longer support legacy DART tags after March 31, 2016.

If you are using legacy DART tags, you must re-tag using Google Publisher Tags (GPT) prior to the cutoff date, to ensure seamless ad serving on your site(s). Learn more

If your network uses legacy DART ad tags, you can use TagShooter to determine what's serving to your DART tags and why. TagShooter checks your page for many common JavaScript tagging errors, identifies all of the ad units and creatives on the page, and helps you visualize the ad request behavior of a web page.

TagShooter can only handle one ad request and show a single winning line item. It cannot be used to troubleshoot out-of-page ad calls using dcopt=ist.

To use TagShooter:

  1. While signed-in to DoubleClick for Publishers, locate and copy the ad tag you want to troubleshoot.

    To find the tag on your page, right-click and select View page source, press Ctrl + F (Command ⌘ + F, for Mac) to find the ad tag. It should look similar to the following:

    http://ad.doubleclick.net/N1234/adj/top-level-ad-unit/second-level-ad-unit;pos=top;sz=300x250;ord=123456

    In the upgraded version of DFP, top-level ad units are analogous to DART sites, and second-level ad units are analogous to DART zones. Learn more

  2. Paste the tag in the field in TagShooter and click OPEN, to see the debug screen for that ad request.

    TagShooter causes the ad server to restart the ad selection process, so different ads may appear because of creative rotation.

See reasons why a line item may not be serving.

This tool is only for legacy DART tags. If you're using Google Publisher Tags (GPT), you can debug tagged pages using the Google Publisher Console.

How helpful is this article:

Feedback recorded. Thanks!
  • Not at all helpful
  • Not very helpful
  • Somewhat helpful
  • Very helpful
  • Extremely helpful