From 510a8eef6cc3b94122e07f21fd83994c1da12359 Mon Sep 17 00:00:00 2001 From: vishal egbert Date: Thu, 4 Dec 2025 11:04:51 +1100 Subject: [PATCH 1/6] Clarify refresh timestamp behavior --- docs/endpoints/post-identity-map.md | 4 ++++ docs/getting-started/gs-faqs.md | 2 +- .../integration-advertiser-dataprovider-endpoints.md | 6 ++++-- .../integration-advertiser-dataprovider-overview.md | 6 ++++-- docs/guides/integration-databricks.md | 4 ++++ docs/guides/integration-snowflake.md | 4 ++++ docs/sdks/sdk-ref-java.md | 8 +++++++- docs/sdks/sdk-ref-python.md | 6 +++++- 8 files changed, 33 insertions(+), 7 deletions(-) diff --git a/docs/endpoints/post-identity-map.md b/docs/endpoints/post-identity-map.md index 53fddb9ed..aa5a685ed 100644 --- a/docs/endpoints/post-identity-map.md +++ b/docs/endpoints/post-identity-map.md @@ -178,6 +178,10 @@ For successfully mapped DII, the mapped object includes the properties shown in | `p` | string | One of the following: | | `r` | number | The Unix timestamp (in milliseconds) that indicates when the raw UID2 might be refreshed. The raw UID2 is guaranteed to be valid until this timestamp. | +:::note +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. +::: + For unsuccessfully mapped input values, the mapped object includes the properties shown in the following table. | Property | Data Type | Description | diff --git a/docs/getting-started/gs-faqs.md b/docs/getting-started/gs-faqs.md index 5e9edcbe6..93a289cdc 100644 --- a/docs/getting-started/gs-faqs.md +++ b/docs/getting-started/gs-faqs.md @@ -198,7 +198,7 @@ To determine whether to refresh a raw UID2: 2. If the current time is greater than or equal to the refresh timestamp, regenerate the raw UID2 by calling the identity map endpoint again with the same DII. :::note -We recommend checking for refresh opportunities daily. It is guaranteed that the raw UID2 won't refresh before the indicated timestamp. At some point on or after that time, the raw UID2 is refreshed. +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. We recommend checking for refresh opportunities daily. ::: #### How often should raw UID2s be refreshed for incremental updates? diff --git a/docs/guides/integration-advertiser-dataprovider-endpoints.md b/docs/guides/integration-advertiser-dataprovider-endpoints.md index c4d7948c4..38af6dee0 100644 --- a/docs/guides/integration-advertiser-dataprovider-endpoints.md +++ b/docs/guides/integration-advertiser-dataprovider-endpoints.md @@ -93,9 +93,11 @@ You could also send conversion information via API or pixels for measurement (at ### 5: Monitor for Raw UID2 Refresh -A raw UID2 is an identifier for a user at a specific moment in time. The raw UID2 for a specific user changes roughly once per year as part of the UID2 refresh process. +A raw UID2 is an identifier for a user at a specific moment in time. The raw UID2 for a specific user rotates roughly once per year as part of the UID2 refresh process. -The v3 Identity Map API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might refresh. Use this timestamp to determine when to regenerate raw UID2s for your stored data. It is guaranteed that it won't refresh before that time. +The v3 Identity Map API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might rotate. Use this timestamp to determine when to regenerate raw UID2s for your stored data. + +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. We recommend checking for refresh opportunities daily. The following table shows the steps for monitoring raw UID2 refresh. diff --git a/docs/guides/integration-advertiser-dataprovider-overview.md b/docs/guides/integration-advertiser-dataprovider-overview.md index f30bb6524..971468bdf 100644 --- a/docs/guides/integration-advertiser-dataprovider-overview.md +++ b/docs/guides/integration-advertiser-dataprovider-overview.md @@ -121,9 +121,11 @@ You could also send conversion information via API or pixels for measurement (at ### 5: Monitor for Raw UID2 Refresh -A raw UID2 is an identifier for a user at a specific moment in time. The raw UID2 for a specific user changes roughly once per year as part of the UID2 refresh process. +A raw UID2 is an identifier for a user at a specific moment in time. The raw UID2 for a specific user rotates roughly once per year as part of the UID2 refresh process. -The v3 Identity Map API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might refresh. Use this timestamp to determine when to regenerate raw UID2s for your stored data. It is guaranteed that it won't refresh before that time. +The v3 Identity Map API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might rotate. Use this timestamp to determine when to regenerate raw UID2s for your stored data. + +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. We recommend checking for refresh opportunities daily. To determine whether to refresh a raw UID2: diff --git a/docs/guides/integration-databricks.md b/docs/guides/integration-databricks.md index 5104e0716..8537bb58b 100644 --- a/docs/guides/integration-databricks.md +++ b/docs/guides/integration-databricks.md @@ -142,6 +142,10 @@ The following table provides information about the structure of the output data, | `REFRESH_FROM` | timestamp | The value is one of the following: | | `UNMAPPED` | string | The value is one of the following: | +:::note +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. +::: + #### Values for the UNMAPPED Column The following table shows possible values for the `UNMAPPED` column in the output table schema. diff --git a/docs/guides/integration-snowflake.md b/docs/guides/integration-snowflake.md index e0a308f5c..7bec3edf6 100644 --- a/docs/guides/integration-snowflake.md +++ b/docs/guides/integration-snowflake.md @@ -387,6 +387,10 @@ The following table identifies each item in the response, including `NULL` value The `FN_T_IDENTITY_MAP_V3` function returns refresh timestamps (`REFRESH_FROM`) that indicate when each UID2 should be refreshed. +:::note +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. +::: + To determine which UID2s need regeneration, compare the current time to the `REFRESH_FROM` timestamps returned by the function. | Column Name | Data Type | Description | diff --git a/docs/sdks/sdk-ref-java.md b/docs/sdks/sdk-ref-java.md index bfc5353d9..8a9d5d8c2 100644 --- a/docs/sdks/sdk-ref-java.md +++ b/docs/sdks/sdk-ref-java.md @@ -332,6 +332,10 @@ For the earlier version, see [Previous SDK Version (using POST /identity/map v2) .withHashedPhone("preHashedPhone"); ``` +:::note +The SDK automatically handles email normalization and hashing, ensuring that raw email addresses and phone numbers do not leave your server. +::: + 3. Call a function that takes the `input` and generates an IdentityMapV3Response object: ```java IdentityMapV3Response identityMapResponse = identityMapV3Client.generateIdentityMap(input); @@ -356,7 +360,9 @@ For the earlier version, see [Previous SDK Version (using POST /identity/map v2) } ``` ->**Note:** The SDK automatically handles email normalization and hashing, ensuring that raw email addresses and phone numbers do not leave your server. +:::note +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. +::: ### Usage Example diff --git a/docs/sdks/sdk-ref-python.md b/docs/sdks/sdk-ref-python.md index 2d09cac4c..e14afc864 100644 --- a/docs/sdks/sdk-ref-python.md +++ b/docs/sdks/sdk-ref-python.md @@ -255,6 +255,10 @@ To map DII to raw UID2s, follow these steps: .with_hashed_phone("pre_hashed_phone") ``` +:::note +The SDK automatically handles email normalization and hashing, ensuring that raw email addresses and phone numbers do not leave your server. +::: + 3. Call a function that takes the `input` and generates an `IdentityMapV3Response` object: ```py identity_map_response = identity_map_v3_client.generate_identity_map(input) @@ -279,7 +283,7 @@ To map DII to raw UID2s, follow these steps: ``` :::note -The SDK automatically handles email normalization and hashing, ensuring that raw email addresses and phone numbers do not leave your server. +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. ::: #### Usage Example From 7053224af331dab001f7bd28037d70a4afb3d5f3 Mon Sep 17 00:00:00 2001 From: vishal egbert Date: Thu, 4 Dec 2025 15:59:34 +1100 Subject: [PATCH 2/6] Update wording --- docs/endpoints/post-identity-map.md | 2 +- docs/getting-started/gs-faqs.md | 2 +- docs/guides/integration-advertiser-dataprovider-endpoints.md | 2 +- docs/guides/integration-advertiser-dataprovider-overview.md | 2 +- docs/guides/integration-databricks.md | 2 +- docs/guides/integration-snowflake.md | 2 +- docs/sdks/sdk-ref-java.md | 2 +- docs/sdks/sdk-ref-python.md | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/endpoints/post-identity-map.md b/docs/endpoints/post-identity-map.md index aa5a685ed..822cd564d 100644 --- a/docs/endpoints/post-identity-map.md +++ b/docs/endpoints/post-identity-map.md @@ -179,7 +179,7 @@ For successfully mapped DII, the mapped object includes the properties shown in | `r` | number | The Unix timestamp (in milliseconds) that indicates when the raw UID2 might be refreshed. The raw UID2 is guaranteed to be valid until this timestamp. | :::note -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. ::: For unsuccessfully mapped input values, the mapped object includes the properties shown in the following table. diff --git a/docs/getting-started/gs-faqs.md b/docs/getting-started/gs-faqs.md index 93a289cdc..f63ad0b02 100644 --- a/docs/getting-started/gs-faqs.md +++ b/docs/getting-started/gs-faqs.md @@ -198,7 +198,7 @@ To determine whether to refresh a raw UID2: 2. If the current time is greater than or equal to the refresh timestamp, regenerate the raw UID2 by calling the identity map endpoint again with the same DII. :::note -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. We recommend checking for refresh opportunities daily. +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. ::: #### How often should raw UID2s be refreshed for incremental updates? diff --git a/docs/guides/integration-advertiser-dataprovider-endpoints.md b/docs/guides/integration-advertiser-dataprovider-endpoints.md index 38af6dee0..110aee4c2 100644 --- a/docs/guides/integration-advertiser-dataprovider-endpoints.md +++ b/docs/guides/integration-advertiser-dataprovider-endpoints.md @@ -97,7 +97,7 @@ A raw UID2 is an identifier for a user at a specific moment in time. The raw UID The v3 Identity Map API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might rotate. Use this timestamp to determine when to regenerate raw UID2s for your stored data. -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. We recommend checking for refresh opportunities daily. The following table shows the steps for monitoring raw UID2 refresh. diff --git a/docs/guides/integration-advertiser-dataprovider-overview.md b/docs/guides/integration-advertiser-dataprovider-overview.md index 971468bdf..8da624d46 100644 --- a/docs/guides/integration-advertiser-dataprovider-overview.md +++ b/docs/guides/integration-advertiser-dataprovider-overview.md @@ -125,7 +125,7 @@ A raw UID2 is an identifier for a user at a specific moment in time. The raw UID The v3 Identity Map API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might rotate. Use this timestamp to determine when to regenerate raw UID2s for your stored data. -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. We recommend checking for refresh opportunities daily. To determine whether to refresh a raw UID2: diff --git a/docs/guides/integration-databricks.md b/docs/guides/integration-databricks.md index 8537bb58b..5ae57e804 100644 --- a/docs/guides/integration-databricks.md +++ b/docs/guides/integration-databricks.md @@ -143,7 +143,7 @@ The following table provides information about the structure of the output data, | `UNMAPPED` | string | The value is one of the following: | :::note -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. ::: #### Values for the UNMAPPED Column diff --git a/docs/guides/integration-snowflake.md b/docs/guides/integration-snowflake.md index 7bec3edf6..b35356429 100644 --- a/docs/guides/integration-snowflake.md +++ b/docs/guides/integration-snowflake.md @@ -388,7 +388,7 @@ The following table identifies each item in the response, including `NULL` value The `FN_T_IDENTITY_MAP_V3` function returns refresh timestamps (`REFRESH_FROM`) that indicate when each UID2 should be refreshed. :::note -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. ::: To determine which UID2s need regeneration, compare the current time to the `REFRESH_FROM` timestamps returned by the function. diff --git a/docs/sdks/sdk-ref-java.md b/docs/sdks/sdk-ref-java.md index 8a9d5d8c2..f4eda0a76 100644 --- a/docs/sdks/sdk-ref-java.md +++ b/docs/sdks/sdk-ref-java.md @@ -361,7 +361,7 @@ The SDK automatically handles email normalization and hashing, ensuring that raw ``` :::note -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. ::: ### Usage Example diff --git a/docs/sdks/sdk-ref-python.md b/docs/sdks/sdk-ref-python.md index e14afc864..88208d47c 100644 --- a/docs/sdks/sdk-ref-python.md +++ b/docs/sdks/sdk-ref-python.md @@ -283,7 +283,7 @@ The SDK automatically handles email normalization and hashing, ensuring that raw ``` :::note -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. This is by design to encourage more frequent checks of the opt-out status of the underlying DII. +It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. ::: #### Usage Example From 20b31a85ff249a0114ab93bf5be4ddcc87862ecc Mon Sep 17 00:00:00 2001 From: vishal egbert Date: Thu, 4 Dec 2025 23:44:34 +1100 Subject: [PATCH 3/6] Update wording --- docs/endpoints/post-identity-map.md | 2 +- docs/getting-started/gs-faqs.md | 2 +- docs/guides/integration-advertiser-dataprovider-endpoints.md | 2 +- docs/guides/integration-advertiser-dataprovider-overview.md | 2 +- docs/guides/integration-databricks.md | 2 +- docs/guides/integration-snowflake.md | 2 +- docs/sdks/sdk-ref-java.md | 2 +- docs/sdks/sdk-ref-python.md | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/endpoints/post-identity-map.md b/docs/endpoints/post-identity-map.md index 822cd564d..b5568b108 100644 --- a/docs/endpoints/post-identity-map.md +++ b/docs/endpoints/post-identity-map.md @@ -179,7 +179,7 @@ For successfully mapped DII, the mapped object includes the properties shown in | `r` | number | The Unix timestamp (in milliseconds) that indicates when the raw UID2 might be refreshed. The raw UID2 is guaranteed to be valid until this timestamp. | :::note -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. +The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. ::: For unsuccessfully mapped input values, the mapped object includes the properties shown in the following table. diff --git a/docs/getting-started/gs-faqs.md b/docs/getting-started/gs-faqs.md index f63ad0b02..0c90cc21a 100644 --- a/docs/getting-started/gs-faqs.md +++ b/docs/getting-started/gs-faqs.md @@ -198,7 +198,7 @@ To determine whether to refresh a raw UID2: 2. If the current time is greater than or equal to the refresh timestamp, regenerate the raw UID2 by calling the identity map endpoint again with the same DII. :::note -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. +The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. ::: #### How often should raw UID2s be refreshed for incremental updates? diff --git a/docs/guides/integration-advertiser-dataprovider-endpoints.md b/docs/guides/integration-advertiser-dataprovider-endpoints.md index 110aee4c2..d0a12bccf 100644 --- a/docs/guides/integration-advertiser-dataprovider-endpoints.md +++ b/docs/guides/integration-advertiser-dataprovider-endpoints.md @@ -97,7 +97,7 @@ A raw UID2 is an identifier for a user at a specific moment in time. The raw UID The v3 Identity Map API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might rotate. Use this timestamp to determine when to regenerate raw UID2s for your stored data. -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. +The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. We recommend checking for refresh opportunities daily. The following table shows the steps for monitoring raw UID2 refresh. diff --git a/docs/guides/integration-advertiser-dataprovider-overview.md b/docs/guides/integration-advertiser-dataprovider-overview.md index 8da624d46..df51f5b57 100644 --- a/docs/guides/integration-advertiser-dataprovider-overview.md +++ b/docs/guides/integration-advertiser-dataprovider-overview.md @@ -125,7 +125,7 @@ A raw UID2 is an identifier for a user at a specific moment in time. The raw UID The v3 Identity Map API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might rotate. Use this timestamp to determine when to regenerate raw UID2s for your stored data. -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. +The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. We recommend checking for refresh opportunities daily. To determine whether to refresh a raw UID2: diff --git a/docs/guides/integration-databricks.md b/docs/guides/integration-databricks.md index 5ae57e804..22378c0bb 100644 --- a/docs/guides/integration-databricks.md +++ b/docs/guides/integration-databricks.md @@ -143,7 +143,7 @@ The following table provides information about the structure of the output data, | `UNMAPPED` | string | The value is one of the following:
  • **DII was successfully mapped**: `NULL`.
  • **Otherwise**: The reason why the identifier was not mapped: `OPTOUT`, `INVALID IDENTIFIER`, or `INVALID INPUT TYPE`.
    For details, see [Values for the UNMAPPED Column](#values-for-the-unmapped-column).
| :::note -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. +The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. ::: #### Values for the UNMAPPED Column diff --git a/docs/guides/integration-snowflake.md b/docs/guides/integration-snowflake.md index b35356429..d2d3c2271 100644 --- a/docs/guides/integration-snowflake.md +++ b/docs/guides/integration-snowflake.md @@ -388,7 +388,7 @@ The following table identifies each item in the response, including `NULL` value The `FN_T_IDENTITY_MAP_V3` function returns refresh timestamps (`REFRESH_FROM`) that indicate when each UID2 should be refreshed. :::note -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. +The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. ::: To determine which UID2s need regeneration, compare the current time to the `REFRESH_FROM` timestamps returned by the function. diff --git a/docs/sdks/sdk-ref-java.md b/docs/sdks/sdk-ref-java.md index f4eda0a76..b3eafce13 100644 --- a/docs/sdks/sdk-ref-java.md +++ b/docs/sdks/sdk-ref-java.md @@ -361,7 +361,7 @@ The SDK automatically handles email normalization and hashing, ensuring that raw ``` :::note -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. +The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. ::: ### Usage Example diff --git a/docs/sdks/sdk-ref-python.md b/docs/sdks/sdk-ref-python.md index 88208d47c..24467ba87 100644 --- a/docs/sdks/sdk-ref-python.md +++ b/docs/sdks/sdk-ref-python.md @@ -283,7 +283,7 @@ The SDK automatically handles email normalization and hashing, ensuring that raw ``` :::note -It is guaranteed that the raw UID2 will not rotate before the refresh timestamp. After the refresh timestamp, when remapping the DII, a new refresh timestamp will be returned but the raw UID2 may not rotate. +The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. ::: #### Usage Example From b97c54b7aa44df9e6dd0d09062649e148549d5ba Mon Sep 17 00:00:00 2001 From: vishal egbert Date: Fri, 5 Dec 2025 21:40:51 +1100 Subject: [PATCH 4/6] Address feedback --- docs/endpoints/post-identity-map.md | 2 +- docs/getting-started/gs-faqs.md | 2 +- .../integration-advertiser-dataprovider-endpoints.md | 4 ++-- .../integration-advertiser-dataprovider-overview.md | 2 +- docs/guides/integration-databricks.md | 2 +- docs/guides/integration-snowflake.md | 2 +- docs/sdks/sdk-ref-java.md | 12 ++++++------ docs/sdks/sdk-ref-python.md | 12 ++++++------ 8 files changed, 19 insertions(+), 19 deletions(-) diff --git a/docs/endpoints/post-identity-map.md b/docs/endpoints/post-identity-map.md index b5568b108..a1af3fab7 100644 --- a/docs/endpoints/post-identity-map.md +++ b/docs/endpoints/post-identity-map.md @@ -179,7 +179,7 @@ For successfully mapped DII, the mapped object includes the properties shown in | `r` | number | The Unix timestamp (in milliseconds) that indicates when the raw UID2 might be refreshed. The raw UID2 is guaranteed to be valid until this timestamp. | :::note -The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. +The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. ::: For unsuccessfully mapped input values, the mapped object includes the properties shown in the following table. diff --git a/docs/getting-started/gs-faqs.md b/docs/getting-started/gs-faqs.md index 0c90cc21a..a0bffde58 100644 --- a/docs/getting-started/gs-faqs.md +++ b/docs/getting-started/gs-faqs.md @@ -198,7 +198,7 @@ To determine whether to refresh a raw UID2: 2. If the current time is greater than or equal to the refresh timestamp, regenerate the raw UID2 by calling the identity map endpoint again with the same DII. :::note -The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. +The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. ::: #### How often should raw UID2s be refreshed for incremental updates? diff --git a/docs/guides/integration-advertiser-dataprovider-endpoints.md b/docs/guides/integration-advertiser-dataprovider-endpoints.md index d0a12bccf..5a63e13a8 100644 --- a/docs/guides/integration-advertiser-dataprovider-endpoints.md +++ b/docs/guides/integration-advertiser-dataprovider-endpoints.md @@ -93,11 +93,11 @@ You could also send conversion information via API or pixels for measurement (at ### 5: Monitor for Raw UID2 Refresh -A raw UID2 is an identifier for a user at a specific moment in time. The raw UID2 for a specific user rotates roughly once per year as part of the UID2 refresh process. +A raw UID2 is an identifier for a user at a specific moment in time. The raw UID2 for a specific user changes roughly once per year as part of the UID2 refresh process. The v3 Identity Map API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might rotate. Use this timestamp to determine when to regenerate raw UID2s for your stored data. -The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. +The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. We recommend checking for refresh opportunities daily. The following table shows the steps for monitoring raw UID2 refresh. diff --git a/docs/guides/integration-advertiser-dataprovider-overview.md b/docs/guides/integration-advertiser-dataprovider-overview.md index df51f5b57..d7d4afbb0 100644 --- a/docs/guides/integration-advertiser-dataprovider-overview.md +++ b/docs/guides/integration-advertiser-dataprovider-overview.md @@ -125,7 +125,7 @@ A raw UID2 is an identifier for a user at a specific moment in time. The raw UID The v3 Identity Map API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might rotate. Use this timestamp to determine when to regenerate raw UID2s for your stored data. -The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. +The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. We recommend checking for refresh opportunities daily. To determine whether to refresh a raw UID2: diff --git a/docs/guides/integration-databricks.md b/docs/guides/integration-databricks.md index 22378c0bb..f1975c727 100644 --- a/docs/guides/integration-databricks.md +++ b/docs/guides/integration-databricks.md @@ -143,7 +143,7 @@ The following table provides information about the structure of the output data, | `UNMAPPED` | string | The value is one of the following:
  • **DII was successfully mapped**: `NULL`.
  • **Otherwise**: The reason why the identifier was not mapped: `OPTOUT`, `INVALID IDENTIFIER`, or `INVALID INPUT TYPE`.
    For details, see [Values for the UNMAPPED Column](#values-for-the-unmapped-column).
| :::note -The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. +The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. ::: #### Values for the UNMAPPED Column diff --git a/docs/guides/integration-snowflake.md b/docs/guides/integration-snowflake.md index d2d3c2271..0922fcd3d 100644 --- a/docs/guides/integration-snowflake.md +++ b/docs/guides/integration-snowflake.md @@ -388,7 +388,7 @@ The following table identifies each item in the response, including `NULL` value The `FN_T_IDENTITY_MAP_V3` function returns refresh timestamps (`REFRESH_FROM`) that indicate when each UID2 should be refreshed. :::note -The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. +The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. ::: To determine which UID2s need regeneration, compare the current time to the `REFRESH_FROM` timestamps returned by the function. diff --git a/docs/sdks/sdk-ref-java.md b/docs/sdks/sdk-ref-java.md index b3eafce13..09ec28ef7 100644 --- a/docs/sdks/sdk-ref-java.md +++ b/docs/sdks/sdk-ref-java.md @@ -332,9 +332,9 @@ For the earlier version, see [Previous SDK Version (using POST /identity/map v2) .withHashedPhone("preHashedPhone"); ``` -:::note -The SDK automatically handles email normalization and hashing, ensuring that raw email addresses and phone numbers do not leave your server. -::: + :::note + The SDK automatically handles email normalization and hashing, ensuring that raw email addresses and phone numbers do not leave your server. + ::: 3. Call a function that takes the `input` and generates an IdentityMapV3Response object: ```java @@ -360,9 +360,9 @@ The SDK automatically handles email normalization and hashing, ensuring that raw } ``` -:::note -The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. -::: + :::note + The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. + ::: ### Usage Example diff --git a/docs/sdks/sdk-ref-python.md b/docs/sdks/sdk-ref-python.md index 24467ba87..576d346db 100644 --- a/docs/sdks/sdk-ref-python.md +++ b/docs/sdks/sdk-ref-python.md @@ -255,9 +255,9 @@ To map DII to raw UID2s, follow these steps: .with_hashed_phone("pre_hashed_phone") ``` -:::note -The SDK automatically handles email normalization and hashing, ensuring that raw email addresses and phone numbers do not leave your server. -::: + :::note + The SDK automatically handles email normalization and hashing, ensuring that raw email addresses and phone numbers do not leave your server. + ::: 3. Call a function that takes the `input` and generates an `IdentityMapV3Response` object: ```py @@ -282,9 +282,9 @@ The SDK automatically handles email normalization and hashing, ensuring that raw reason = unmapped_identity.reason # OPTOUT, INVALID_IDENTIFIER, or UNKNOWN ``` -:::note -The raw UID2 is guaranteed not to rotate before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 may remain unchanged across multiple refresh cycles. The raw UID2 will eventually rotate after approximately one year. -::: + :::note + The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. + ::: #### Usage Example From 506fdb697978873af44859efa2c5b2bbadf40b88 Mon Sep 17 00:00:00 2001 From: vishal egbert Date: Fri, 5 Dec 2025 22:03:53 +1100 Subject: [PATCH 5/6] Address feedback --- docs/guides/integration-advertiser-dataprovider-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/integration-advertiser-dataprovider-overview.md b/docs/guides/integration-advertiser-dataprovider-overview.md index d7d4afbb0..882d6e19e 100644 --- a/docs/guides/integration-advertiser-dataprovider-overview.md +++ b/docs/guides/integration-advertiser-dataprovider-overview.md @@ -121,7 +121,7 @@ You could also send conversion information via API or pixels for measurement (at ### 5: Monitor for Raw UID2 Refresh -A raw UID2 is an identifier for a user at a specific moment in time. The raw UID2 for a specific user rotates roughly once per year as part of the UID2 refresh process. +A raw UID2 is an identifier for a user at a specific moment in time. The raw UID2 for a specific user changes roughly once per year as part of the UID2 refresh process. The v3 Identity Map API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might rotate. Use this timestamp to determine when to regenerate raw UID2s for your stored data. From ca36389b69f964e9758a3879228a7b4d794daaee Mon Sep 17 00:00:00 2001 From: genwhittTTD Date: Fri, 5 Dec 2025 11:43:50 -0500 Subject: [PATCH 6/6] update expiration wording per Slack thread --- docs/endpoints/post-identity-map.md | 2 +- docs/getting-started/gs-faqs.md | 2 +- docs/guides/integration-advertiser-dataprovider-endpoints.md | 2 +- docs/guides/integration-advertiser-dataprovider-overview.md | 2 +- docs/guides/integration-databricks.md | 2 +- docs/guides/integration-snowflake.md | 2 +- docs/ref-info/glossary-uid.md | 4 ++-- docs/sdks/sdk-ref-java.md | 2 +- docs/sdks/sdk-ref-python.md | 2 +- .../current/sdks/sdk-ref-java.md | 2 +- 10 files changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/endpoints/post-identity-map.md b/docs/endpoints/post-identity-map.md index a1af3fab7..d9ba3e11e 100644 --- a/docs/endpoints/post-identity-map.md +++ b/docs/endpoints/post-identity-map.md @@ -179,7 +179,7 @@ For successfully mapped DII, the mapped object includes the properties shown in | `r` | number | The Unix timestamp (in milliseconds) that indicates when the raw UID2 might be refreshed. The raw UID2 is guaranteed to be valid until this timestamp. | :::note -The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. +The raw UID2 does not change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. ::: For unsuccessfully mapped input values, the mapped object includes the properties shown in the following table. diff --git a/docs/getting-started/gs-faqs.md b/docs/getting-started/gs-faqs.md index a0bffde58..96092f99e 100644 --- a/docs/getting-started/gs-faqs.md +++ b/docs/getting-started/gs-faqs.md @@ -198,7 +198,7 @@ To determine whether to refresh a raw UID2: 2. If the current time is greater than or equal to the refresh timestamp, regenerate the raw UID2 by calling the identity map endpoint again with the same DII. :::note -The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. +The raw UID2 does not change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. ::: #### How often should raw UID2s be refreshed for incremental updates? diff --git a/docs/guides/integration-advertiser-dataprovider-endpoints.md b/docs/guides/integration-advertiser-dataprovider-endpoints.md index 5a63e13a8..6a0e92c4f 100644 --- a/docs/guides/integration-advertiser-dataprovider-endpoints.md +++ b/docs/guides/integration-advertiser-dataprovider-endpoints.md @@ -97,7 +97,7 @@ A raw UID2 is an identifier for a user at a specific moment in time. The raw UID The v3 Identity Map API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might rotate. Use this timestamp to determine when to regenerate raw UID2s for your stored data. -The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. +The raw UID2 does not change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. We recommend checking for refresh opportunities daily. The following table shows the steps for monitoring raw UID2 refresh. diff --git a/docs/guides/integration-advertiser-dataprovider-overview.md b/docs/guides/integration-advertiser-dataprovider-overview.md index 882d6e19e..5196c7d5d 100644 --- a/docs/guides/integration-advertiser-dataprovider-overview.md +++ b/docs/guides/integration-advertiser-dataprovider-overview.md @@ -125,7 +125,7 @@ A raw UID2 is an identifier for a user at a specific moment in time. The raw UID The v3 Identity Map API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might rotate. Use this timestamp to determine when to regenerate raw UID2s for your stored data. -The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. +The raw UID2 does not change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. We recommend checking for refresh opportunities daily. To determine whether to refresh a raw UID2: diff --git a/docs/guides/integration-databricks.md b/docs/guides/integration-databricks.md index f1975c727..da1985502 100644 --- a/docs/guides/integration-databricks.md +++ b/docs/guides/integration-databricks.md @@ -143,7 +143,7 @@ The following table provides information about the structure of the output data, | `UNMAPPED` | string | The value is one of the following:
  • **DII was successfully mapped**: `NULL`.
  • **Otherwise**: The reason why the identifier was not mapped: `OPTOUT`, `INVALID IDENTIFIER`, or `INVALID INPUT TYPE`.
    For details, see [Values for the UNMAPPED Column](#values-for-the-unmapped-column).
| :::note -The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. +The raw UID2 does not change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. ::: #### Values for the UNMAPPED Column diff --git a/docs/guides/integration-snowflake.md b/docs/guides/integration-snowflake.md index 0922fcd3d..18b83bc52 100644 --- a/docs/guides/integration-snowflake.md +++ b/docs/guides/integration-snowflake.md @@ -388,7 +388,7 @@ The following table identifies each item in the response, including `NULL` value The `FN_T_IDENTITY_MAP_V3` function returns refresh timestamps (`REFRESH_FROM`) that indicate when each UID2 should be refreshed. :::note -The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. +The raw UID2 does not change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. ::: To determine which UID2s need regeneration, compare the current time to the `REFRESH_FROM` timestamps returned by the function. diff --git a/docs/ref-info/glossary-uid.md b/docs/ref-info/glossary-uid.md index 2c2c663f2..0d51e6db9 100644 --- a/docs/ref-info/glossary-uid.md +++ b/docs/ref-info/glossary-uid.md @@ -421,8 +421,8 @@ import MdxJumpAnchor from '@site/src/components/MdxJumpAnchor';
The UID2 service uses salt as part of the process, along with hashing and encryption, to secure the original value. Salt is added to the input value before hashing.
Salt bucket
-
A salt bucket is used to manage secret salt values, used to generate raw UID2s or UID2 tokens, over time. Each bucket contains a single current salt value, which remains active for approximately one year before being rotated to a new value. Buckets can be updated independently of one another.
-
There are just over one million salt buckets, and each email address or phone number is assigned to a specific bucket in a deterministic manner. However, this assignment is not permanent; it might change when the bucket's current salt is rotated to a new value.
+
A salt bucket is used to manage secret salt values, used to generate raw UID2s or UID2 tokens, over time. Each bucket contains a single current salt value, which remains active for a period of time before being rotated to a new value. Buckets can be updated independently of one another.
+
There are over one million salt buckets, and each email address or phone number is assigned to a specific bucket in a deterministic manner. However, this assignment is not permanent; it might change when the bucket's current salt is rotated to a new value.
In versions of the [POST /identity/map](../endpoints/post-identity-map.md) endpoint earlier than version 3, such as [POST /identity/map (v2)](../endpoints/post-identity-map-v2.md), the endpoint returns salt bucket IDs. In v3 and later, salt bucket information is not needed.
Salt bucket ID
diff --git a/docs/sdks/sdk-ref-java.md b/docs/sdks/sdk-ref-java.md index 09ec28ef7..5298f7210 100644 --- a/docs/sdks/sdk-ref-java.md +++ b/docs/sdks/sdk-ref-java.md @@ -361,7 +361,7 @@ For the earlier version, see [Previous SDK Version (using POST /identity/map v2) ``` :::note - The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. + The raw UID2 does not change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. ::: ### Usage Example diff --git a/docs/sdks/sdk-ref-python.md b/docs/sdks/sdk-ref-python.md index 576d346db..49a297fb7 100644 --- a/docs/sdks/sdk-ref-python.md +++ b/docs/sdks/sdk-ref-python.md @@ -283,7 +283,7 @@ To map DII to raw UID2s, follow these steps: ``` :::note - The raw UID2 is guaranteed not to change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. + The raw UID2 does not change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. ::: #### Usage Example diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-java.md b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-java.md index 3d6283c8e..a526aa2db 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-java.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-java.md @@ -319,7 +319,7 @@ Server-Side Integration ([Publisher Integration Guide, Server-Side](../guides/in IdentityMapV3Input input = IdentityMapV3Input.fromEmails(Arrays.asList("user@example.com", "user2@example.com")); ``` - 複数の ID タイプを組み合わせることもできます: + 複数の ID タイプを組み合わせることもできます: ```java IdentityMapV3Input input = new IdentityMapV3Input() .withEmail("user@example.com")