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

Where to specify app contextual data in ortb2 object? #7415

Closed
patmmccann opened this issue Sep 14, 2021 · 4 comments
Closed

Where to specify app contextual data in ortb2 object? #7415

patmmccann opened this issue Sep 14, 2021 · 4 comments
Labels

Comments

@patmmccann
Copy link
Collaborator

Type of issue

Standards

Description

#6057 proposes where to put content taxonomies. If they are contextual they go in site.content.data, but the site field is not valid openRTB when the app field exists, so we would propose app.content.data with the structure mirroring that defined in IAB SDA proposal and in #6057

Separately, there appears to be a need for a segtax 7 for app focused content data at https://github.com/InteractiveAdvertisingBureau/AdCOM/blob/master/AdCOM%20v1.0%20FINAL.md#list_categorytaxonomies ; or additions to the segtax 6 = content 2.2 that are app focused such as those proposed at https://docs.google.com/spreadsheets/d/1T4P7DfvAPLvwmNC_mSwfHzaW57M2uy__/edit?usp=sharing&ouid=105283563856401027398&rtpof=true&sd=true.

If data provider wanted to specify some data from existing content taxonomy 6 and future app context taxonomy 7, the object could look like this:

ortb2: {
	app: {
		name: "myappname",
		keywords: "power tools, drills",
		content: {
			data: [{
				name: "www.dataprovider1.com",
				ext: {
					"segtax": 6
				},
				segment: [{
					id: "687"
				}, {
					id: "123"
				}]
			}],
			  data: [{
				name: "www.dataprovider1.com",
				ext: {
					"segtax": 7
				},
				segment: [{
					id: "456"
				}, {
					id: "789"
				}]
			}]
		}
	}
@abhinavsinha001
Copy link

Is app object applicable for Prebid Js implementation ? Ideally I expect respective Prebid implementations (server, sdk) support data.segment for all locations which are supported by oRTB.

Small correction on the format for supporting multiple taxonomies

{
  "app": {
    "name": "myappname",
    "keywords": "power tools, drills",
    "content": {
      "data": [
        {
          "name": "www.dataprovider1.com",
          "ext": {
            "segtax": 6
          },
          "segment": [
            {
              "id": "687"
            },
            {
              "id": "123"
            }
          ]
        },
        {
          "name": "www.dataprovider1.com",
          "ext": {
            "segtax": 7
          },
          "segment": [
            {
              "id": "456"
            },
            {
              "id": "789"
            }
          ]
        }
      ]
    }
  }
}

@patmmccann
Copy link
Collaborator Author

Ty for the correction. The taxonomy committee uses this board, but perhaps you are correct this would get more attention on the SDK board. I am not familiar with that.

@patmmccann
Copy link
Collaborator Author

tl;dr: app.content.data should be documented somewhere as following the same structure as site.content.data

@patmmccann
Copy link
Collaborator Author

Closing with submission of prebid/prebid.github.io#3299

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants