You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: dev-docs/modules/jwplayerRtdProvider.md
+28-16Lines changed: 28 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,31 +110,43 @@ Each bidRequest for which targeting information was found will conform to the fo
110
110
adUnitCode: 'xyz',
111
111
bidId: 'abc',
112
112
...,
113
-
rtd: {
114
-
jwplayer: {
115
-
targeting: {
116
-
segments: ['123', '456'],
117
-
content: {
118
-
id: 'jw_abc123'
119
-
}
120
-
}
121
-
}
122
-
}
113
+
ortb2: {
114
+
site: {
115
+
content: {
116
+
id: 'jw_abc123',
117
+
data: [{
118
+
name: 'jwplayer',
119
+
ext: {
120
+
segtax: 502
121
+
},
122
+
segment: [{
123
+
id: '123'
124
+
}, {
125
+
id: '456'
126
+
}]
127
+
}]
128
+
}
129
+
}
130
+
}
123
131
}
124
132
```
133
+
Each bid for which targeting information was found will have a ortb2 param conforming to the [oRTB v2 object structure](https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf). The `ortb2` object will contain our proprietaty targeting segments in a format compliant with the [IAB's segment taxonomy structure](https://github.com/InteractiveAdvertisingBureau/openrtb/blob/master/extensions/community_extensions/segtax.md).
125
134
126
-
Read the bidRequest.jwTargeting object and pass the values to your endpoint as appropriate.
135
+
The content's ID can be obtained in the `bid.ortb2.site.content.id` property path and the targeting segments can be found in `bid.ortb2.site.content.data.segment`.
0 commit comments