diff --git a/dev-docs/bidders/adgeneration.md b/dev-docs/bidders/adgeneration.md index 12e9914304..34e603082d 100644 --- a/dev-docs/bidders/adgeneration.md +++ b/dev-docs/bidders/adgeneration.md @@ -27,8 +27,12 @@ In release 1.6.4 and later, publishers should use the `ortb2` method of setting * 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. +If `ad-generation.jp` is specified for ortb2.site.content.data[].name and `546` is specified for ortb2.site.content.data[].ext.segtax, the segment array objects are processed as follows: + +* segment[].id: Required. Must be a string. +* segment[].value: Optional. Must be a string. +* If only id is provided (e.g., { id: "1001" } or { id: "sports" }), the id field itself is treated as the segment value (e.g., an attribute or tag). +* If both id and value are provided (e.g., { id: "news_category", value: "Sports_Sumo" }), the value is read as the value associated with the id (key). Example first party data that's available to all bidders and all adunits: @@ -43,9 +47,13 @@ pbjs.setConfig({ 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" } + // Processed as a single segment value (attribute or tag) + { id: "1001" }, + { id: "sports" }, + // Processed as Key-Value pairs + { id: "news_category", value: "Sports_Sumo" }, + { id: "local_gourmet", value: "sushi" }, + { id: "location", value: "tokyo" }, ] }] }