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-snowflake.md
+21-38Lines changed: 21 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,31 +63,46 @@ This update provides two major benefits:
63
63
-**Simplified Refresh Management**: You can monitor for UID2s reaching `REFRESH_FROM` timestamps instead of polling <Linkhref="../ref-info/glossary-uid#gl-salt-bucket-id">salt buckets</Link> for rotation.
64
64
-**Previous UID2 Access**: You have access to previous raw UID2s for 90 days after rotation for campaign measurement.
65
65
66
+
## Workflow Diagram
67
+
68
+
The following diagram and table illustrate the different parts of the UID2 integration process in Snowflake, and the workflow.
|As a partner, you set up a Snowflake account to host your data and engage in UID2 integration by consuming functions and views through the UID2 Share. | UID2 integration, hosted in a Snowflake account, grants you access to authorized functions and views that draw data from private tables. You can't access the private tables. The UID2 Share reveals only essential data needed for you to perform UID2-related tasks.<br/>**NOTE**: We store <Linkhref="../ref-info/glossary-uid#gl-salt">salts</Link> and encryption keys in the private tables. No <Linkhref="../ref-info/glossary-uid#gl-dii">DII</Link> is stored at any point. |ETL (Extract Transform Load) jobs constantly update the UID2 Core/Optout Snowflake storage with internal data that powers the UID2 Operator Web Services. The data used by the Operator Web Services is also available through the UID2 Share. |
75
+
|When you use shared functions and views, you pay Snowflake for transactional computation costs. |These private tables, secured in the UID2 Snowflake account, automatically synchronize with the UID2 Core/Optout Snowflake storage that holds internal data used to complete UID2-related tasks. ||
76
+
66
77
## Summary of Integration Steps
67
78
79
+
:::important
80
+
To be able to request data, you must use the `ACCOUNTADMIN` role or another role with the `CREATE DATABASE` and `IMPORT SHARE` privileges in your Snowflake account.
81
+
:::
82
+
68
83
The following list summarizes the integration steps for UID2 mapping in Snowflake in the production environment:
69
84
70
85
:::note
71
-
If you want to try out an integration before using the production environment, see [Testing in the Integration Environment](#testing-in-the-integration-environment).
86
+
If you want to try out an integration before using the production environment, see [Testing in the Integ Environment](#testing-in-the-integ-environment).
72
87
:::
73
88
74
89
1. Make sure that the UID2 POC paperwork is signed with your UID2 contact.
75
90
76
91
1. Request access to the UID2 share:
77
92
78
-
- Request access through the [Snowflake Marketplace Listing](#snowflake-marketplace-listing). In your request, include your Snowflake account number and the region
93
+
- Request access through the [Snowflake Marketplace Listing](#snowflake-marketplace-listing). In your request, include your Snowflake account number and the region.
79
94
80
-
-In addition, let your UID2 contact know that you've requested access.
95
+
-Let your UID2 contact know that you've requested access.
81
96
82
97
1. Your UID2 contact arranges for your Snowflake account to be provisioned with access to the UID2 mapping share.
83
98
84
99
:::note
85
-
If you did any initial testing (see [Testing in the Integration Environment](#testing-in-the-integration-environment)), be sure to update the functions to reflect the production UID2 share, along with your own relevant table names.
100
+
If you did any initial testing (see [Testing in the Integ Environment](#testing-in-the-integ-environment)), be sure to update the functions to reflect the production UID2 share, along with your own relevant table names.
86
101
:::
87
102
88
-
## Testing in the Integration Environment
103
+
## Testing in the Integ Environment
89
104
90
-
If you'd like to test the mapping share before signing a UID2 POC, you can ask your UID2 contact for access to the Snowflake share in the integ (integration) environment. This environment is for testing only, and has no production data. In the request, be sure to include your account number and region (see [Summary of Integration Steps](#summary-of-integration-steps) Step 2).
105
+
If you'd like to test the mapping share before signing a UID2 POC, you can ask your UID2 contact for access to the Snowflake share in the integ (integration) environment. This environment is for testing only, and has no production data. In the request, be sure to include your account number and region.
91
106
92
107
In this scenario, the following steps occur:
93
108
@@ -97,38 +112,6 @@ In this scenario, the following steps occur:
97
112
98
113
3. When you've requested access, your UID2 contact provisions the integ share to your account.
99
114
100
-
## Workflow Diagram
101
-
102
-
The following diagram and table illustrate the different parts of the UID2 integration process in Snowflake, and the workflow.
|As a partner, you set up a Snowflake account to host your data and engage in UID2 integration by consuming functions and views through the UID2 Share. | UID2 integration, hosted in a Snowflake account, grants you access to authorized functions and views that draw data from private tables. You can't access the private tables. The UID2 Share reveals only essential data needed for you to perform UID2-related tasks.<br/>**NOTE**: We store <Linkhref="../ref-info/glossary-uid#gl-salt">salts</Link> and encryption keys in the private tables. No <Linkhref="../ref-info/glossary-uid#gl-dii">DII</Link> is stored at any point. |ETL (Extract Transform Load) jobs constantly update the UID2 Core/Optout Snowflake storage with internal data that powers the UID2 Operator Web Services. The data used by the Operator Web Services is also available through the UID2 Share. |
109
-
|When you use shared functions and views, you pay Snowflake for transactional computation costs. |These private tables, secured in the UID2 Snowflake account, automatically synchronize with the UID2 Core/Optout Snowflake storage that holds internal data used to complete UID2-related tasks. ||
110
-
111
-
## Access the UID2 Share
112
-
113
-
Access to the UID2 Share is available through the following listing on the [Snowflake Data Marketplace](https://www.snowflake.com/data-marketplace/):
114
-
115
-
-[Unified ID 2.0: Advertiser and Data Provider Identity Solution](https://app.snowflake.com/marketplace/listing/GZT0ZRYXTN8/unified-id-2-0-unified-id-2-0-advertiser-and-data-provider-identity-solution)
116
-
117
-
:::important
118
-
To be able to request data, you must use the `ACCOUNTADMIN` role or another role with the `CREATE DATABASE` and `IMPORT SHARE` privileges in your Snowflake account.
119
-
:::
120
-
121
-
To request access to the UID2 Share, complete the following steps:
122
-
123
-
1. Log in to the Snowflake Data Marketplace and select the UID2 listing:
124
-
- [Unified ID 2.0: Advertiser and Data Provider Identity Solution](https://app.snowflake.com/marketplace/listing/GZT0ZRYXTN8/unified-id-2-0-unified-id-2-0-advertiser-and-data-provider-identity-solution)
125
-
2. In the **Personalized Data** section, click **Request Data**.
126
-
3. Follow the onscreen instructions to verify and provide your contact details and other required information.
127
-
4. If you are an existing client of The Trade Desk, include your partner and advertiser IDs issued by The Trade Desk in the **Message** field of the data request form.
128
-
5. Submit the form.
129
-
130
-
After your request is received, a UID2 administrator will contact you with the appropriate access instructions. For details about managing data requests in Snowflake, see the [Snowflake documentation](https://docs.snowflake.com/en/user-guide/data-marketplace-consumer.html).
131
-
132
115
## Shared Objects
133
116
134
117
You can map DII to UID2s by using the following function:
0 commit comments