Skip to content
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

Merged
merged 18 commits into from
Sep 23, 2024
Merged

OpenRTB 2.6-202409 #103

merged 18 commits into from
Sep 23, 2024

Conversation

hillslatt
Copy link
Collaborator

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

added new attributes and appendix
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
@pm-harshad-mane
Copy link

In example 4, and 5, the buyeruid is passed and the same ID is mentioned in the eids arrray as buyeruid is derived.
In example 6 and 7 the device.ifa is mentioned as it is retrieved directly from CTV OS hence it mentioned
In example 8, device.ifa is not mentioned as it not retrieved directly from CTV OS ,so only mentioned in eids

So if buyeruid is derived we mention it in buyeruid and eids
But if device.ifa can be derived we do not recommend to set it in device.ifa but only allow to be passed in eids.

is it a correct understanding?

@pm-harshad-mane
Copy link

matcher, inserter and source are expected to be domain names (strings)... Can we suggest to pass GVL ID instead?
Will not work for passing publisher domain but thinking of sustainability, will be able to save some characters from payload.

@pm-harshad-mane
Copy link

In reference to Example 5, I might be missing some key information, but I'm wondering if it's necessary to make uids[].id mandatory when the eid has "source": "universalid.com". My concern is that DSPs may not be able to validate this value, and including it could lead to an increased payload size. I would appreciate any clarification or additional insights on this matter.

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
@hillslatt hillslatt changed the title OpenRTB 2.6-202407 OpenRTB 2.6-202409 Sep 23, 2024
@hillslatt hillslatt merged commit 75fad05 into main Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants