AMP (Accelerated Mobile Pages)

AMP (https://www.ampproject.org/) is a JavaScript/HTML technology for rendering mobile pages faster, using special HTML tags (<amp-img> instead of <img>, etc). All ads should be loaded in <amp-ad> tags:

Description of the <amp-ad> element

There exists a couple of important restrictions on creatives running inside an <amp-ad> tag:

  • The creative will be shown inside an <iframe> on a different domain, this makes it impossible for the creative to access the AMP-page itself.
  • All creatives will be served over HTTPS, even if the AMP HTML page is served over HTTP. This means that no “http:” references can be used in e.g. [HTML] creatives.

Except of these restrictions, creatives will be allowed to do just about anything as normal. They will themselves not be part of the AMP document but instead be standalone normal HTML documents running inside iframes “sandboxes”.

Notice also that ads will be loaded more on-demand then on normal HTML pages. This will certainly give lower impression count for campaigns, especially for campaigns in Content Units further down your AMP pages.

Cxense Display integration

Supported parameters in the amp-ad tag

  • data-eas-domain - Required parameter, your ad server domain
  • data-eas-[parameter] - Any ad-request parameter, like 'cu'

Example

Basic call that corresponds to https://eas4.emediate.eu/eas?cu=12345

<amp-ad width=320 height=50
    type="eas"
    data-eas-domain="eas4.emediate.eu"
    data-eas-cu="12345">
</amp-ad>

With targeting parameters

<amp-ad width=320 height=50
    type="eas"
    data-eas-domain="eas4.emediate.eu"
    data-eas-cu="12345"
    data-eas-EASTsomename="somevalue"
    data-eas-kw1="somekeyword">
</amp-ad>

Configuration

For `data-eas-domain=<YourAdServerDomain>`, use your ad-server domain (e. g. eas3.emediate.se); If you're using a custom domain-name (like eas.somesite.com) you should NOT use that one unless you already have an SSL-certificate installed on our ad servers.

Any dimension campaigns

Campaigns using Any dimension and have other dimensions then the CU might or might not resize itself the campaign's dimensions.

This depends on if the AMP framework allows it. As a rule of thumb, top-banners that you immediately see won't resize correctly - while campaigns on CUs further down the page will work. The reason is to avoid “jumping” pages when ads are resized.

In-Screen Measurements (ISM) reporting

ISM impressions are counted as normal. But for performance-, etc, reasons there is one limitation when it comes to reporting:

The Duration: and Average duration columns will not be useful - as only 1 second is logged for each ISM impression. This means that while the counting of ISM impressions itself will be just as normal - the “duration” reporting numbers won't.

Cxense © 2012 | Support