Skip to content

Latest commit

 

History

History
84 lines (70 loc) · 1.76 KB

yieldpro.md

File metadata and controls

84 lines (70 loc) · 1.76 KB
Raw

YieldPro

Examples

Single ad

<amp-ad
  width="728"
  height="90"
  type="yieldpro"
  data-pubnetwork="12c6fc06"
  data-section-id="100"
  data-slot="107"
>
</amp-ad>

Multi instance ads

<amp-ad
  width="250"
  height="250"
  type="yieldpro"
  data-pubnetwork="12c6fc06"
  data-section-id="475"
  data-slot="650"
  data-instance="1"
>
</amp-ad>
<amp-ad
  width="250"
  height="250"
  type="yieldpro"
  data-pubnetwork="12c6fc06"
  data-section-id="475"
  data-slot="650"
  data-instance="2"
>
</amp-ad>

Using custom params and custom ad server url

<amp-ad
  width="728"
  height="90"
  type="yieldpro"
  data-pubnetwork="12c6fc06"
  data-section-id="100"
  data-slot="107"
  data-custom='{"my_custom_param":"my_custom_value"}'
  data-ad-server-url="//creative.yieldpro.eu/ad"
>
</amp-ad>

Configuration

For details on the configuration semantics, please contact the ad network or refer to their documentation.

Required parameters

  • sectionId: ID of this section in ad server.
  • slot: ID of ad slot in ad server.
  • pubnetwork: ID of the publisher that in ad server.

Optional parameters

  • instance: ID of section instance in case we multiple times used the same section on the same page. Can contain only letters and numbers.Strictly required to use the same section multiple times per page.

  • click3rd: 3rd party click watcher.

  • adServerUrl

  • cacheSafe

  • pageIdModifier

  • custom: Custom targeting properties. You may use 3 types for its properties: {String}, {Number} and {Array}. The following array usage example translates into: arrayKey=value1&arrayKey=1&stringKey=stringValue...

    {
    arrayKey: [ "value1", 1 ],
    stringKey: 'stringValue'
}