All Collections
Inventory & Ad Formats
Available Ad Formats
Display Banner Ads, Ad Tags and Supported Sizes
Display Banner Ads, Ad Tags and Supported Sizes
Updated over a week ago

Display Campaign Setup

If you wish to advertise with Display creatives (graphic banners), you will need to set up a new Display Campaign.

1. Navigate to your Account level and click on the + Campaign button to add a new Campaign.

2. Within the Campaign setup dialogue window, select Display under the Campaign Type drop-down menu.

3. The rest of the Campaign settings are the same as for other types of Campaigns. You can find detailed instructions for Campaign settings here.

4. To turn your Campaign on, you need to add at least one ad group. You can find detailed instructions for ad group settings here.

5. Use the Creative Library to upload assets for Display ads. You can decide whether to upload Display banners or Display Ad Tags. Visuals are supported in png, jpeg, and GIF file formats. HTML5 and rich media ads are supported through Ad Tags serving.

Banner Creative Upload

1. Navigate to Creative Library

2. Add a new Display creative by clicking on the + Add new creative button.

3. Fill out the form.

  • Ad Name - custom name intended for reporting purposes

  • URL - link to the landing page you want to promote

  • Ad Type - select Display banner

  • Upload image file - you can upload static jpeg or png file formats or dynamic GIF format (GIF uploads are limited to 30 MB). Make sure that your image file complies with one of the supported banner sizes

  • Display URL - short URL of your landing page that will be displayed when hovering over the banner

  • Tags - custom label to better organize creatives in the library

  • Trackers - option to add additional trackers to track banner impressions

Ad Tag Creative Upload

1. Repeat steps 1 and 2 from the previous section.

2. Fill out the form.

  • Ad Name - a custom name for reporting purposes

  • URL - link to the landing page you want to promote

  • Ad Type - select Display Ad Tag

  • Ad Size - select one of the supported ad sizes

  • Ad Tag - paste HTML or JS code

  • Display URL - short URL of your landing page that will be displayed when hovering over the banner

  • Tags - custom label to better organize creatives in the library

Ad Tag Troubleshoot Tool

In Zemanta, you can now troubleshoot different issues when uploading and adding an Ad Tag Display ad, using the Troubleshoot tool. You can access the Troubleshoot tool by heading to your Creative Library and clicking on your existing creative or by adding a new creative.

The Troubleshoot tool allows you to quickly recheck and fix all necessary Ad Tag parameters (including redirects) that might adversely affect the success of your creative.

In the background, the Troubleshoot tool simulates clicking on your Ad Tag creative and looks for any error in the redirect chain. It also checks if your Ad Tag is properly attributed and tracked by Zemanta.

IMPORTANT: If the Troubleshoot tool shows an error and you are in doubt, please reach out to a Zemanta representative. When the Troubleshoot tool indicates that everything is correct, your Ad Tag is working properly.

Ad Tags Troubleshooting Scenarios

1. No issues were detected by the Troubleshoot tool. Your Ad Tag contains all tracking parameters needed and the redirects are functioning properly. Congrats!

2. Troubleshoot tool has detected that the Ad Tag is missing the tracking parameters in the final URL or it has detected an error in the Ad Tag redirect chain.

3. Troubleshoot tool has detected that the Ad Tag is missing tracking parameters in the final URL. Please make sure you add the correct tracking parameters.

4. Troubleshoot tool has detected that the Ad Tag does not contain any redirects. Recheck the Ad Tag.

5. Troubleshoot tool has detected an absence of a landing page. The colour of the specific listing will be red, indicating an issue. Please recheck the Ad Tag.

Third-Party Ad Tags Workarounds

When you use third-party services to generate Ad Tags, you must make sure that the Ad Tag code (HTML or JavaScript) is compiled in a way that enables Zemanta to correctly serve and render the Display ad in the publisher's placement and to track the engaged online user.

Typically, you should include the click_url and cachebuster macros in your Ad Tag.

  • click_url enables Zemanta to track clicks and is crucial for CTR prediction and CPC optimization engines

  • cachebuster prevents ads from being cached on the browser side and guarantees that the ad will display correctly to the online user

Adform

