Skip to content

Latest commit

 

History

History
81 lines (68 loc) · 2.02 KB

amx-server.md

File metadata and controls

81 lines (68 loc) · 2.02 KB
layout title description hide schain_supported tcfeu_supported usp_supported coppa_supported userIds biddercode safeframes_ok media_types pbjs pbs pbs_app_supported fpd_supported multiformat_supported ortb_blocking_supported gpp_supported gvl_id sidebarType
bidder
AMX RTB
AMX RTB Bid Adapter
true
true
true
true
true
all
amx
true
banner, video, native
false
true
true
true
true
true
true
737
1

Bid Params

{: .table .table-bordered .table-striped }

Name Scope Description Example Type
tagId required Tag ID 'cHJlYmlkLm9yZw' string
testMode optional Activate 100% fill ads true boolean
adUnitId optional Ad Unit ID used in reporting. Will default to bid.adUnitCode 'sticky_banner' string

Test Parameters

To enable 100% fill test ads, you can use the following params:

{
  testMode: true,
  tagId: "cHJlYmlkLm9yZw"
}

This will produce a bid at $10 with a test creative.

Note that the tagId is case-sensitive. Do not use cHJlYmlkLm9yZw in production environments: this ID is for testing only.

First Party Data

From Prebid.js >= 4.30, publishers can use the ortb2 configuration parameter to provide First Party Data. We accept all standard OpenRTB fields for both:

  • ortb2.site
  • ortb2.user

Note that all fields are optional. For contextual data (e.g. categories), standard IAB taxonomies are supported. We do not support passing first party data via bid parameters.

Example - Setting ortb2.site and ortb2.user fields

pbjs.setBidderConfig({
  bidders: ["amx"],
  config: {
    ortb2: {
      site: {
        keywords: "kw1,kw2",
        cat: ["IAB2"],
        sectioncat: ["IAB2-1"],
        pagecat: ["IAB2-22"],
        content: {
          context: 5,
        },
      },
      user: {
        yob: 1981,
        keywords: "kw3",
      },
    },
  },
});