Publisher Ad Server – Best Practices

Creating a Test Page

What makes a good test page? When you are making your test page for the Sortable team, review it to ensure it has the following:

  • The root domain of the test page matches the domain you are onboarding. If the testing domain does not match, give Sortable the testing domain so we can whitelist it in our system.
  • Replace all programmatic ads with Sortable's and place the ads in the same positions you plan on using with Sortable on the whole test page. 
  • Remove your previous provider's code from the test page.
  • Use a test page with the same code as a regular page on your site, using all the same plugins and third-party scripts (except your previous provider's) so we can check for code conflicts.
  • If needed, apply any of the required workarounds from the Conflicting Code section (below) to your test page.
  • Using the search function in your browser's inspector, double-check that you made all the required code replacements.
  • We prefer that your test page does not have live traffic going to the page. This allows us the opportunity to test everything before you set it to live. If a live page is used, select a low traffic page.
  • Send Sortable your testing URL as soon as it is ready. It may take our team a few days to test depending on the complexity of your code.

Suggested Sizes

We suggest using multi-sized units whenever possible to increase competition, CPMs, and revenue. 

  • Use sizeMapping to request multiple sizes based on the device width and height. 
  • The order of the sizes is very important. We suggest placing the size that has the highest performance first, as some bidders only support single size bidding. 
  • The 1x1 and 1x2 sizes are used for specialized demand and should not be at the beginning of your list; we suggest adding these at the end.

Here are the suggested sizes for each ad type:

Header Units

These units should appear at the top of the page on desktop and tablet, and at least halfway down the first viewport on mobile.

Suggested sizes:

  • Desktop: 970x250, 970x90, 728x90, 728x15, 468x60, 1x1, 1x2
  • Tablet: 728x90, 728x15, 468x60, 300x250, 336x280, 320x50, 300x50, 320x100, 1x1, 1x2
  • Mobile: 300x250, 336x280, 320x50, 300x50, 320x100, 1x1, 1x2

Anchors

These units should appear at the bottom of your site pages on all device types, they should be fixed to the bottom of the screen, and must include a close button.

Suggested sizes:

  • Desktop: 970x90, 728x90, 468x60, 1x1, 1x2
  • Tablet: 728x90, 468x60, 320x50, 300x50, 1x1, 1x2
  • Mobile: 320x50, 300x50, 1x1, 1x2

Side Rails/Side Bar

These units should appear in your side rails on desktop and larger tablets. 

On mobile, if your side rails appear, remove the ads or lazy load them. They often appear below the site content and would have very low viewability.

Suggested sizes:

  • Desktop: 300x600, 300x250, 160x600, 120x600, 336x280, 1x1, 1x2
  • Tablet: 300x600, 300x250, 160x600, 120x600, 336x280, 1x1, 1x2; if the width of the sidebar is smaller on tablet, adjust your size list based on what width fits.
  • Mobile: Either use lazy load or do not display the ads.

In-article/In-content

These units should appear inside the content of your page.

Suggested sizes:

  • Desktop: 970x250, 970x90, 728x90, 728x15, 468x60, 300x250, 320x50, 1x1, 1x2
  • Tablet: 728x90, 728x15, 468x60, 300x250, 320x50, 1x1, 1x2
  • Mobile: 300x250, 336x280, 320x50, 300x50, 320x100, 1x1, 1x2

Conflicting Code

See the list below for known code conflicts that can be solved with a workaround. 

For a list of code conflicts that do not have a workaround, see the list in the introduction of Publisher Ad Server – Integration Example.

WhatIssue it causesHow to work around the issue
TealiumAd latencySortable will need to see this on a test page to see if we can provide guidance.
RebelMouse  CMSThey use the same "ad-tag" class that Sortable uses. This conflicts with our code as we try to insert an ad into that div.No ad widgets should be used on a RebelMouse site using Sortable.
Cloudflare Rocket LoaderRocket loader caches our JavaScript causing your site to have outdated scripts.Add data-cfasync="false" to all script tags with Sortable's code.

Example:
<script data-cfasync="false" src="//tags-cdn.deployads.com/a/snapsort.com.js" async ></script>
W3 Total CacheW3 Total Cache caches our JavaScript causing your site to have outdated scripts.
  1. In WordPress, go to Performance > Minify > Advanced
  2. Enter the URL to your Sortable JavaScript file into the "Never minify the following JS files" where <SITE_NAME> is your Sortable JavaScript file name:
    tags-cdn.deployads.com/a/<SITE_NAME>.js
  3. Select Save all settings. If you already added the JavaScript file before doing this, Save Settings and Purge Caches.
AutoptimizeAutoptimize caches our JavaScript causing your site to have outdated scripts.Add <!--noptimize--> around all script tags with Sortable's code.

Example:
<!--noptimize--><script src="//tags-cdn.deployads.com/a/snapsort.com.js" async ></script><!--/noptimize-->
Theia Post SliderDefault settings for this theme in WordPress automatically refresh ads. Since these refresh calls are not using Sortable's version of refresh, we are not notified when the refresh occurs.On the Advanced tab of the Theia Post Slider plugin, uncheck the box next to Refresh ads when navigating to another side to disable it (in the Ad behavior section).
Confiant DFP WrapperWe don't support integrating Confiant through a DFP wrapper.Speak to your Sortable representative for other options.

For industry insights and information about our product offerings, check out our blog!

Want to see our products in action? For a demo, fill out a form here.