If you use the Adform service in order to generate Ad Tags, you must add the following macros: click_url, click_url_enc, gdpr (optional)

  • include gdpr and click_ulr_enc macros within the <script> part of the code

  • include the click_url in the <noscript> part of the code

Example:

Original Ad Tag:

<script language="javascript" src="<a href="https://track.adform.net/adfscript/?bn=12345678">https://track.adform.net/adfscript/?bn=12345678</a>"></script><noscript> <a href="{CLICK_URL}"https://track.adform.net/C/?bn=12345678;C=0">https://track.adform.net/C/?bn=12345678;C=0</a>" target="_blank"> <img src="<a href="https://track.adform.net/adfserve/?bn=12345678;srctype=4;ord=%5Btimestamp%5D">https://track.adform.net/adfserve/?bn=12345678;srctype=4;ord=[timestamp]</a>" border="0" width="970" height="90" alt=""/> </a> </noscript>

Resolved Ad Tag:

<script language="javascript" src="<a href="https://track.adform.net/adfscript/?bn=12345678">https://track.adform.net/adfscript/?bn=12345678</a>;gdpr={GDPR};gdpr_consent={GDPR_CONSENT_50};click={CLICK_URL_ENC}"></script><noscript> <a href="{CLICK_URL}<a href="https://track.adform.net/C/?bn=12345678;C=0">https://track.adform.net/C/?bn=12345678;C=0</a>" target="_blank"> <img src="<a href="https://track.adform.net/adfserve/?bn=12345678;srctype=4;ord=%5Btimestamp">https://track.adform.net/adfserve/?bn=12345678;srctype=4;ord=[timestamp]” border="0" width="970" height="90" alt=""/> </a> </noscript>

DCM

If you are using the Campaign Manager 360 insertion tags, you must include the data-dcm-tracker parameter and set the value to the macro ${click_url}.

Use the script rendering mode and not iFrame to avoid reporting discrepancies. Set the data-dcm-rendering-mode to script (data-dcm-rendering-mode=‘script’).

Example:

Resolved Ad Tag:

<ins class='dcmads' style='display:inline-block;width:300px;height:250px' data-dcm-placement='N571601.2165303/B26559109.315468392' data-dcm-rendering-mode='script' data-dcm-click-tracker='{CLICK_URL}' data-dcm-https-only data-dcm-gdpr-applies='gdpr={GDPR}' data-dcm-gdpr-consent='gdpr_consent={GDPR_CONSENT_755}' data-dcm-addtl-consent='addtl_consent={ADDTL_CONSENT}' data-dcm-ltd='false' data-dcm-resettable-device-id='' data-dcm-app-id=''> <script src='<a href="https://fw.adsafeprotected.com/rjss/www.googletagservices.com/832115/57397613/dcm/dcmads.js">https://fw.adsafeprotected.com/rjss/www.googletagservices.com/832115/57397613/dcm/dcmads.js</a>'></script> </ins>

Learn more about DCM Ad Tags here.

Sizmek

If you are relying on Sizmek for creating Ad Tags, you should include the click_url and cachebuster macros in your Ad Tag.

Example:

Original Ad Tag:

<script src="https://bs.serving-sys.com/Serving/adServer.bs?c=28&cn=display&pli=12345678910&gdpr=${GDPR}&gdpr_consent=${GDPR_CONSENT_68}&w=300&h=250&ord=[timestamp]&LineID=$$$$$$z1{contentAdId}{mediaSource}__{publisher}1z$$$$$$&z=10000"></script> <noscript> <a href="https://bs.serving-sys.com/Serving/adServer.bs?cn=brd&pli=1077679785&gdpr=${GDPR}&gdpr_consent=${GDPR_CONSENT_68}&Page=&Pos=12345678910&LineID=$$$$$$z1{contentAdId}{mediaSource}__{publisher}1z$$$$$$" target="_blank"> <img src="https://bs.serving-sys.com/Serving/adServer.bs?c=8&cn=display&pli=12345678910&gdpr=${GDPR}&gdpr_consent=${GDPR_CONSENT_68}&Page=&Pos=541928491&LineID=$$$$$$z1{contentAdId}{mediaSource}__{publisher}1z$$$$$$" border=0 width=300 height=250></a> </noscript>

