mods

Author: genwhittTTD

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

@@ -1,20 +1,20 @@
 ---
-title: Advertiser/Data Provider Integration by Calling to HTTP Endpoints
+title: Advertiser/Data Provider Integration Directly to HTTP Endpoints
 sidebar_label: HTTP Endpoints
-description: Integration for organizations that collect user data and push it to other participants.
+description: Integration for organizations that collect user data and push it to other participants, coding to HTTP endpoints rather than an SDK or Snowflake.
 hide_table_of_contents: false
 sidebar_position: 07
 displayed_sidebar: sidebarAdvertisers
 ---
 
 import Link from '@docusaurus/Link';
 
-# Advertiser/Data Provider Integration By Calling HTTP Endpoints
+# Advertiser/Data Provider Integration Directly to HTTP Endpoints
 
-This guide covers integration steps for advertisers and data providers to integration by writing code to call UID2 HTTP endpoints, rather than using another implementation options such as an SDK, Snowflake, or AWS Entity Resolution.
+This guide covers integration steps for advertisers and data providers to integrate with UID2 by writing code to call UID2 HTTP endpoints, rather than using another implementation options such as an SDK, Snowflake, or AWS Entity Resolution.
 
 :::tip
-For a summary of UID2 integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md).
+For a summary of all integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md).
 :::
 
 ### High-Level Steps

docs/guides/integration-advertiser-dataprovider.md

@@ -22,7 +22,7 @@ If you're not currently part of the UID2 ecosystem, go to the [Request Access to
 For a video presentation about integration with UID2 by using AWS Entity Resolution, and a demo, see [Getting Started with AWS Entity Resolution Integration with Unified ID 2.0](https://www.youtube.com/watch?v=ORbSsKMgVj8) on YouTube.
 
 :::tip
-For a summary of UID2 integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md).
+For a summary of all integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md).
 :::
 
 ## Functionality

docs/guides/integration-aws-entity-resolution.md

@@ -18,7 +18,7 @@ The following listings for UID2 are available on the Snowflake marketplace:
 - For data providers: [Unified ID 2.0: Data Provider Identity Solution](https://app.snowflake.com/marketplace/listing/GZT0ZRYXTN0/unified-id-2-0-unified-id-2-0-data-provider-identity-solution?originTab=provider&providerName=Unified+ID+2.0)
 
 :::tip
-For a summary of UID2 integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md).
+For a summary of all integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md).
 :::
 
 ## Functionality

docs/guides/snowflake_integration.md

@@ -1,20 +1,20 @@
 ---
-title: Advertiser/Data Provider Integration by Calling to HTTP Endpoints
+title: Advertiser/Data Provider Integration Directly to HTTP Endpoints
 sidebar_label: HTTP Endpoints
-description: Integration for organizations that collect user data and push it to other participants.
+description: Integration for organizations that collect user data and push it to other participants, coding to HTTP endpoints rather than an SDK or Snowflake.
 hide_table_of_contents: false
 sidebar_position: 07
 displayed_sidebar: sidebarAdvertisers
 ---
 
 import Link from '@docusaurus/Link';
 
-# Advertiser/Data Provider Integration By Calling HTTP Endpoints
+# Advertiser/Data Provider Integration Directly to HTTP Endpoints
 
 This guide covers integration steps for advertisers and data providers to integration by writing code to call UID2 HTTP endpoints, rather than using another implementation options such as an SDK, Snowflake, or AWS Entity Resolution.
 
 :::tip
-For a summary of UID2 integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md).
+For a summary of all integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md).
 :::
 
 ### High-Level Steps

i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-advertiser-dataprovider-endpoints.md

@@ -31,6 +31,19 @@ There are other ways that you can use UID2, outside these use cases. These are j
 - **Send in conversions**: You can send UID2s as conversion information that can be used for measurement (attribution) or retargeting via API or pixels
 - **Receive graph data**: You can receive UID2s from graph/data providers via API or pixels. -->
 
