diagram updates and other updates

Author: genwhittTTD

docs/getting-started/gs-faqs.md

@@ -170,7 +170,7 @@ We do not make any promises about when the rotation takes place. To stay as up-t
 
 #### Do refreshed emails get assigned to the same bucket with which they were previously associated?
 
-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#retrieve-a-raw-uid2-for-dii) and save the returned UID2 and bucket ID again.
+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.
 
 :::info
 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
 
 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.
 
-For more information, see [Monitor for salt bucket rotations related to your stored raw UID2s](../guides/integration-advertiser-dataprovider-overview.mdmonitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s) in the *Advertiser/Data Provider Integration Guide*.
+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*.
 
 #### If two operators process the same DII, are the results the same?
 

…uides/images/advertiser-flow-mermaid.png …es/advertiser-flow-endpoints-mermaid.pngdocs/guides/images/advertiser-flow-mermaid.png renamed to docs/guides/images/advertiser-flow-endpoints-mermaid.png docs/guides/images/advertiser-flow-mermaid.png renamed to docs/guides/images/advertiser-flow-endpoints-mermaid.png

@@ -0,0 +1,78 @@
+Updated 12/23/24 to split out Advertiser/Data Provider overview diagram vs endpoints diagram.
+
+URL: https://mermaid.live/edit 
+
+
+<!-- 12/23/24: Code: 
+
+  sequenceDiagram
+    participant ADP as Advertuser/Data Provider
+    participant UID2 as UID2 Operator
+    participant DSP
+    loop 1. Generate a raw UID2 from DII.
+    ADP->>UID2: 1-a. Send a request containing DII using an SDK, raw HTTP endpoint, Snowflake, or AWS Entity Resolution.
+    UID2->>ADP: 1-b. Store the raw UID2 and salt bucket ID.
+    end
+    ADP-->>DSP: 2. Manipulate or combine raw UID2s, then send to DSPs to create audiences and conversions.
+
+    loop 3. Monitor for salt bucket rotations related to your stored raw UID2s.
+       ADP->>UID2: 3-a. Monitor salt bucket rotations using an SDK, raw HTTP endpoint, or Snowflake.
+       UID2->>ADP: 3-b. Receive salt buckets rotated since a specified timestamp.
+       ADP->>UID2: 3-c. Compare the rotated salt buckets to the stored UID2 salt buckets.<br>If salt bucket ID has changed, resend DII for a new raw UID2.
+       UID2->>ADP: 3-d. Store the new raw UID2 and salt bucket ID.
+    end
+    loop 4. Monitor for opt-out status.
+       ADP->>UID2: 4-a. Send a request to the POST /optout/status endpoint.
+       UID2->>ADP: 4-b. Receive updated optout status. For any new opt-outs, remove the stored raw UID2 and salt bucket ID.
+    end
+
+-->
+
+<!-- Config:
+
+{
+  "theme": "forest"
+}
+
+-->
+
+<!-- 8/30/24: Code:
+
+  sequenceDiagram
+    participant DP as Data Provider
+    participant UID2 as UID2 Operator
+    participant DSP
+    loop 1. Retrieve a UID2 for DII using the identity map endpoint.
+    DP->>UID2: 1-a. Send a request containing DII to the identity mapping endpoints.
+    UID2->>DP: 1-b. Store the raw UID2 and salt bucket returned from the identity mapping service.
+    end
+    DP-->>DSP: 2. Send stored UID2s to DSPs to create audiences and conversions.
+
+    loop 3. Monitor for salt bucket rotations related to your stored raw UID2s.
+       DP->>UID2: 3-a. Monitor salt bucket rotations using the bucket service.
+       UID2->>DP: 3-b. Return salt buckets rotated since a specified timestamp.
+       DP->>UID2: 3-c. Compare the rotated salt buckets to the stored UID2 salt buckets.<br>If rotated, resend DII to identity mapping service for a new raw UID2.
+       UID2->>DP: 3-d. Store the raw UID2 and the salt bucket returned from the identity mapping service.
+    end
+
+ -->
+
+<!-- Config:
+
+{
+  "theme": "forest"
+}
+
+-->
+
+<!--  12/23/24: URL with "Pan & Zoom" on:
+
+https://mermaid.live/edit#pako:eNqNVFtr21AM_ivCz25Kmz6FUSjzLmGUhrpjMPKiHCvJofGRdy4pofS_T7KdxO1S1kCIY0v6bvJ5zgxXlE0ygEB_EjlDhcWVx3ruQD4N-miNbdBFuClmgAFuqi35mAL58wIjwszz1lbk_234OS0utaP9vWvIY-QTZUU5625umBu4GME3clpLgODxqWtfeq6hmE5HXalwObu-1icTuDjDEZTkKq1XESGCYRfROutW2gQp6BU6KIsfeTv0-8PDDKSnYetiDqXjp-UGHykH9nDzq4QvLtq4g3sKvEnRsuuRFVOghYAiLwRZRBHENR3JonAJuImwSOaRIkyLvlkAj_xlikifwOUIbtHZJm1Us8AbrhfWHeeFXMc7SUjmRlbDgv4aT61LqbIaXGhxRbnkE4RwENCBsWOBYWeFLSzlO-TnOaJKDOKfkmhRdpykSsVVRya9jjcJjDWB_fDTg_-bgHQeQjiiDN0eq9v3ZMhuaYgSOhihKRhGtyY0ZOzSqg5byzpg3bxH3IzgM9eyjn2E-0nD8WKGPuu9aBMePh99Wvjr6fJN4rCWzTdrdCuqRDC14ekuqvkIjp4Orr4ntxou17DhAwvWRn71OnJu4hmnKEJQ3t_TjlydeJl6_bO78gHOZYjMOO9mHPI7LeFqmFhqqtbabsCeBHxVO9yu1dcTDOpXzVsa2v4h7Vme1eRrtJUcac96e57JjJrm2UQuxQTRM8_m7kUqMUUud85kk-gT5ZnntFpnkyVugvzr6PaH4eEuVermbXdmtkdnnskh9pt5X_PyF8MiupQ
+
+-->
+
+<!--  8/30/24: URL with "Pan & Zoom" on:
+
+https://mermaid-js.github.io/mermaid-live-editor/edit#pako:eNqlVMGO2jAQ_ZWRz9mIhISFqOLS9MBhVbSol4qLiQfWKrFT22FLEf_esZOwoIVTuQRnZt5782biE6u0QFYwAIu_W1QVlpLvDK_XCujXcONkJRuuHJRL4BZK7jgsjT5IgeZz0o9Fmfq08PzeoOFO30krV8vu5V7rBpIYXtEZiQcE3pVutYFysYDWSrUD94ZAfMpJd4SaN4BKNFoqF3co5fJpPvd1BSRPPIYVxQnJ-Jasg0orx6XySB7T6U-AjY8NoLZH9YCEWy496oZQqRUMpYa_950Sj-V7B5u2-oWOGF1rFArYGl3fZ7FoDrLCnoM4Ly14rhWRpX0D1vOJQGS9aAqGZ2WQO3KqFdIPzAYV1OMBjZVaeflX5o5jeNFKElYw9Uatdtz5CtK9J0jh0Y-6NQP10OfgyK3VY2_1gH0f92N8fei2-1uTx97k1-DgNZzt8EgOgVV-Q2yDldxKr1fWNGBeNw8EVjF81TVtXj-3AegavV-HK7dv4vGXjZkvtkNtRF5ZP51-kx7NN5jNQeH7xcUHTYuHmxVk_fd2sYjVaGouBX3nJx9YM6qtcc0K-ks6ycI1W6szZfLW6dVRVaxwpsWIGd3u3lix5XtLp7YR5EF_Qwwp3ctvwq_BJRPD8aW7XMIdEzH68n9qfamjIytO7A8rxvkkTpPseTYZJXmSpHnEjqzI0zifzLJxRqFsNkqm54j9DfWjeJqlWf48nY3yZJTns-T8D5qfkDg
+
+-->

