Skip to main content
Troubleshooting Flytedesk Digital

Learn some common issues that may be preventing ads from serving in your Flytedesk Digital unit

Publisher Support avatar
Written by Publisher Support
Updated over a year ago

The Flytedesk Digital tool generates a constant stream of revenue on your website and adds your organization to a premium national network of student media websites. Once you install Flytedesk Digital, remnant ads should start serving in the unit within 24 hours.

If you don't see remnant ads serving in your Flytedesk Digital unit within 24 hours, this article will help you troubleshoot some common potential causes. Please go through the steps below to make sure everything is fully functional.

-

1) Make sure you have tagged a specific unit as a Flytedesk Digital unit on your website

One common installation issue is that your site is tagged with Flytedesk's script, but a specific unit is not tagged with a class. You need both tags for ads to start appearing on your site. For help with unit class tags or WordPress widgets, please consult one of the support articles below:

2) Make sure the script and class tags are added in the right spot on your site

Another common installation issue is that the script and/or class tags are added in the wrong spot on your site. If this is the case, you'll need to revisit the installation instructions in Step 1 to verify that the unit is properly installed. Here are a few ways to check if this is the case:

2a) Check if your script tag is being detected

Go to your Flytedesk media kit digital property settings (where you got your script tag from) and check the status under 'Active Domains.' If you see "The Script Tag has not been detected...", then the script tag may be located in the wrong place on your site, the code may have been edited, or it may not be installed on your site at all:

2b) Inspect your website code

Inspect your website (command+option+I on Mac) to check for your script tag and tagged unit. You'll see a window pop up that looks like this:

Within your inspector tool, search for the terms “flytedigital” and "flytead." (Just use command+F to search). If just one, or neither, of these terms are in your site code, then your site is likely missing one of the two required tags (script and class).

3) Turn off your ad blocker

If your ad blocker is turned on, you won't see any ads in the unit. Turn off your internet ad blocker to verify that ads are appearing.

4) If you're using the WP plugin, remove any manual code

If you had previously installed (or attempted to install) Flytedesk Digital manually but switched to the WordPress plugin, make sure any manual code you added to your site is removed. (The WordPress code and the manual code could be interfering with one another and preventing the WordPress plugin from functioning.)

5) Double check that the Flytedesk tags have not been edited

If you made any changes to the script tag or class tag code from your Flytedesk media kit when installing the code on your site, then the unit will not function properly. If you're not sure, try revisiting your digital media kit to grab and reinstall the code.

6) Navigate to the page where your ads should be serving

Depending on how you set up your unit, ads may be serving on your homepage only, throughout your site, or just on specific pages. Double check that you're on a page of your website that is meant to be serving Flytedesk Digital ads.

7) Try another browser

Ad viewability might be affected depending on the browser you're using. Try one or two additional browsers to check if ads are displaying on one and not another.

8) Authorize Flytedesk remnant advertising

If remnant ads were serving on your site previously with Flytedesk Digital and now aren't, you may need to add additional permissions to your ads.txt file. The ads.txt file provides information to your advertising platform regarding which publishers are allowed to serve ads on your site. Flytedesk's remnant network must be whitelisted in order to allow our ads. To authorize us, add the following line to your ads.txt file:

google.com, pub-6349992477875006, DIRECT, f08c47fec0942fa0

9) Troubleshoot a 403 error

A 403 error occurs when Google AdSense detects a reason not to serve ads on your site. To check if you have a 403 error, inspect your website, open the console, and check for a red error message:

403 error causes will vary on a case-by-case basis. Most likely, they are caused by AdSense policy violations such as content & user experience issues.

We recommend going through AdSense's troubleshooting guide or reaching out to AdSense support for help troubleshooting a 403 error.

-

If after taking these steps you're still not seeing ads serving in the unit, please email your Flytedesk rep with the following info:

  • Name of your publication

  • Website URL

  • Method of installation (WordPress or manual)

  • Installation date

  • Is the unit dynamically loaded or always present?

  • Type of ad that's not displaying (remnant, national direct, or Ad Shop)

  • Were ads displaying previously, and now they aren't?

  • More description of the issue

Did this answer your question?