From 53251c1b31caa318af9a6f3f99fb64843696df71 Mon Sep 17 00:00:00 2001 From: ss-toshihide-tajima Date: Wed, 22 Oct 2025 14:46:03 +0900 Subject: [PATCH 1/2] AdGeneration: Align segment parameter with OpenRTB spec This commit updates the AdGeneration bidder documentation to reflect a new specification for processing First Party Data segments (ortb2.site.content.data[].segment). The updated specification defines two distinct behaviors: 1. If only `segment[].id` is provided (e.g., `{ id: "1001" }`), the 'id' is treated as a pre-arranged classification code. 2. If both `segment[].id` and `segment[].value` are provided (e.g., `{ id: "news", value: "sports" }`), the 'value' is read as the value for the 'id' key. The documentation example has been updated to demonstrate both use cases. --- dev-docs/bidders/adgeneration.md | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/dev-docs/bidders/adgeneration.md b/dev-docs/bidders/adgeneration.md index 12e9914304..8745bfd15d 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" }), the id is treated as a pre-arranged classification code agreed upon with the publisher. +* 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,12 @@ 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" } + // Only id (required, string) is provided; treated as a classification code + { id: "1001" } + // Both id (required, string) and value (optional, string) are provided + { id: "news_category", value: "Sports_Sumo" }, + { id: "local_gourmet", value: "sushi" }, + { id: "location", value: "tokyo" }, ] }] } From b422dc614e96dd5a75e3cbb3fcb7f01065a088e8 Mon Sep 17 00:00:00 2001 From: ss-toshihide-tajima Date: Wed, 22 Oct 2025 18:19:21 +0900 Subject: [PATCH 2/2] Broaden definition for id-only FPD segments --- dev-docs/bidders/adgeneration.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/dev-docs/bidders/adgeneration.md b/dev-docs/bidders/adgeneration.md index 8745bfd15d..34e603082d 100644 --- a/dev-docs/bidders/adgeneration.md +++ b/dev-docs/bidders/adgeneration.md @@ -31,7 +31,7 @@ If `ad-generation.jp` is specified for ortb2.site.content.data[].name and `546` * segment[].id: Required. Must be a string. * segment[].value: Optional. Must be a string. -* If only id is provided (e.g., { id: "1001" }), the id is treated as a pre-arranged classification code agreed upon with the publisher. +* 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: @@ -47,9 +47,10 @@ pbjs.setConfig({ segtax: 546 }, segment: [ - // Only id (required, string) is provided; treated as a classification code - { id: "1001" } - // Both id (required, string) and value (optional, string) are provided + // 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" },