Back to Bidders

Ampliffy

Features

Bidder Code ampliffy Prebid.org Member no
Media Types display, video, native TCF-EU Support yes
User IDs none USP/CCPA Support check with bidder
Supply Chain Support check with bidder COPPA Support check with bidder
Demand Chain Support check with bidder GPP Support check with bidder
Supports Deals check with bidder Prebid.js Adapter yes
IAB GVL ID 1258 Prebid Server Adapter no
Floors Module Support check with bidder First Party Data Support check with bidder
Multi Format Support will-bid-on-one ORTB Blocking Support check with bidder
Safeframes OK yes Privacy Sandbox check with bidder

Table of contents

Introduction

Publishers can use Prebid.js to call Ampliffy through our client-side adapter: Prebid.js calls ampliffy directly from the browser using our client-side adapter. For configuration instructions, see the below on this page.

Example

Supported media types

The following table lists the media types that Ampliffy supports.

Type
banner
video
native

Modules to include in your build process

If you are building the JS binary on your own from source code, follow the instructions in Prebid.js project README. You will need to include the ampliffyBidAdapter. To show video ads with Google Ad Manager, you need to include the dfpAdServerVideo module. We highly recommend adding the gptPreAuction module as well, which improves a DSP’s ability to bid accurately on your supply. The following is an example build command that include these modules:
gulp build --modules=ampliffyBidAdapter,dfpAdServerVideo,gptPreAuction

If you are using a JSON file to specify modules, add ampliffyBidAdapter and dfpAdServerVideo to the modules array as follows:

[
    "ampliffyBidAdapter",
    "dfpAdServerVideo",
    "gptPreAuction"
]

Bid request parameters

You must include these parameters at the bidder level.

Name Scope Type Description
placementId Required String An Ampliffy-specific identifier that is associated with this ad unit. This is similar to a placement ID or an ad unit ID that some other modules have. For example, '3723', '6482', '3639'
format Required String specify ‘display’ for this kind of inventory`
server Optional String An Ampliffy-specific identifier that is associated with this ad unit`

Video

You must include these parameters at the bidder level.

Name Scope Type Description
placementId Required String An Ampliffy-specific identifier that is associated with this ad unit. It will be associated with the single size, if the size is provided. This is similar to a placement ID or an ad unit ID that some other modules have. For example, '3723', '6482', '3639'
Note: You can re-use the existing siteId within the same flex position or video size, if the video adapts to the containing <div> element.
format Required String specify ‘video’ for this kind of inventory`
server Optional String An Ampliffy-specific identifier that is associated with this ad unit`

Examples

Video (instream):

var adUnits = [{
    code: 'video1',
    mediaTypes: {
        video: {
            playerSize: [[640, 480]],
            context: 'instream'
        },
    },
    bids: [{
        bidder: 'ampliffy',
        params: {
            server: 'bidder.ampliffy.com',
            placementId: '1213213/example/vrutal_/',
            format: 'video'
        }
    }]
}];

"Send All Bids" Ad Server Keys

These are the bidder-specific keys that would be targeted within GAM in a Send-All-Bids scenario. GAM truncates keys to 20 characters.
hb_pb_ampliffy hb_bidder_ampliffy hb_adid_ampliffy
hb_size_ampliffy hb_source_ampliffy hb_format_ampliffy
hb_cache_host_amplif hb_cache_id_ampliffy hb_uuid_ampliffy
hb_cache_path_amplif hb_deal_ampliffy

Back to Bidders