-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenRTB 2.6-202409 #103
OpenRTB 2.6-202409 #103
Conversation
added new attributes and appendix
round 2
grrrrrrrr
json examples to signal different id bridging scenarios
addressing comments for 2.x from PSCCG
Updated per CR from PSCCG
comment resolution
Fixed JSON examples
link to list: id match methods
2.6-202405 ID Bridging attributes, implementation guidance, Appendix C: Cookie Syncing
Link to Appendix C in buyeruid attribute
In example 4, and 5, the So if is it a correct understanding? |
matcher, inserter and source are expected to be domain names (strings)... Can we suggest to pass GVL ID instead? |
In reference to Example 5, I might be missing some key information, but I'm wondering if it's necessary to make |
Updated user.id attribute description to match language of buyeruid per Public Comment Feedback
Removing examples for Public Comment period from `matcher` and `mm` attributes
Update 2.6.md
OpenRTB Updates:
Updated buyeruid attribute description in Object: User
Updated ifa attribute description in Object: User
New attributes (inserter, matcher, mm) in Object: EID
Updated source attribute description in in Object: EID
New Implementation Guidance with multiple Bridging Scenarios
Added Appendix C: Cookie Based ID Syncing