Standard implementation self-check

Last updated on December 15, 2016

Before sending your test page to your OpenX representative, you can perform the following troubleshooting steps. Similar steps can be used to perform troubleshooting in the other major browsers.

Verify defined ad slots

Chrome Develop tools console screenshot

  1. From your test page, open the Chrome web browser.
  2. Open the Developer tools panel: Chrome menu > More tools > Developer tools.
  3. Click the Console tab.
  4. Type OX_dfp_ads into the console and press Enter. This will list all defined ad slots. If this response returns an empty list ([]) or ERROR, please ensure that the OX_dfp_ads global variable has been defined.

Confirm PUBLISHER,NETWORKCODE and SITE placeholders

Screenshot of OX.dfp_bidder_config

Type OX.dfp_bidder_config into the console and press Enter. If this returns {}, confirm that you are using the correct values for PUBLISHER,NETWORKCODE and SITE when loading the JSTAG library.

Confirm the number of ad calls

Screenshot of acj calls.

  1. Click the Network tab.
  2. Filter for acj. This will identify all the OpenX ad calls.
  3. Verify the number of acj calls matches the number of defined ad slots on the page. If the number of acj calls and number of defined ad slots do not match:
    • The code to load the JSTAG library may be malformed
    • The PUBLISHER,NETWORKCODE orSITE value may be incorrect

Verify the key-value pairs in ad call

Verifying key value pairs screenshot

  1. Close the Chrome Developer tools panel.
  2. Append ?googfc to the URL in the address bar. The DFP Console will appear.
  3. Click the Page Request tab.
  4. Search for oxb in the Timeline. This confirms that OpenX key-value pairs are being sent to DFP. Verify the number of oxb occurrences matches the number of slots defined in OX_dfp_ads. If these do not match, some ad slots may not be defined.
Fill out my online form.