Solutions to frequent problems

Make sure that:

• The campaign has the active status.

• The campaign has a banner with the active status.

• The start date and time of the campaign (banner display) are in the past.

• The page has an ad tag from the campaign's placement.

If this is all correct, check whether placement is enabled for banners:

1. Go to the Placements tab of the banner.
2. Make sure that the banner placements are enabled.

If Sites not found is displayed on the banner's Placements tab, go to the campaign's Placement tab. Make sure that the site pages where banners should be placed are enabled.

If the placements are enabled on the banner's Placements tab but there are still no impressions, make sure the ad tag is taken from the site level.

If the ad tag is taken from the site level, check whether the referer templates are configured correctly.

Make sure that the banner is displayed correctly before uploading it to Adfox.

Check the HTML creative: unzip the archive on your computer and open the .html file. If the banner is displayed incorrectly, fix it according to the requirements.

If it's a third-party ad tag, make sure it works. Check the ad tag in any test environment before uploading the banner to Adfox. If it doesn't work, contact support of the system that provided it.

Make sure that the banner is clickable before uploading it to Adfox.

Check the HTML creative: unzip the archive on your computer and open the .html file. Make sure that the banner click works. If it doesn't, it means the creative doesn't have a button (link) or its script that processes banner clicks is incorrect. Fix the errors according to the requirements before uploading the banner to Adfox.

If it's a different ag tag, make sure that it includes the link and the link wraps the clickable area. Create a link according to the instructions.

Check the HTML creative: make sure that the link isn't specified directly in the banner tag. For Adfox to count banner clicks, the link must be specified as the %banner.reference_user1% variable. When uploading the banner, the link specified in the Transition URL field in the banner parameters is used as the variable.

It's important that you use randomized links for installing in third-party systems.

Every Adfox link has the pr parameter with the [RANDOM] value, to which you need to add the randomization function (generating a random integer from 1 to 4294967295 inclusive).

Make sure a random number is generated when calling the Adfox pixel. It should be different for each pixel request.

If the Adfox pixel is randomized, but there is still a discrepancy, contact support. In the request form, please specify:

• Banner IDs.
• Indicators where the discrepancies are (impressions or clicks).
• Logs of the third-party system that provided the pixels.

If the pixel is not randomized, discrepancies may reach 30%.

Most links to pixels of third-party systems include a parameter where you need to substitute a random number in order to reduce the statistics discrepancy. In Adfox, this number is generated by the %random% variable: you need to specify this variable as the value of the parameter responsible for randomization.

See examples of the most common third-party systems links where variables are substituted for randomization.

If the third-party pixel is randomized, but there is still a discrepancy, contact support. In the request form, please specify the indicators where the discrepancies occurred (impressions or clicks) and logs of the third-party system that provided pixels.

If the pixel is not randomized, discrepancies may reach 30%.

Possible reasons:

• There is no Yandex Metrica tag.

  The ad contains a URL that redirects to a page that doesn't have a Yandex Metrica tag. Follow the instructions to make sure the tag is installed correctly.

• The traffic source isn't defined.

  When determining the traffic source, the referrer isn't transferred if the user is redirected from an HTTPS site to an HTTP site. If your site is running over the HTTP protocol, you won't see the traffic source if this source is running over a secure HTTPS connection.

  See how to solve this issue in Yandex Metrica Help.

• Impression discrepancy.

  When comparing page impressions in Yandex Metrica and banner loads in Adfox, exclude impressions to users who use ad blockers. Adfox isn't displayed for users with AdBlock or other ad blockers.

Targeting works incorrectly. Possible reasons:

• Non-compliance with the impression frequency when frequency targeting is configured.

  Make sure that targeting settings aren't redefined at the placement or banner level.

  1. Click Targeting next to the name of the campaign and go to the Summary tab.
  2. Choose Targeting and make sure that frequency isn't redefined at the placement (site, section, or placement) or campaign banner level.

  Learn more about targeting levels

• Non-compliance with the impression frequency when frequency targeting is configured for a campaign that has the XML video banner type, taking into account impressions by event.

If the targeting doesn't work, make sure that the Adfox ad tag on the site page contains parameters in the format puidN , where N is the characteristic number from 1 to 63, with values for targeting. Make sure that the correct identifier (ID) of the characteristic is passed to puidN.

To view the value IDs, go to Settings → Custom targeting → Characteristic → Values.

If the ad tag was installed on the site before enabling custom characteristics, you need to add the parameters to the tag manually or obtain a new ad tag in the interface.

If the ad tag hasn't changed, follow the instructions.

If the targeting doesn't work, make sure the necessary targeting values are passed to the ad tag:

• The ad tag contains the pk parameter that keywords are added to.

• The values are the same as the values set in the interface.

If the ad tag hasn't changed, follow the instructions. Make sure that the necessary values are correctly added to the ad tag and match the values set in the interface.

The desired banner is not displayed on the site page, and in the browser console (F12) on the Network tab, a request to https://yandex.ru/ads/adfox/ returns an error saying "status":"404".

1. If the code is embedded from the placement level (the following is shown in the comments):

   <!--Adfox START-->
   <!--account-->
   <!--Placement: Site name / Section name / Placement name-->
   ...
   

   Check whether the placement that the ad code was received from is present in that section. You can determine this by the section name in the code comments.

   The Banner type and Position parameters of the site and ad code must match.

   If there is no placement with such parameters, do one of the following:

   • Create a placement.
   • Remove the ad code from the page.

2. If the code is embedded from the site level (the following is shown in the comments):

   <!--Adfox START-->
   <!--account-->
   <!--Placement: Site name / * / *-->
   ...
   

   Check if the page belongs to the appropriate section:

   • The section is identified correctly: Go to the Placements tab of the found section and check whether it contains a placement with the same Banner type and Position parameters as those of the ad code. If there is no such placement, create one.

   • The section is identified incorrectly or not found: This means it does not comply with the existing section referer templates. Check the section referer templates and do one of the following:

     • Add a template to the desired section, which would fit the URL of our page.
     • Create a new section and add the necessary placements to it.

3. Check if the request parameter indicating your account ID has changed.

   In the ad tag, this parameter is in the ownerID variable:

   <div id="adfox_16244342575025707"></div>
   <script>
   window.yaContextCb.push(()=>{
       Ya.adfoxCode.create({
       ownerId: 353052,
       containerId: 'adfox_16244342575025707',
       params: {
           pp: 'g',
           ps: 'ezwy',
           p2: 'gnhv'
       }
       })
   })
   </script>
   

   If it's missing or its value differs from the new ad code, we recommend that you get the ad code in the interface again and embed it on the site.

4. If the problem persists, please contact support.