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
description: Adlane Real-Time Data Provider for Age Verification
6
+
page_type: module
7
+
module_type: rtd
8
+
module_code: adlaneRtdProvider
9
+
enable_download: true
10
+
vendor_specific: true
11
+
sidebarType: 1
12
+
---
13
+
14
+
# Adlane RTD Provider
15
+
16
+
## Overview
17
+
18
+
The Adlane Real-Time Data (RTD) Provider automatically retrieves age verification information and adds it to the bid stream, allowing for age-appropriate ad targeting. This module does not have a Global Vendor List ID (GVL ID).
19
+
20
+
## Integration
21
+
22
+
1. Compile the Adlane RTD Module into your Prebid build:
23
+
24
+
```bash
25
+
gulp build --modules=adlaneRtdProvider ...
26
+
```
27
+
28
+
2. Use `setConfig` to instruct Prebid.js to initialize the adlaneRtdProvider module, as specified below.
| waitForIt | Boolean | Whether to waitfor the module before auction |true|
52
+
53
+
## Age Verification Data
54
+
55
+
The module attempts to retrieve age verification data from the following sources, in order:
56
+
57
+
1. AdlCmp API (if available)
58
+
2. Local storage
59
+
60
+
The age verification data is added to the bid request in the following format:
61
+
62
+
```javascript
63
+
{
64
+
ortb2: {
65
+
regs: {
66
+
ext: {
67
+
age_verification: {
68
+
status: 'accepted', //The acceptance indicates that the user has confirmed they are 21 years of age or older (accepted/declined)
69
+
id: "123456789123456789", //unique identifier for the age verification // Optional
70
+
decisionDate: "2011-10-05T14:48:00.000Z", //ISO 8601 date string (e.g.,"2011-10-05T14:48:00.000Z") // Optional, represents the date when the age verification decision was made
*`thetradedesk` will be exposed as `tdid` because of historical reasons.
109
-
* In order for`segments` to be presentin`ortb2.user.data` of the bid requests, you need to configure the [liveIntentRTDProvider](/dev-docs/modules/liveIntentRtdProvider.html) module.
109
+
* In order for`segments` to be presentin`ortb2.user.data` of the bid requests, you need to configure the [liveIntentRTDProvider](/dev-docs/modules/liveIntentRtdProvider.html) module.
110
110
111
111
For example, incase`uid2` is configured to be requested in addition to the `nonID`, the `request.userId` object would look like the following:
112
112
@@ -195,9 +195,6 @@ pbjs.setConfig({
195
195
196
196
## LiveIntent ID configuration
197
197
198
-
{: .alert.alert-info :}
199
-
NOTE: For optimal performance, the LiveIntent ID sub-module should be called at every opportunity. It is best not to use `params.storage` with this sub-module as it has its own optimal caching mechanism.
200
-
201
198
{: .table .table-bordered .table-striped }
202
199
203
200
| Param under userSync.userIds[] | Scope | Type | Description | Example |
0 commit comments