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/getting-started/gs-faqs.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,7 +170,7 @@ We do not make any promises about when the rotation takes place. To stay as up-t
170
170
171
171
#### Do refreshed emails get assigned to the same bucket with which they were previously associated?
172
172
173
-
Not necessarily. After you remap emails associated with a particular bucket ID, the emails might be assigned to a different bucket ID. To check the bucket ID, [call the mapping function](../guides/integration-advertiser-dataprovider-overview.md#generate-a-raw-uid2-for-dii) and save the returned UID2 and bucket ID again.
173
+
Not necessarily. After you remap emails associated with a particular bucket ID, the emails might be assigned to a different bucket ID. To check the bucket ID, see [Generate Raw UID2s from DII](../guides/integration-advertiser-dataprovider-overview.md#1-generate-raw-uid2s-from-dii) and save the returned UID2 and bucket ID again.
174
174
175
175
:::info
176
176
When mapping and remapping emails, do not make any assumptions about the number of buckets, their rotation dates, or the specific bucket that an email gets assigned to.
@@ -208,7 +208,7 @@ In general yes, the process of generating a raw UID2 from DII is the same, and r
208
208
209
209
However, there is a variable factor, which is the <Linkhref="../ref-info/glossary-uid#gl-salt">salt</Link> value that's used in generating the raw UID2. The salt values are rotated roughly once per year (for details, see [How often should UID2s be refreshed for incremental updates?](#how-often-should-uid2s-be-refreshed-for-incremental-updates)). If the salt value changes between one request and another, those two requests result in two different raw UID2, even when the DII is the same.
210
210
211
-
For more information, see [Monitor for salt bucket rotations related to your stored raw UID2s](../guides/integration-advertiser-dataprovider-overview.md#monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s) in the *Advertiser/Data Provider Integration Guide*.
211
+
For more information, see [Monitor for Salt Bucket Rotations for Your Stored Raw UID2s](../guides/integration-advertiser-dataprovider-overview.md#5-monitor-for-salt-bucket-rotations-for-your-stored-raw-uid2s) in the *Advertiser/Data Provider Integration Guide*.
212
212
213
213
#### If two operators process the same DII, are the results the same?
Copy file name to clipboardExpand all lines: docs/guides/integration-advertiser-dataprovider-endpoints.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ The steps for advertisers and data providers integrating with UID2 by calling th
34
34
35
35
1. Generate a raw UID2 from <Linkhref="../ref-info/glossary-uid#gl-dii">directly identifying information (DII)</Link>, or receive UID2s from another UID2 participant such as a data provider acting on your behalf.
36
36
37
-
**Instructions**: see [Retrieve a raw UID2 for DII](#generate-a-raw-uid2-for-dii).
37
+
**Instructions**: see [Generate Raw UID2s from DII](#generate-raw-uid2s-from-dii).
38
38
39
39
2. Use the UID2s you received in Step 1. For example, you might do one or more of the following:
40
40
- Do some manipulation: for example, combine UID2s you generated from DII and UID2s received from another participant such as an advertiser or data provider.
@@ -54,13 +54,13 @@ The steps for advertisers and data providers integrating with UID2 by calling th
54
54
55
55
5. Monitor for salt bucket rotations related to your stored raw UID2s.
56
56
57
-
**Instructions**: See [Monitor for salt bucket rotations related to your stored raw UID2s](integration-advertiser-dataprovider-overview.md#monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s).
57
+
**Instructions**: See [Monitor for salt bucket rotations related to your stored raw UID2s](#monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s).
58
58
59
59
6. Periodically, monitor for opt-out status, to be sure that you don't continue using UID2s for users that have recently opted out.
60
60
61
61
**Instructions**: See [Monitor for Opt-Out Status](#monitor-for-opt-out-status).
62
62
63
-
### Generate a raw UID2 for DII
63
+
### Generate Raw UID2s from DII
64
64
65
65
| Step | Endpoint | Description |
66
66
| --- | --- | --- |
@@ -91,10 +91,10 @@ To help ensure that your integration has the current raw UID2s, check salt bucke
91
91
92
92
To keep your UID2-based audience information accurate and up to date, follow these integration steps every day:
93
93
94
-
1. The response from the [UID2 retrieval step](#generate-a-raw-uid2-for-dii) contains mapping information. Cache the following:
94
+
1. The response from the [UID2 retrieval step](#generate-raw-uid2s-from-dii) contains mapping information. Cache the following:
95
95
- The mapping between DII (`identifier`), raw UID2 (`advertising_id`), and salt bucket (`bucket_id`).
96
96
- The most recent `last_updated` timestamp.
97
-
2. Using the results from Step 3, [Monitor for salt bucket rotations related to your stored raw UID2s](#monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s), remap any raw UID2 for which the salt buckets have been rotated by retrieving new raw UID2 for those IDs, following Step 1, [Retrieve a raw UID2 for DII](#generate-a-raw-uid2-for-dii).
97
+
2. Using the results from Step 3, [Monitor for salt bucket rotations related to your stored raw UID2s](#monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s), remap any raw UID2 for which the salt buckets have been rotated by retrieving new raw UID2 for those IDs, following Step 1, [Generate Raw UID2s from DII](#generate-raw-uid2s-from-dii).
98
98
99
99
Then, use the refreshed UID2s to update audiences or conversions, following Step 2, [send raw UID2 to a DSP](#send-stored-raw-uid2s-to-dsps-to-create-audiences-or-conversions).
Copy file name to clipboardExpand all lines: docs/guides/integration-advertiser-dataprovider-overview.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ At a high level, the steps for advertisers and data providers integrating with U
47
47
48
48
5. Monitor for Salt Bucket Rotations for your stored raw UID2s.
49
49
50
-
6. Periodically, monitor for opt-out status, to be sure that you don't continue using UID2s for users that have recently opted out. For details, see [Monitor for Opt-Out Status](#monitor-for-opt-out-status).
50
+
6. Periodically, monitor for opt-out status, to be sure that you don't continue using UID2s for users that have recently opted out. For details, see [Monitor for Opt-Out Status](#6-monitor-for-opt-out-status).
51
51
52
52
## Summary of Implementation Options
53
53
@@ -86,7 +86,7 @@ To generate raw UID2s, use one of the following options:
0 commit comments