Skip to content

Commit c2705ce

Browse files
committed
fix broken links
1 parent 4c93836 commit c2705ce

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

docs/getting-started/gs-faqs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -170,7 +170,7 @@ We do not make any promises about when the rotation takes place. To stay as up-t
170170

171171
#### Do refreshed emails get assigned to the same bucket with which they were previously associated?
172172

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.
174174

175175
:::info
176176
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
208208

209209
However, there is a variable factor, which is the <Link href="../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.
210210

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*.
212212

213213
#### If two operators process the same DII, are the results the same?
214214

docs/guides/integration-advertiser-dataprovider-endpoints.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ The steps for advertisers and data providers integrating with UID2 by calling th
3434

3535
1. Generate a raw UID2 from <Link href="../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.
3636

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).
3838

3939
2. Use the UID2s you received in Step 1. For example, you might do one or more of the following:
4040
- 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
5454

5555
5. Monitor for salt bucket rotations related to your stored raw UID2s.
5656

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).
5858

5959
6. Periodically, monitor for opt-out status, to be sure that you don't continue using UID2s for users that have recently opted out.
6060

6161
**Instructions**: See [Monitor for Opt-Out Status](#monitor-for-opt-out-status).
6262

63-
### Generate a raw UID2 for DII
63+
### Generate Raw UID2s from DII
6464

6565
| Step | Endpoint | Description |
6666
| --- | --- | --- |
@@ -91,10 +91,10 @@ To help ensure that your integration has the current raw UID2s, check salt bucke
9191

9292
To keep your UID2-based audience information accurate and up to date, follow these integration steps every day:
9393

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:
9595
- The mapping between DII (`identifier`), raw UID2 (`advertising_id`), and salt bucket (`bucket_id`).
9696
- 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).
9898

9999
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).
100100

docs/guides/integration-advertiser-dataprovider-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ At a high level, the steps for advertisers and data providers integrating with U
4747

4848
5. Monitor for Salt Bucket Rotations for your stored raw UID2s.
4949

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).
5151

5252
## Summary of Implementation Options
5353

@@ -86,7 +86,7 @@ To generate raw UID2s, use one of the following options:
8686

8787
- AWS Entity Resolution: [AWS Entity Resolution Integration Guide](integration-aws-entity-resolution.md).
8888

89-
- HTTP endpoints: [Generate a raw UID2 from DII](integration-advertiser-dataprovider-endpoints.md#generate-a-raw-uid2-from-dii).
89+
- HTTP endpoints: [Generate a raw UID2 from DII](integration-advertiser-dataprovider-endpoints.md#generate-raw-uid2s-from-dii).
9090

9191
### 2: Store Raw UID2s and Salt Bucket IDs
9292

0 commit comments

Comments
 (0)