Resolved Ad Tag:

<script src="https://bs.serving-sys.com/Serving/adServer.bs?c=28&cn=display&pli=12345678910&gdpr=${GDPR}&gdpr_consent=${GDPR_CONSENT_68}&w=300&h=250&ord={CACHEBUSTER}&ncu={CLICK_URL_ENC}&ucm=true&LineID=$$$$$$z1{contentAdId}{mediaSource}__{publisher}1z$$$$$$&z=10000"></script> <noscript> <a href="https://bs.serving-sys.com/Serving/adServer.bs?cn=brd&pli=12345678910&gdpr={GDPR}&gdpr_consent={GDPR_CONSENT_68}&Page=&Pos=12345678910&LineID=$$$$$$z1{contentAdId}{mediaSource}__{publisher}1z$$$$$$" target="_blank"> <img src="{CLICK_URL}https://bs.serving-sys.com/Serving/adServer.bs?c=8&cn=display&pli=12345678910&gdpr=${GDPR}&gdpr_consent=${GDPR_CONSENT_68}&Page=&Pos=12345678910&LineID=$$$$$$z1{contentAdId}{mediaSource}__{publisher}1z$$$$$$" border=0 width=300 height=250></a> </noscript>

Celtra

If you are using a Celtra Ad Tag and it contains the “UseClickAsDestination” parameter then the clickUrl is used as a landing page. In order to configure the clickUrl properly, please add the CLICK_DESTINATION macro.

Original Ad Tag:

<div class="celtra-ad-v3"> <!-- eas.e3ZpZGVvX3N0YXJ0fQ%3D%3D = raw {video_start} --> <!-- eas.e3ZpZGVvX2ZpcnN0X3F1YXJ0aWxlfQ%3D%3D = raw {video_first_quartile} --> <!-- eas.e3ZpZGVvX21pZHBvaW50fQ%3D%3D = raw {video_midpoint} --> <!-- eas.e3ZpZGVvX3RoaXJkX3F1YXJ0aWxlfQ%3D%3D = raw {video_third_quartile} --> <!-- eas.e3ZpZGVvX2NvbXBsZXRlfQ%3D%3D = raw {video_complete} --> <img src="data:image/png,celtra" style="display: none" onerror=" (function(img) { var params = {'clickUrl':'{CLICK_URL}','widthBreakpoint':'','expandDirection':'undefined','preferredClickThroughWindow':'new','clickEvent':'advertiser','useClickAsDestination':'1','externalAdServer':'Zemanta','tagVersion':'html-standard-7'}; [].slice.apply(img.parentNode.childNodes).forEach(function(n) { var decfs = { urldecode: decodeURIComponent, htmldecode: function(v) { var d = document.createElement('div'); d.innerHTML = v; return d.textContent; }, eval: function(v) { return eval(v); }, raw: function(v) { return v; } }; var m; if (n.nodeType == 8 && (m = n.textContent.match(/^\s+([\w%.]+)(\[.+\])?\s+=\s+(\w+)\s+(.*)$/i))) { try { params[m[1]+(m[2] || '')] = decfs[m[3]](m[4].replace(/^\s+|\s+$/g, '')); } catch (e) {} } }); var req = document.createElement('script'); req.id = params.scriptId = 'celtra-script-' + (window.celtraScriptIndex = (window.celtraScriptIndex||0)+1); params.clientTimestamp = new Date/1000; params.clientTimeZoneOffsetInMinutes = new Date().getTimezoneOffset(); params.hostPageLoadId=window.celtraHostPageLoadId=window.celtraHostPageLoadId||(Math.random()+'').slice(2); var qs = ''; for (var k in params) { qs += '&' + encodeURIComponent(k) + '=' + encodeURIComponent(params[k]); } var src = 'https://ads.celtra.com/2c29f1a9/web.js?' + qs; req.src = src; img.parentNode.insertBefore(req, img.nextSibling); })(this); "> </div> <script src="https://z.moatads.com/zemantadisplay585179817718/moatad.js#moatClientLevel1=ClubMed_FR_ND&moatClientLevel2={publisher}&moatClientLevel3={widget_ID}&moatClientLevel4={ad_id}"></script>

