Merge branch 'main' into jpn-translation-update-887-913

Author: miyaichi

.idea/.gitignore

@@ -19,8 +19,8 @@ For details about the UID2 opt-out workflow and how users can opt out, see [User
 
 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.md).
 
-:::important
-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.md#migration-from-v2-identity-map). For deprecation information, see [Deprecation Schedule: Endpoint Versions](../ref-info/deprecation-schedule.md#endpoint-versions).
+:::note
+If you're using an earlier 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.md#migration-from-v2-identity-map). For deprecation information, see [Deprecation Schedule: Endpoint Versions](../ref-info/deprecation-schedule.md#endpoint-versions).
 :::
 
 ## Batch Size and Request Parallelization Requirements

docs/endpoints/post-identity-map-v2.md

@@ -213,7 +213,7 @@ The following sections provide general information and guidance for migrating to
 
 The following table shows key differences between the versions.
 
-| Feature                        | V2 Implementation                           | V3 Implementation                          |
+| Feature                        | v2 Implementation                           | v3 Implementation                          |
 |:-------------------------------|:--------------------------------------------|:-------------------------------------------|
 | Endpoints Required         | `/v2/identity/map` + `/v2/identity/buckets` | `/v3/identity/map` only                    |
 | Identity Types per Request | Single identity type only                   | Multiple identity types                    |
