Skip to content

Commit fa78158

Browse files
committed
added instructions for first party data
1 parent 7770f81 commit fa78158

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed

dev-docs/bidders/relevatehealth.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,3 +54,30 @@ var adUnits = [
5454
}
5555
];
5656
```
57+
58+
#### First Party Data
59+
60+
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:
61+
62+
* ortb2.user.id
63+
* ortb2.user.buyeruid
64+
* ortb2.user.keywords
65+
* ortb2.user.ext.*
66+
67+
Example first party data that's available to all bidders and all adunits:
68+
69+
```javascript
70+
pbjs.setConfig({
71+
ortb2: {
72+
user: {
73+
id: 123456789, // Unique pseudonymized ID for the user (e.g., NPI).
74+
buyeruid: 987654321, // DSP-assigned user ID for identity resolution.
75+
keywords: "kw1,kw2", // Interest or specialty tags (e.g., oncology, cardiology)
76+
ext: {
77+
key1: "values", // Custom healthcare metadata (e.g., icd10), single or comma seperated.
78+
key2: "values" // Additional campaign context (e.g., ndc), single or comma seperated.
79+
}
80+
}
81+
}
82+
});
83+
```

0 commit comments

Comments
 (0)