Ad Generation
Features
| Bidder Code | adgeneration | Prebid.org Member | no | 
|---|---|---|---|
| Prebid.js Adapter | yes | Prebid Server Adapter | no | 
| Media Types | display, native | Multi Format Support | check with bidder | 
| TCF-EU Support | no | IAB GVL ID | check with bidder | 
| GPP Support | check with bidder | DSA Support | check with bidder | 
| USP/CCPA Support | check with bidder | COPPA Support | check with bidder | 
| Supply Chain Support | yes | Demand Chain Support | check with bidder | 
| Safeframes OK | check with bidder | Supports Deals | check with bidder | 
| Floors Module Support | check with bidder | First Party Data Support | yes | 
| Endpoint Compression | check with bidder | ORTB Blocking Support | check with bidder | 
| User IDs | all | Privacy Sandbox | check with bidder | 
Bid Params
| 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" }
                    ]
                }]
            }
        },
    }
});
"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_adgeneration | hb_bidder_adgenerati | hb_adid_adgeneration | 
| hb_size_adgeneration | hb_source_adgenerati | hb_format_adgenerati | 
| hb_cache_host_adgene | hb_cache_id_adgenera | hb_uuid_adgeneration | 
| hb_cache_path_adgene | hb_deal_adgeneration |