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: docs/endpoints/post-identity-buckets.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Used by: This endpoint is used mainly by advertisers and data providers. For det
16
16
:::important
17
17
If you're using the latest version of `POST /v3/identity/map`, v3, you don't need to use `POST /identity/buckets` at all. You only need to use it if you're using the earlier version, `POST /v2/identity/map`.
18
18
19
-
If you're using the earlier version, we recommend that you upgrade as soon as possible, to take advantage of improvements.
19
+
If you're using the V2 version, we recommend that you upgrade as soon as possible, to take advantage of improvements. For migration guidance, see [Migration From V2 Identity Map](post-identity-map-v3.md#migration-from-v2-identity-map).
@@ -115,7 +115,7 @@ The response arrays preserve the order of input arrays. Each element in the resp
115
115
116
116
Input values that cannot be mapped to a raw UID2 are mapped to an error object with the reason for unsuccessful mapping. An unsuccessful mapping occurs if the DII is invalid or has been opted out from the UID2 ecosystem. In these cases, the response status is `success` but no raw UID2 is returned.
117
117
118
-
The following example shows input and response.
118
+
The following example shows the input and corresponding response.
119
119
120
120
Input:
121
121
@@ -153,7 +153,7 @@ Response:
153
153
"phone": [],
154
154
"phone_hash": []
155
155
},
156
-
"status":"success"
156
+
"status":"success"
157
157
}
158
158
```
159
159
@@ -190,7 +190,92 @@ The following table lists the `status` property values and their HTTP status cod
190
190
| Status | HTTP Status Code | Description |
191
191
| :--- | :--- | :--- |
192
192
|`success`| 200 | The request was successful. The response will be encrypted. |
193
-
|`client_error`| 400 | The request had missing or invalid parameters.|
193
+
|`client_error`| 400 | The request had missing or invalid parameters.|
194
194
|`unauthorized`| 401 | The request did not include a bearer token, included an invalid bearer token, or included a bearer token unauthorized to perform the requested operation. |
195
195
196
196
If the `status` value is anything other than `success`, the `message` field provides additional information about the issue.
197
+
198
+
## Migration From V2 Identity Map
199
+
200
+
### Migration Overview
201
+
202
+
The V3 Identity Map API provides several improvements over V2:
203
+
204
+
-**Simplified Refresh Management**: Monitor for UID2s reaching `refresh_from` timestamps instead of polling <Linkhref="../ref-info/glossary-uid#gl-salt-bucket-id">salt buckets</Link> for rotation
205
+
-**Previous UID2 Access**: Access to previous raw UID2s for 90 days after rotation for campaign measurement
206
+
-**Single Endpoint**: Use only `/v3/identity/map` instead of both `/v2/identity/map` and `/v2/identity/buckets`
207
+
-**Multiple Identity Types In One Request**: Process emails and phone numbers in a single request
208
+
-**Improved Performance**: The V3 API uses significantly less bandwidth for the same amount of DII
#### 3. **Replace Salt Bucket Monitoring with Refresh Timestamp Logic**
261
+
**V3 Approach (Refresh Timestamps)**:
262
+
263
+
```python
264
+
import time
265
+
266
+
defis_refresh_needed(mapping):
267
+
now =int(time.time() *1000) # Convert to milliseconds
268
+
return now >= mapping['refresh_from']
269
+
270
+
# Check individual mappings for refresh needs
271
+
to_remap = [mapping for mapping in mappings if is_refresh_needed(mapping)]
272
+
remap_identities(to_remap)
273
+
```
274
+
275
+
### Additional Resources
276
+
277
+
For SDK-specific migration guidance, see:
278
+
-[SDK for JavaScript V3](../sdks/sdk-ref-javascript-v3.md) for client-side implementations
279
+
-[SDK for Java](../sdks/sdk-ref-java.md) for server-side implementations (see Usage for Advertisers/Data Providers section)
280
+
281
+
For general information about identity mapping, see [Advertiser/Data Provider Integration Overview](../guides/integration-advertiser-dataprovider-overview.md).
Copy file name to clipboardExpand all lines: docs/endpoints/post-identity-map.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ For details about the UID2 opt-out workflow and how users can opt out, see [User
20
20
This documentation is for version 2 of this endpoint, which is not the latest version. For the latest version, v3, see [POST /identity/map](post-identity-map-v3.md).
21
21
22
22
:::note
23
-
If you're using the earlier version, we recommend that you upgrade as soon as possible, to take advantage of improvements.
23
+
If you're using the V2 version, we recommend that you upgrade as soon as possible, to take advantage of improvements. For migration guidance, see [Migration From V2 Identity Map](post-identity-map-v3.md#migration-from-v2-identity-map).
24
24
:::
25
25
26
26
## Batch Size and Request Parallelization Requirements
This directory contains Python tests for the code samples in the [POST /identity/map v3 documentation](../../docs/endpoints/post-identity-map-v3.md). The tests verify that the Python code examples in the documentation work correctly and demonstrate proper usage patterns.
4
+
5
+
## Quick Start
6
+
7
+
### Prerequisites
8
+
9
+
1.**Install UV** (Python package manager):
10
+
```bash
11
+
pip install uv
12
+
```
13
+
14
+
## Environment Configuration
15
+
Fill the following environment variables into the `.env` file. The file is gitignored.
0 commit comments