BuySellAds Content Portal

Other

Last Updated on March 30, 2017

This miscellaneous section of information focuses on a variety of topics that can not be grouped into large sections throughout this document. If you haven’t been able to find a technical answer to your questions throughout this section, there’s a good chance what you’re looking for may be available within this document.

What actually happens when I connect my ad server through an API integration

What actually happens when I connect my ad server through an API integration?

BuySellAds has some incredibly handy integrations with Adzerk and DoubleClick for Publishers (DFP). These integrations magically keep the marketplace updated with the correct number of impressions you can sell AND automatically creates the ad code, serves it through the ad server, and rotates with existing ad partners.

An API (Application Programming Interface) allows a third-party company, like BuySellAds, to connect and interact with components of the original system.  Adzerk and DoubleClick both have created APIs that allow BuySellAds to “plugin” to their system and schedule tasks. This ensures that we are working within the functionality of the ad server and are taking care of the diligence on our end to execute an ad purchase.

For DoubleClick for Publishers (DFP), this will create an Order titled “BSA Self-Serve Campaigns“. When you first make the connection to a zone (completing Step 7 and 8 in the tutorials) you won’t immediately see anything in your ad server. Only after we have sold an advertisement directly for you, will a line item or flight be created automatically.

  • Delivering: Indicates that the ad campaign is serving. In the example above, you are viewing an ad campaign that is scheduled to serve from August 26th to Sept 21st. BSA has served 1,400 impressions of the campaign. To view the total impressions in a campaign, head over to your Dashboard and view the Transaction History. The ID # of the Order is the last string of digits for the Transaction ID.
  • Ready: Campaigns that are connected and are scheduled, but are not actively serving. This could mean other ads units are being served at the moment for that inventory. If an advertiser has submitted multiple creative, the inactive ads will appear in Ready status until served.

Selecting each header will allow you to go further into the order to learn about the campaign.

For Adzerk, a flight will be created that is titled, “BSA Self-Serve Campaigns“. This can be found under campaigns, showing the dates of the campaigns and their status. Active, running campaigns will display a bright green “Healthy” status. The image below shows what a finished BSA campaign looks like; other ad partners would be listed below it.

An Adzerk flight will look like this: 

In Summary: BuySellAds is able to tap into the API from either ad server and schedule a campaign automatically. The ad campaigns are scheduled over a 30-day period and will rotate evenly with existing orders/campaigns.

How do I use Asynchronous Adsense Code for backfill?

We serve our ad code asynchronously, so our ad code never blocks a page load. We also serve backfill (i.e. the Adsense code) in an iframe, so there’s no benefit to using the async Adsense code instead of the normal Adsense code.

If you still want to try to use adsense async, please see Google’s page about altering their code here, and you may also be interested in viewing this message thread for further help.

Does your ad code work in HTTPS pages?

Yes – we support SSL / HTTPS. The ad code can be installed on these pages, and there is nothing additional that needs to be done for this to work.

Note: If you are a current publisher with ads running before this change in March 2015, and you are changing your site from HTTP to HTTPS, you will need to copy and paste the latest STEP 1 code into your site from the Ad Code page in your account.

The ad code throws an error on the page because we run a content security policy that stops inline JavaScript actions.

We recommend the following workaround:

  • Enable ‘unsafe-inline
  • Put it in an iframe with no CSP (or a less restrictive CSP that allows ‘unsafe-inline‘)

Cloudflare Issues

If you are using Cloudflare, you may experience problems with ad display after installing our ad code. If this happens, you can follow the instructions here, or you may need to turn off ‘auto-minify‘ in Cloudflare. 

Using the JavaScript callback for the Marketplace ad code

If you are using the Marketplace ad code directly on your site (the ad code with step 1 reference to http://s3.buysellads.com/ac/bsa.js we provide a callback function that you can use to detect whether or not an ad is being served.

Here’s an example:


One browser is displaying my BSA ads, but the other isn’t. Why is that?

Sometimes this is due to an ad blocker being turned on in your browser. Please check your browser settings to make sure that an ad blocker is not turned on and then try again.

If you are sure that your ad blocker is turned off, then it could also be that certain code surrounding your ad code is causing the div to be hidden in a particular browser. Browsers can render code in different ways, and some browsers are more sensitive than others. If there is an error in your code, or if a certain CSS property is being used, it may cause display issues in some browsers.

You can use the W3C Markup Validator to check your site for code errors. Sometimes correcting code errors can also correct any ad display issues.

If you need further assistance, please open a support ticket so we can help you resolve the issue.