@@ -225,7 +225,7 @@ The following table shows key differences between the versions.
 To upgrade from an earlier version to version 3, follow these steps:
 
 1. [Update Endpoint URL](#1-update-endpoint-url)
-2. [Update V3 Response Parsing Logic](#2-update-v3-response-parsing-logic)
+2. [Update v3 Response Parsing Logic](#2-update-v3-response-parsing-logic)
 3. [Replace Salt Bucket Monitoring with Refresh Timestamp Logic](#3-replace-salt-bucket-monitoring-with-refresh-timestamp-logic)
 
 #### 1. Update Endpoint URL
@@ -244,7 +244,7 @@ url = '/v3/identity/map'
 
 Update the logic for parsing the response, as shown in the following example.
 
-V2 Response Parsing:
+v2 Response Parsing:
 ```python
 # v2: Process mapped/unmapped objects with identifier lookup
 for item in response['body']['mapped']:
@@ -255,7 +255,7 @@ for item in response['body']['mapped']:
     store_mapping(original_identifier, raw_uid, bucket_id)
 ```
 
-V3 Response Parsing:
+v3 Response Parsing:
 ```python
 # v3: Process array-indexed responses
 for index, item in enumerate(response['body']['email']):

docs/endpoints/post-identity-map.md

@@ -191,10 +191,12 @@ For instructions for monitoring for salt bucket rotations, refer to one of the f
 
 - Python SDK: [Monitor Rotated Salt Buckets](../sdks/sdk-ref-python.md#monitor-rotated-salt-buckets).
 
-- Snowflake: [Monitor for Salt Bucket Rotation and Regenerate Raw UID2s](integration-snowflake.md#monitor-for-salt-bucket-rotation-and-regenerate-raw-uid2s).
+- Snowflake: [Monitor for Salt Bucket Rotation and Regenerate Raw UID2s](integration-snowflake-previous#monitor-for-salt-bucket-rotation-and-regenerate-raw-uid2s).
 
 - HTTP endpoints: [Monitor for Salt Bucket Rotations for Your Stored Raw UID2s (v2)](integration-advertiser-dataprovider-endpoints.md#monitor-for-salt-bucket-rotations-for-your-stored-raw-uid2s-v2).
 
+<!-- GWH_Note 8/4/25 I took the .md out of the Snowflake link line 194 because Docu would not build it correctly... broken link in output. Do not know why, though. Same thing on 2 links -->
+
 :::note
 For AWS Entity Resolution, there is no way to do salt bucket monitoring. As an alternative, you could regenerate raw UID2s periodically using the AWS Entity Resolution service.
 :::

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

@@ -41,7 +41,7 @@ The latest ZIP file is available in the Assets section at the bottom of the link
 | Q3 2024 | [v5.38.104](https://github.com/IABTechLab/uid2-operator/releases/tag/v5.38.104) | 5.38.104 | September 12, 2024 | Mar 31, 2026 |
 | Q2 2024 | [v5.37.12](https://github.com/IABTechLab/uid2-operator/releases/tag/v5.37.12) | 5.37.12 | June 12, 2024 | Sep 30, 2025 |
 
-For documentation, see [UID2 Private Operator for AWS Integration Guide](..\guides\operator-guide-aws-marketplace.md).
+For documentation, see [UID2 Private Operator for AWS Integration Guide](../guides/operator-guide-aws-marketplace.md).
 
 ### Private Operator for GCP
 
@@ -55,7 +55,7 @@ The latest ZIP file is linked in the GCP Download column in the following table.
 | Q3 2024 | [v5.38.104](https://github.com/IABTechLab/uid2-operator/releases/tag/v5.38.104) | [gcp-oidc-deployment-files-5.38.104.zip](https://github.com/IABTechLab/uid2-operator/releases/download/v5.38.104/gcp-oidc-deployment-files-5.38.104.zip) | September 12, 2024 | Mar 31, 2026 |
 | Q2 2024 | [v5.37.12](https://github.com/IABTechLab/uid2-operator/releases/tag/v5.37.12) | [gcp-oidc-deployment-files-5.37.12.zip](https://github.com/IABTechLab/uid2-operator/releases/download/v5.37.12/gcp-oidc-deployment-files-5.37.12.zip) | June 12, 2024 | Sep 30, 2025 |
 
-For documentation, see [UID2 Private Operator for GCP Integration Guide](..\guides\operator-private-gcp-confidential-space.md).
+For documentation, see [UID2 Private Operator for GCP Integration Guide](../guides/operator-private-gcp-confidential-space.md).
 
 ### Private Operator for Azure
 
@@ -69,7 +69,7 @@ The latest ZIP file is linked in the Azure Download column in the following tabl
 | Q3 2024 | [v5.38.104](https://github.com/IABTechLab/uid2-operator/releases/tag/v5.38.104) | [azure-cc-deployment-files-5.38.104.zip](https://github.com/IABTechLab/uid2-operator/releases/download/v5.38.104/azure-cc-deployment-files-5.38.104.zip) | September 12, 2024 | Mar 31, 2026 |
 | Q2 2024 | [v5.37.12](https://github.com/IABTechLab/uid2-operator/releases/tag/v5.37.12) | [azure-cc-deployment-files-5.37.12.zip](https://github.com/IABTechLab/uid2-operator/releases/download/v5.37.12/azure-cc-deployment-files-5.37.12.zip) | June 12, 2024 | Sep 30, 2025 |
 
-For documentation, see [UID2 Private Operator for Azure Integration Guide](..\guides\operator-guide-azure-enclave.md).
+For documentation, see [UID2 Private Operator for Azure Integration Guide](../guides/operator-guide-azure-enclave.md).
 
 <!-- ### Private Operator for AKS
 

docs/guides/integration-snowflake-before-february-2025.md

@@ -26,6 +26,23 @@ The following documents were released in this quarter.
 
 <CustomTagsContainer tags="Endpoints, Guides, SDKs">
 
+### Identity Map v3 (Python SDK, Snowflake)
+
+July 31, 2025
+
+We've released updated versions of two additional docs to reflect adoption of the new version of the Identity Map API (v3), announced 11 July, which provides significant improvements for advertisers and data providers.
+
+We updated the following additional implementations and corresponding documentation:
+
+- Python SDK: see [SDK for Python Reference Guide](../sdks/sdk-ref-python.md)
+- Snowflake: see [Snowflake Integration Guide](../guides/integration-snowflake.md)
+
+<!-- PIDOCS-3320 -->
+
+</CustomTagsContainer>
+
+<CustomTagsContainer tags="Endpoints, Guides, SDKs">
+
 ### Identity Map v3
 
 July 11, 2025

docs/guides/integration-snowflake-previous.md

@@ -56,7 +56,7 @@ The initialization step depends on the role, as shown in the following table.
 | Role                     | Create Instance of Class | Link to Instructions                                                         |
 |:-------------------------| :--- |:-----------------------------------------------------------------------------|
 | Publisher                | `PublisherUid2Client` | [Usage for Publishers](#usage-for-publishers)                                |
-| Advertiser/Data Provider | `IdentityMapClient` | [Usage for Advertisers/Data Providers](#usage-for-advertisersdata-providers) |
+| Advertiser/Data Provider | `IdentityMapV3Client` | [Usage for Advertisers/Data Providers](#usage-for-advertisersdata-providers) |
 | DSP                      | `BidstreamClient` | [Usage for DSPs](#usage-for-dsps)                                            |
 | Sharer                   | `SharingClient` | [Usage for UID2 Sharers](#usage-for-uid2-sharers)                            |
 
@@ -339,7 +339,7 @@ If you're using server-side integration (see [Publisher Integration Guide, Serve
    HashMap<String, IdentityMapV3Response.UnmappedIdentity> unmappedIdentities = identityMapResponse.getUnmappedIdentities();
    ```
 
-5. Process the results. For successfully mapped identities:
+5. Process the results for successfully mapped identities:
    ```java
    IdentityMapV3Response.MappedIdentity mappedIdentity = mappedIdentities.get("[email protected]");
    if (mappedIdentity != null) {