+## Summary of Implementation Options
+
+The following table shows the implementation options that are available for advertisers and data providers, for each of the high-level steps. Some steps are managed solely as part of your own custom implementation; some steps can be managed by one or more of the UID2 implementation options available. Click through on each option for applicable documentation.
+
+| High-Level Step | Implementation Options |
+| --- | --- |
+| 1. Generate a raw UID2 | Any of the following options:<ul><li>Python SDK: see <Link href="../sdks/sdk-ref-python">SDK for Python Reference Guide</Link></li><li>Raw HTTP endpoint: <Link href="../endpoints/post-identity-map">POST /identity/map</Link></li><li>Snowflake: see <Link href="snowflake_integration">Snowflake Integration Guide</Link>, section titled <Link href="snowflake_integration#map-dii">Map DII</Link></li><li>AWS Entity Resolution: see <Link href="integration-aws-entity-resolution">AWS Entity Resolution Integration Guide</Link></li></ul> |
+| 2. Manipulate or combine raw UID2s | Custom (your choice) |
+| 3. Use the raw UID2s | Custom (your choice) |
+| 4. Store raw UID2s and salt bucket IDs | Custom (your choice) |
+| 5. Monitor for salt bucket rotation | Any of the following options:<ul><li>Python SDK: see <Link href="../sdks/sdk-ref-python">SDK for Python Reference Guide</Link></li><li>Raw HTTP endpoint: <Link href="../endpoints/post-identity-buckets">POST /identity/buckets</Link></li><li>Snowflake: see <Link href="snowflake_integration">Snowflake Integration Guide</Link>, section titled <Link href="snowflake_integration#monitor-for-salt-bucket-rotation-and-regenerate-raw-uid2s">Monitor for Salt Bucket Rotation and Regenerate Raw UID2s</Link></li></ul> |
+| 6. Monitor for opt-out status | API call to the [POST /optout/status](../endpoints/post-optout-status.md) endpoint: see [Check Opt-Out Status](#check-opt-out-status) |
+
 ## High-Level Steps
 
 At a high level, the steps for advertisers and data providers integrating with UID2 are as follows:
@@ -52,19 +65,6 @@ At a high level, the steps for advertisers and data providers integrating with U
 
 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 [Check Opt-Out Status](#check-opt-out-status).
 
-## Summary of Implementation Options
-
-The following table shows the implementation options that are available for advertisers and data providers, for each of the high-level steps. Some steps are managed solely as part of your own custom implementation; some steps can be managed by one or more of the UID2 implementation options available. Click through on each option for applicable documentation.
-
-| High-Level Step | Implementation Options |
-| --- | --- |
-| 1. Generate a raw UID2 | Any of the following options:<ul><li>Python SDK: see <Link href="../sdks/sdk-ref-python">SDK for Python Reference Guide</Link></li><li>Raw HTTP endpoint: <Link href="../endpoints/post-identity-map">POST /identity/map</Link></li><li>Snowflake: see <Link href="snowflake_integration">Snowflake Integration Guide</Link>, section titled <Link href="snowflake_integration#map-dii">Map DII</Link></li><li>AWS Entity Resolution: see <Link href="integration-aws-entity-resolution">AWS Entity Resolution Integration Guide</Link></li></ul> |
-| 2. Manipulate or combine raw UID2s | Custom (your choice) |
-| 3. Use the raw UID2s | Custom (your choice) |
-| 4. Store raw UID2s and salt bucket IDs | Custom (your choice) |
-| 5. Monitor for salt bucket rotation | Any of the following options:<ul><li>Python SDK: see <Link href="../sdks/sdk-ref-python">SDK for Python Reference Guide</Link></li><li>Raw HTTP endpoint: <Link href="../endpoints/post-identity-buckets">POST /identity/buckets</Link></li><li>Snowflake: see <Link href="snowflake_integration">Snowflake Integration Guide</Link>, section titled <Link href="snowflake_integration#monitor-for-salt-bucket-rotation-and-regenerate-raw-uid2s">Monitor for Salt Bucket Rotation and Regenerate Raw UID2s</Link></li></ul> |
-| 6. Monitor for opt-out status | API call to the [POST /optout/status](../endpoints/post-optout-status.md) endpoint: see [Check Opt-Out Status](#check-opt-out-status) |
-
 ## Integration Diagram
 
 The following diagram outlines the steps that data collectors must complete to map DII to raw UID2s for audience building and targeting.