Resolved Ad Tag:

<div class="celtra-ad-v3"> <!-- eas.e3ZpZGVvX3N0YXJ0fQ%3D%3D = raw {video_start} --> <!-- eas.e3ZpZGVvX2ZpcnN0X3F1YXJ0aWxlfQ%3D%3D = raw {video_first_quartile} --> <!-- eas.e3ZpZGVvX21pZHBvaW50fQ%3D%3D = raw {video_midpoint} --> <!-- eas.e3ZpZGVvX3RoaXJkX3F1YXJ0aWxlfQ%3D%3D = raw {video_third_quartile} --> <!-- eas.e3ZpZGVvX2NvbXBsZXRlfQ%3D%3D = raw {video_complete} --> <img src="data:image/png,celtra" style="display: none" onerror=" (function(img) { var params = {'clickUrl':'{CLICK_DESTINATION}','widthBreakpoint':'','expandDirection':'undefined','preferredClickThroughWindow':'new','clickEvent':'advertiser','useClickAsDestination':'1','externalAdServer':'Zemanta','tagVersion':'html-standard-7'}; [].slice.apply(img.parentNode.childNodes).forEach(function(n) { var decfs = { urldecode: decodeURIComponent, htmldecode: function(v) { var d = document.createElement('div'); d.innerHTML = v; return d.textContent; }, eval: function(v) { return eval(v); }, raw: function(v) { return v; } }; var m; if (n.nodeType == 8 && (m = n.textContent.match(/^\s+([\w%.]+)(\[.+\])?\s+=\s+(\w+)\s+(.*)$/i))) { try { params[m[1]+(m[2] || '')] = decfs[m[3]](m[4].replace(/^\s+|\s+$/g, '')); } catch (e) {} } }); var req = document.createElement('script'); req.id = params.scriptId = 'celtra-script-' + (window.celtraScriptIndex = (window.celtraScriptIndex||0)+1); params.clientTimestamp = new Date/1000; params.clientTimeZoneOffsetInMinutes = new Date().getTimezoneOffset(); params.hostPageLoadId=window.celtraHostPageLoadId=window.celtraHostPageLoadId||(Math.random()+'').slice(2); var qs = ''; for (var k in params) { qs += '&' + encodeURIComponent(k) + '=' + encodeURIComponent(params[k]); } var src = 'https://ads.celtra.com/2c29f1a9/web.js?' + qs; req.src = src; img.parentNode.insertBefore(req, img.nextSibling); })(this); "> </div> <script src="https://z.moatads.com/zemantadisplay585179817718/moatad.js#moatClientLevel1=ClubMed_FR_ND&moatClientLevel2={publisher}&moatClientLevel3={widget_ID}&moatClientLevel4={ad_id}"></script>

Please note: when you upload the Ad Tag in Zemanta remember to enter only the Landing Page URL without UTMs and Click ID in the "URL" field instead of the 3rd party Click Tracker, if you have it. Do not insert 3rd party Click Tracker here.

Supported Display Banner Sizes

To successfully serve a Display ad to the online user within the available placement, you need to include creatives in Display Campaigns with the supported banner sizes below, regardless of the ad type (image or Ad Tag).

We recommend adding a variety of different ad sizes to your Display ad groups to access a broader pool of placements on the open web.

Horizontal:

  • 970x250 billboard

  • 970x90 large leaderboard

  • 728x90 leaderboard

  • 468x60 banner

  • 300x100, 320x100 large mobile banner

  • 300x50, 320x50 mobile banner

  • 500x250, 800x250 large banner

Square:

  • 125x125 button

  • 180x150 small rectangle

  • 200x200 small square

  • 250x250 square

  • 300x165 inline rectangle

  • 300x250 rectangle

  • 320x480 rectangle

  • 336x280 large rectangle

  • 480x320 large rectangle - mobile landscape (phone)

  • 1024x768 large rectangle - mobile landscape (tablet)

Vertical:

  • 300x600, 320x480 half page

  • 120x600, 160x600 skyscraper

  • 300x1050 portrait

  • 768x1024 large portrait

Did this answer your question?