adgeneration.md

layout	title	description	schain_supported	pbjs	pbs	pbs_app_supported	fpd_supported	biddercode	userIds	media_types	sidebarType
bidder	Ad Generation	Prebid Ad Generation Bidder Adaptor	true	true	false	false	true	adgeneration	all	native	1

Bid Params

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

Name	Scope	Description	Example	Type
id	required	adId	'1234'	string

First Party Data

In release 1.6.4 and later, publishers should use the ortb2 method of setting First Party Data. The following fields are supported:

• ortb2.site.content.data[]

If ad-generation.jp is specified for ortb2.site.content.data[].name and 546 is specified for ortb2.site.content.data[].ext.segtax, ortb2.site.content.data[].segment[].name and ortb2.site.content.data[].segment[].value can be any string value.

Example first party data that's available to all bidders and all adunits:

pbjs.setConfig({
    ortb2: {
        site: {
            content: {
                data: [{
                    name: "ad-generation.jp",
                    ext: {
                        segtax: 546
                    },
                    segment: [
                        { name: "news_category", value: "Sports_Sumo" },// name and value must be string types
                        { name: "local_gourmet", value: "sushi" },
                        { name: "location", value: "tokyo" }
                    ]
                }]
            }
        },
    }
});