docs/guides/images/advertiser-flow-overview-mermaid.png

@@ -23,9 +23,9 @@ The following diagram outlines the steps that data collectors must complete to m
 
 DII refers to a user's normalized email address or phone number, or the normalized and SHA-256-hashed email address or phone number.
 
-![Advertiser Flow](images/advertiser-flow-mermaid.png)
+![Advertiser Flow](images/advertiser-flow-endpoints-mermaid.png)
 
-<!-- diagram source: resource/advertiser-flow-mermaid.md.bak -->
+<!-- diagram source: resource/advertiser-flow-endpoints-mermaid.md.bak -->
 
 
 ## Detailed Steps
@@ -34,7 +34,7 @@ The steps for advertisers and data providers integrating with UID2 by calling th
 
 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.
 
-    **Instructions**: see [Retrieve a raw UID2 for DII](#retrieve-a-raw-uid2-for-dii).
+    **Instructions**: see [Retrieve a raw UID2 for DII](#generate-a-raw-uid2-for-dii).
 
 2. Use the UID2s you received in Step 1. For example, you might do one or more of the following:
    - Do some manipulation: for example, combine UID2s you generated from DII and UID2s received from another participant such as an advertiser or data provider.
@@ -58,14 +58,14 @@ The steps for advertisers and data providers integrating with UID2 by calling th
 
 6.	Periodically, monitor for opt-out status, to be sure that you don't continue using UID2s for users that have recently opted out.
 
-    **Instructions**: See [Check Opt-Out Status](#check-opt-out-status).
+    **Instructions**: See [Monitor for Opt-Out Status](#monitor-for-opt-out-status).
 
-### Retrieve a raw UID2 for DII
+### Generate a raw UID2 for DII
 
 | Step | Endpoint | Description |
 | --- | --- | --- |
 | 1-a | [POST&nbsp;/identity/map](../endpoints/post-identity-map.md) request | Send a request containing DII to the identity mapping endpoint. |
-| 1-b | [POST&nbsp;/identity/map](../endpoints/post-identity-map.md) response | The `advertising_id` (raw UID2) returned in the response can be used to target audiences on relevant DSPs.<br/>The response returns a user's raw UID2 and the corresponding `bucket_id` for the salt bucket. The salt assigned to the bucket rotates annually, which impacts the generated raw UID2. For details on how to check for salt bucket rotation, see [3: Monitor for salt bucket rotations](monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s).<br/>For ease of maintenance, a recommended approach is to store a user's raw UID2 and `bucket_id` in a mapping table. For guidance on incremental updates, see [Use an incremental process to continuously update raw UID2s](#use-an-incremental-process-to-continuously-update-raw-uid2s). |
+| 1-b | [POST&nbsp;/identity/map](../endpoints/post-identity-map.md) response | The `advertising_id` (raw UID2) returned in the response can be used to target audiences on relevant DSPs.<br/>The response returns a user's raw UID2 and the corresponding `bucket_id` for the salt bucket. The salt assigned to the bucket rotates annually, which impacts the generated raw UID2. For details on how to check for salt bucket rotation, see [3: Monitor for salt bucket rotations](#monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s).<br/>For ease of maintenance, a recommended approach is to store a user's raw UID2 and `bucket_id` in a mapping table. For guidance on incremental updates, see [Use an incremental process to continuously update raw UID2s](#use-an-incremental-process-to-continuously-update-raw-uid2s). |
 
 ### Send stored raw UID2s to DSPs to create audiences or conversions
 
@@ -91,14 +91,14 @@ To help ensure that your integration has the current raw UID2s, check salt bucke
 
 To keep your UID2-based audience information accurate and up to date, follow these integration steps every day:
 
-1. The response from the [UID2 retrieval step](#retrieve-a-raw-uid2-for-dii) contains mapping information. Cache the following:
+1. The response from the [UID2 retrieval step](#generate-a-raw-uid2-for-dii) contains mapping information. Cache the following:
    - The mapping between DII (`identifier`), raw UID2 (`advertising_id`), and salt bucket (`bucket_id`).
    - The most recent `last_updated` timestamp.
-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](#retrieve-a-raw-uid2-for-dii).
+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).
 
    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).
 
-## Check Opt-Out Status
+## Monitor for Opt-Out Status
 
 It's important to honor user opt-out status. Here are two ways you can check that you have the latest opt-out information: