Skip to content

Commit 7770f81

Browse files
authored
added instructions for first party data (#6260)
1 parent 874d81e commit 7770f81

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed

dev-docs/bidders/lane4.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -90,3 +90,30 @@ var adUnits = [
9090
}
9191
];
9292
```
93+
94+
#### First Party Data
95+
96+
In release 4.30 and later, publishers should use the `ortb2` method of setting [First Party Data](https://docs.prebid.org/features/firstPartyData.html). The following fields are supported:
97+
98+
* ortb2.user.id
99+
* ortb2.user.buyeruid
100+
* ortb2.user.keywords
101+
* ortb2.user.ext.*
102+
103+
Example first party data that's available to all bidders and all adunits:
104+
105+
```javascript
106+
pbjs.setConfig({
107+
ortb2: {
108+
user: {
109+
id: 123456789, // Unique pseudonymized ID for the user (e.g., NPI).
110+
buyeruid: 987654321, // DSP-assigned user ID for identity resolution.
111+
keywords: "kw1,kw2", // Interest or specialty tags (e.g., oncology, cardiology)
112+
ext: {
113+
key1: "values", // Custom healthcare metadata (e.g., icd10), single or comma seperated.
114+
key2: "values" // Additional campaign context (e.g., ndc), single or comma seperated.
115+
}
116+
}
117+
}
118+
});
119+
```

0 commit comments

Comments
 (0)