You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/integration-advertiser-dataprovider-overview.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -191,10 +191,12 @@ For instructions for monitoring for salt bucket rotations, refer to one of the f
191
191
192
192
- Python SDK: [Monitor Rotated Salt Buckets](../sdks/sdk-ref-python.md#monitor-rotated-salt-buckets).
193
193
194
-
- Snowflake: [Monitor for Salt Bucket Rotation and Regenerate Raw UID2s](integration-snowflake-before-july-2025.md#monitor-for-salt-bucket-rotation-and-regenerate-raw-uid2s).
194
+
- Snowflake: [Monitor for Salt Bucket Rotation and Regenerate Raw UID2s](integration-snowflake-previous#monitor-for-salt-bucket-rotation-and-regenerate-raw-uid2s).
195
195
196
196
- 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).
197
197
198
+
<!-- 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 -->
199
+
198
200
:::note
199
201
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.
Copy file name to clipboardExpand all lines: docs/guides/integration-snowflake-before-february-2025.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ import Link from '@docusaurus/Link';
15
15
[Snowflake](https://www.snowflake.com/) is a cloud data warehousing solution, where you as a partner can store your data and integrate with the UID2 framework. Using Snowflake, UID2 enables you to securely share consumer identifier data without exposing sensitive <Linkhref="../ref-info/glossary-uid#gl-dii">directly identifying information (DII)</Link>. Even though you have the option to query the Operator Web Services directly for the consumer identifier data, the Snowflake UID2 integration offers a more seamless experience.
16
16
17
17
:::important
18
-
This document is for anyone using the separate advertiser and data provider Snowflake marketplace listings published prior to February 2025. For documentation on the latest version, see [Snowflake Integration Guide](integration-snowflake.md). If you're using any earlier implementation, we recommend that you migrate to the latest version to take advantage of the updates and enhancements. For migration information, see [Migration Guide](integration-snowflake-before-july-2025.md#migration-guide).
18
+
This document is for anyone using the separate advertiser and data provider Snowflake marketplace listings published prior to February 2025. For documentation on the latest version, see [Snowflake Integration Guide](integration-snowflake.md). If you're using any earlier implementation, we recommend that you migrate to the latest version to take advantage of the updates and enhancements. For migration information, see [Migration Guide](integration-snowflake.md#migration-guide).
19
19
:::
20
20
21
21
The Snowflake marketplace listings for this implementation were separate for advertisers and for data providers. Those listings were removed following the publication of the updated version in February 2025.
Copy file name to clipboardExpand all lines: docs/guides/integration-snowflake.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ import Link from '@docusaurus/Link';
15
15
[Snowflake](https://www.snowflake.com/) is a cloud data warehousing solution, where you as a partner can store your data and integrate with the UID2 framework. Using Snowflake, UID2 enables you to securely share consumer identifier data without exposing sensitive <Linkhref="../ref-info/glossary-uid#gl-dii">directly identifying information (DII)</Link>. Even though you have the option to query the Operator Web Services directly for the consumer identifier data, the Snowflake UID2 integration offers a more seamless experience.
16
16
17
17
:::important
18
-
This document is for those using the combined advertiser and data provider Snowflake marketplace listing published in February 2025. If you're using one of the earlier listings, which were separate for advertiser and data provider (that is, you subscribed prior to February 2025), see [Snowflake Integration (Pre-Feb 2025)](integration-snowflake-before-february-2025.md). If you're using the earlier implementation, we recommend that you migrate to the newer version to take advantage of the updates and enhancements: for details, see [Changes from Previous Version](#changes-from-previous-version). For migration information, see [Migration Guide](#migration-guide).
18
+
This document is for those using the latest [Snowflake marketplace listing](#snowflake-marketplace-listing). If you're using an earlier version, see [Snowflake Integration Guide (Pre-July 2025)](integration-snowflake-previous.md). If you're using the earlier implementation, we recommend that you migrate to the newer version to take advantage of the updates and enhancements: for details, see [Changes from Previous Version](#changes-from-previous-version). For migration information, see [Migration Guide](#migration-guide).
19
19
:::
20
20
21
21
## Snowflake Marketplace Listing
@@ -46,14 +46,14 @@ If you're a publisher who is sharing UID2 tokens in the <Link href="../ref-info/
46
46
The July 2025 update to the UID2 Snowflake Marketplace integration introduces a new identity mapping function that simplifies UID2 refresh management and allows accessing previous raw UID2s for 90 days after rotation.
47
47
48
48
:::note
49
-
These changes assume that your code integration uses the version of Snowflake functions published before July 2025: see [Snowflake Integration Guide (Pre-July 2025)](integration-snowflake-before-july-2025.md). For details on migrating to this version, see [Migration Guide](#migration-guide).
49
+
These changes assume that your code integration uses the version of Snowflake functions published before July 2025: see [Snowflake Integration Guide (Pre-July 2025)](integration-snowflake-previous.md). For details on migrating to this version, see [Migration Guide](#migration-guide).
50
50
:::
51
51
52
52
The following table shows the differences between the old and new identity mapping functions.
53
53
54
54
| Function | Version | Return Fields | Key Differences | Comments |
55
55
| :-- | :-- | :-- | :-- | :-- |
56
-
|`FN_T_IDENTITY_MAP`| Previous |`UID`, `BUCKET_ID`, `UNMAPPED`| Basic identity mapping with salt bucket tracking | Legacy function using salt bucket monitoring for refresh management. For details, see [Snowflake Integration Guide (Pre-July 2025)](integration-snowflake-before-july-2025.md).|
56
+
|`FN_T_IDENTITY_MAP`| Previous |`UID`, `BUCKET_ID`, `UNMAPPED`| Basic identity mapping with salt bucket tracking | Legacy function using salt bucket monitoring for refresh management. For details, see [Snowflake Integration Guide (Pre-July 2025)](integration-snowflake-previous.md).|
57
57
|`FN_T_IDENTITY_MAP_V3`| Current |`UID`, `PREV_UID`, `REFRESH_FROM`, `UNMAPPED`| Enhanced with previous UID2 access and refresh timestamps | Returns previous UID2 for 90 days after rotation and uses refresh timestamps instead of salt bucket monitoring. For details, see [Map DII](#map-dii).|
58
58
59
59
### Key Benefits
@@ -102,7 +102,7 @@ You can map DII to UID2s by using the following function:
102
102
103
103
-`FN_T_IDENTITY_MAP_V3` (for details, see [Map DII](#map-dii))
104
104
105
-
The following function is deprecated in favor of `FN_T_IDENTITY_MAP_V3`. You can still use it if you are on the previous Snowflake version (see [Snowflake Integration Guide (Pre-July 2025)](integration-snowflake-before-july-2025.md)), but we recommend upgrading as soon as possible:
105
+
The following function is deprecated in favor of `FN_T_IDENTITY_MAP_V3`. You can still use it if you are on the previous Snowflake version (see [Snowflake Integration Guide (Pre-July 2025)](integration-snowflake-previous.md)), but we recommend upgrading as soon as possible:
106
106
107
107
-`FN_T_IDENTITY_MAP` (deprecated)
108
108
@@ -617,7 +617,7 @@ To help prevent UID2 tokens from expiring, decrypt the UID2 tokens as soon as th
617
617
This section provides information to help you upgrade from the previous version to the new UID2 Snowflake functionality with v3 functions.
618
618
619
619
:::note
620
-
If you're upgrading from a version earlier than February 2025, see [Migration Guide](integration-snowflake-before-july-2025.md#migration-guide) in the documentation for the February 2025 update.
620
+
If you're upgrading from a version earlier than February 2025, see [Migration Guide](integration-snowflake-previous.md#migration-guide) in the documentation for the previous version.
Copy file name to clipboardExpand all lines: i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-advertiser-dataprovider-overview.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ import Link from '@docusaurus/Link';
53
53
|[2: Store Raw UID2s and Salt Bucket IDs](#2-store-raw-uid2s-and-salt-bucket-ids)| カスタム(適切な方法で)。 |
54
54
|[3: Manipulate or Combine Raw UID2s](#3-manipulate-or-combine-raw-uid2s)| カスタム(適切な方法で)。 |
55
55
|[4: Send Stored Raw UID2s to DSPs to Create Audiences or Conversions](#4-send-stored-raw-uid2s-to-dsps-to-create-audiences-or-conversions)| カスタム(適切な方法で)。 |
56
-
|[5: Monitor for Salt Bucket Rotations for Your Stored Raw UID2s](#5-monitor-for-salt-bucket-rotations-for-your-stored-raw-uid2s)| 以下のいずれかのオプションを使用してください:<ul><li><strong>Python SDK</strong>: Python Reference Guide を参照してください</li><li><strong>Snowflake</strong>: [Snowflake Integration Guide](integration-snowflake.md) の [Monitor for Salt Bucket Rotation and Regenerate Raw UID2s](integration-snowflake-before-february-2025.md#monitor-for-salt-bucket-rotation-and-regenerate-raw-uid2s) を参照してください</li><li><strong>Raw HTTP endpoint</strong>: [POST /identity/buckets](../endpoints/post-identity-buckets.md)</li></ul> |
56
+
|[5: Monitor for Salt Bucket Rotations for Your Stored Raw UID2s](#5-monitor-for-salt-bucket-rotations-for-your-stored-raw-uid2s)| 以下のいずれかのオプションを使用してください:<ul><li><strong>Python SDK</strong>: Python Reference Guide を参照してください</li><li><strong>Snowflake</strong>: [Snowflake Integration Guide](integration-snowflake.md) の [Monitor for Salt Bucket Rotation and Regenerate Raw UID2s](integration-snowflake-previous.md#monitor-for-salt-bucket-rotation-and-regenerate-raw-uid2s) を参照してください</li><li><strong>Raw HTTP endpoint</strong>: [POST /identity/buckets](../endpoints/post-identity-buckets.md)</li></ul> |
57
57
|[6: Monitor for Opt-Out Status](#6-monitor-for-opt-out-status)| API コールを使用して、[POST /optout/status](../endpoints/post-optout-status.md) エンドポイントにアクセスします。 |
58
58
59
59
## Integration Diagram
@@ -124,7 +124,7 @@ raw UID2 は、特定の時点におけるユーザーの識別子です。raw U
124
124
125
125
- Python SDK: [Monitor Rotated Salt Buckets](../sdks/sdk-ref-python.md#monitor-rotated-salt-buckets).
126
126
127
-
- Snowflake: [Monitor for Salt Bucket Rotation and Regenerate Raw UID2s](integration-snowflake-before-july-2025.md#monitor-for-salt-bucket-rotation-and-regenerate-raw-uid2s).
127
+
- Snowflake: [Monitor for Salt Bucket Rotation and Regenerate Raw UID2s](integration-snowflake-previous.md#monitor-for-salt-bucket-rotation-and-regenerate-raw-uid2s).
128
128
129
129
- HTTP endpoints: [Monitor for Salt Bucket Rotations for Your Stored Raw UID2s](integration-advertiser-dataprovider-endpoints.md#5-monitor-for-salt-bucket-rotations-for-your-stored-raw-uid2s).
<!-- GWH_Note 8/4/25 I took the .md out of the Snowflake link line 18 because Docu would not build it correctly... broken link in output. Do not know why, though. Same note on 2 links -->
Copy file name to clipboardExpand all lines: i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-snowflake.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ import Link from '@docusaurus/Link';
19
19
[Snowflake](https://www.snowflake.com/) is a cloud data warehousing solution, where you as a partner can store your data and integrate with the UID2 framework. Using Snowflake, UID2 enables you to securely share consumer identifier data without exposing sensitive <Linkhref="../ref-info/glossary-uid#gl-dii">directly identifying information (DII)</Link>. Even though you have the option to query the Operator Web Services directly for the consumer identifier data, the Snowflake UID2 integration offers a more seamless experience.
20
20
21
21
:::important
22
-
This document is for those using the combined advertiser and data provider Snowflake marketplace listing published in February 2025. If you're using one of the earlier listings, which were separate for advertiser and data provider (that is, you subscribed prior to February 2025), see [Snowflake Integration (Pre-Feb 2025)](integration-snowflake-before-february-2025.md). If you're using the earlier implementation, we recommend that you migrate to the newer version to take advantage of the updates and enhancements: for details, see [Changes from Previous Version](#changes-from-previous-version). For migration information, see [Migration Guide](#migration-guide).
22
+
This document is for those using the latest [Snowflake marketplace listing](#snowflake-marketplace-listing). If you're using an earlier version, see [Snowflake Integration Guide (Pre-July 2025)](integration-snowflake-previous.md). If you're using the earlier implementation, we recommend that you migrate to the newer version to take advantage of the updates and enhancements: for details, see [Changes from Previous Version](#changes-from-previous-version). For migration information, see [Migration Guide](#migration-guide).
23
23
:::
24
24
25
25
## Snowflake Marketplace Listing
@@ -50,14 +50,14 @@ If you're a publisher who is sharing UID2 tokens in the <Link href="../ref-info/
50
50
The July 2025 update to the UID2 Snowflake Marketplace integration introduces a new identity mapping function that simplifies UID2 refresh management and allows accessing previous raw UID2s for 90 days after rotation.
51
51
52
52
:::note
53
-
These changes assume that your code integration uses the version of Snowflake functions published before July 2025: see [Snowflake Integration Guide (Pre-July 2025)](integration-snowflake-before-july-2025.md). For details on migrating to this version, see [Migration Guide](#migration-guide).
53
+
These changes assume that your code integration uses the version of Snowflake functions published before July 2025: see [Snowflake Integration Guide (Pre-July 2025)](integration-snowflake-previous.md). For details on migrating to this version, see [Migration Guide](#migration-guide).
54
54
:::
55
55
56
56
The following table shows the differences between the old and new identity mapping functions.
57
57
58
58
| Function | Version | Return Fields | Key Differences | Comments |
59
59
| :-- | :-- | :-- | :-- | :-- |
60
-
|`FN_T_IDENTITY_MAP`| Previous |`UID`, `BUCKET_ID`, `UNMAPPED`| Basic identity mapping with salt bucket tracking | Legacy function using salt bucket monitoring for refresh management. For details, see [Snowflake Integration Guide (Pre-July 2025)](integration-snowflake-before-july-2025.md).|
60
+
|`FN_T_IDENTITY_MAP`| Previous |`UID`, `BUCKET_ID`, `UNMAPPED`| Basic identity mapping with salt bucket tracking | Legacy function using salt bucket monitoring for refresh management. For details, see [Snowflake Integration Guide (Pre-July 2025)](integration-snowflake-previous.md).|
61
61
|`FN_T_IDENTITY_MAP_V3`| Current |`UID`, `PREV_UID`, `REFRESH_FROM`, `UNMAPPED`| Enhanced with previous UID2 access and refresh timestamps | Returns previous UID2 for 90 days after rotation and uses refresh timestamps instead of salt bucket monitoring. For details, see [Map DII](#map-dii).|
62
62
63
63
### Key Benefits
@@ -106,7 +106,7 @@ You can map DII to UID2s by using the following function:
106
106
107
107
-`FN_T_IDENTITY_MAP_V3` (for details, see [Map DII](#map-dii))
108
108
109
-
The following function is deprecated in favor of `FN_T_IDENTITY_MAP_V3`. You can still use it if you are on the previous Snowflake version (see [Snowflake Integration Guide (Pre-July 2025)](integration-snowflake-before-july-2025.md)), but we recommend upgrading as soon as possible:
109
+
The following function is deprecated in favor of `FN_T_IDENTITY_MAP_V3`. You can still use it if you are on the previous Snowflake version (see [Snowflake Integration Guide (Pre-July 2025)](integration-snowflake-previous.md)), but we recommend upgrading as soon as possible:
110
110
111
111
-`FN_T_IDENTITY_MAP` (deprecated)
112
112
@@ -620,6 +620,10 @@ To help prevent UID2 tokens from expiring, decrypt the UID2 tokens as soon as th
620
620
621
621
This section provides information to help you upgrade from the previous version to the new UID2 Snowflake functionality with v3 functions.
622
622
623
+
:::note
624
+
If you're upgrading from a version earlier than February 2025, see [Migration Guide](integration-snowflake-previous.md#migration-guide) in the documentation for the previous version.
625
+
:::
626
+
623
627
### Changing Existing Code
624
628
625
629
For a summary of changes, see [Changes from Previous Version](#changes-from-previous-version). The code snippets in this section are before/after examples of how the earlier functions might be implemented, and how you could update to use the new function. The key change is migrating from `FN_T_IDENTITY_MAP` to `FN_T_IDENTITY_MAP_V3`, which provides refresh timestamps instead of salt bucket IDs and includes previous UID2 access.
0 commit comments