Back to Bidders

Dailymotion

Features

Registration

To use the adapter with any non-test request, you first need to ask an API key from Dailymotion. Please contact us through DailymotionPrebid.js@dailymotion.com .

This API key will ensure proper identification of your inventory and allow you to get real bids.

Configuration options

Before calling this adapter, you need to at least set a video adUnit in an instream context and the API key in the bid parameters:

const adUnits = [
  {
    bids: [{
      bidder: 'dailymotion',
      params: {
        apiKey: 'fake_api_key'
      },
    }],
    code: 'test-ad-unit',
    mediaTypes: {
      video: {
        context: 'instream',
      },
    },
  }
];

apiKey is your publisher API key. For testing purpose, you can use “dailymotion-testing”.

Test Parameters

By setting the following bid parameters, you’ll get a constant response to any request, to validate your adapter integration:

const adUnits = [
  {
    bids: [{
      bidder: 'dailymotion',
      params: {
        apiKey: 'dailymotion-testing'
      },
    }],
    code: 'test-ad-unit',
    mediaTypes: {
      video: {
        context: 'instream',
      },
    },
  }
];

Please note that failing to set these will result in the adapter not bidding at all.

Sample video AdUnit

To allow better targeting, you should provide as much context about the video as possible. There are three ways of doing this depending on if you’re using Dailymotion player or a third party one.

If you are using the Dailymotion player, you should only provide the video xid in your ad unit, example:

const adUnits = [
  {
    bids: [{
      bidder: 'dailymotion',
      params: {
        apiKey: 'dailymotion-testing'
      }
    }],
    code: 'test-ad-unit',
    mediaTypes: {
      video: {
        api: [2, 7],
        context: 'instream',
        startdelay: 0,
        w: 1280,
        h: 720,
        xid: 'x123456'     // Dailymotion infrastructure unique video ID
      },
    }
  }
];

This will automatically fetch the most up-to-date information about the video. If you provide any other metadata in addition to the xid, they will be ignored.

If you are using a third party video player, you should not provide any xid and instead fill the following members:

const adUnits = [
  {
    bids: [{
      bidder: 'dailymotion',
      params: {
        apiKey: 'dailymotion-testing',
        video: {
          description: 'overriden video description'
        }
      }
    }],
    code: 'test-ad-unit',
    mediaTypes: {
      video: {
        api: [2, 7],
        context: 'instream',
        description: 'this is a video description',
        duration: 556,
        iabcat1: ['IAB-2'],
        iabcat2: ['6', '17'],
        id: '54321',
        lang: 'FR',
        livestream: 0,
        private: false,
        startdelay: 0,
        tags: 'tag_1,tag_2,tag_3',
        title: 'test video',
        topics: 'topic_1, topic_2',
        w: 1280,
        h: 720,
      },
    }
  }
];

Each of the following video metadata fields can be added in mediaTypes.video or bids.params.video. If a field exists in both places, it will be overridden by bids.params.video.

• description - Video description
• duration - Video duration in seconds
• iabcat1 - List of IAB category IDs from the 1.0 taxonomy
• iabcat2 - List of IAB category IDs from the 2.0 taxonomy and above
• id - Video unique ID in host video infrastructure
• lang - ISO 639-1 code for main language used in the video
• livestream - 0 = not live, 1 = content is live
• private - True if video is not publicly available
• tags - Tags for the video, comma separated
• title - Video title
• topics - Main topics for the video, comma separated
• xid - Dailymotion video identifier (only applicable if using the Dailymotion player)

If you already specify First-Party data through the ortb2 object when calling pbjs.requestBids(requestObj), we will fallback to those values when possible. See the mapping below.

"Send All Bids" Ad Server Keys

Back to Bidders