| View + | +Description + | +
|---|---|
+ contacts
+ |
+ Data specific to each contact such as name, address, etc. You can store string type (i.e. first name), number type (i.e. age), geo type (i.e. addresses), and array type (i.e. favorite colors). You can add as many attributes as needed to describe your contacts. Cart items are also stored with each contact and can contain information about a product such as SKU, description image, and much more. + | +
+ contactactivity (events)
+ |
+ Data related to a contact's activity or behavior. This can be message activity as well as website activity (browsed a page, added to cart), or external (IoT) activity. + | +
+ messagesends
+ |
+ Data specific to message sends, such as the channel used to send the message, whether the message is promotional or transactional, information about how and when the message was created, and more. + | +
+orders
+ |
+ + Data about a contact's order history. + | +
CONTACTS**
+
+Here's an example query that uses CONTACTS to find **(1)** the grand total dollar amount of all cart items across all carts, **(2)** the average dollar amount of all cart items per cart, **(3)** the average number of items per cart, and finally **(4)** the total number of carts.
+
+```sql
+SELECT
+ SUM(TRY_TO_NUMBER(cart:"totalAmount"::varchar)) as "grand_total_amount",
+ AVG(TRY_TO_NUMBER(cart:"totalAmount"::varchar)) as "average_total_amount",
+ AVG(ARRAY_SIZE(cart:"cartitems")) as "average_num_cart_items",
+ count(*) as "total_carts"
+FROM
+ contacts
+WHERE
+ cart IS NOT NULL
+;
+```
+
+grand_total_amount
+ |
+
+ average_total_amount
+ |
+
+ average_num_cart_items
+ |
+
+ total_carts
+ |
+
|---|---|---|---|
| + 41479622 + | ++ 1595370.077 + | ++ 13.961538 + | ++ 26 + | +
CONTACTACTIVITY**
+
+Here's an example query that demonstrates selecting data from CONTACTACTIVITY. The query returns total daily counts for several events (aka actions) related to sending messages for a specified date range (message sends, opens, clicks, and bounces). This query makes use of some advanced SQL features such as Common Table Expressions and the PIVOT function, demonstrating Snowflake’s rich SQL support.
+
+```sql
+WITH action_totals AS (
+ SELECT
+ to_date(action_date) as action_date,
+ action,
+ count(*) as total
+ FROM
+ contactactivity
+ WHERE
+ action_date BETWEEN '2022-09-19' AND '2022-09-25'
+ AND action IN ('message-sent', 'open', 'click', 'bounce')
+GROUP BY
+ action_date,
+ action
+)
+SELECT
+ *
+FROM
+ action_totals
+PIVOT (
+ SUM(total) FOR action IN ('message-sent', 'open', 'click', 'bounce')
+) as p
+ORDER BY
+ action_date
+```
+
+
+ action_date
+ |
+
+ message-sent
+ |
+
+ open
+ |
+
+ click
+ |
+
+ bounce
+ |
+
|---|---|---|---|---|
| + 2022-09-19 + | ++ 2749273 + | ++ 1080279 + | ++ 3015 + | ++ 2829 + | +
| + 2022-09-20 + | ++ 2605236 + | ++ 1796475 + | ++ 7139 + | ++ 6229 + | +
| + 2022-09-21 + | ++ 2738569 + | ++ 1884556 + | ++ 4742 + | ++ 2145 + | +
| + 2022-09-22 + | ++ 3073 + | ++ 929171 + | ++ 1485 + | ++ 6047 + | +
| + 2022-09-23 + | ++ 2810032 + | ++ 812085 + | ++ 2628 + | ++ 466 + | +
| + 2022-09-24 + | ++ 2041732 + | ++ 1600629 + | ++ 4839 + | ++ 2258 + | +
| + 2022-09-25 + | ++ 928 + | ++ 87 + | ++ 1 + | ++ 1 + | +
VARCHAR columns. Column size limit is 8kb or VARCHAR(8192).
+- Your Table/View must be set to convert nanoseconds (default in Snowflake) into microseconds (default in Cordial) in order to successfully transfer date attributes.
+
+#### Geo attributes
+
+Geo attributes should be represented as separate columns. For example, the geo attribute homeaddress would be broken up into columns such as:
+
+- homeaddress.street_address
+- homeaddress.city
+- homeaddress.state
+- homeaddress.postal_code
+
+#### Array attributes
+
+Array attributes will be updated as a whole unless additional syntax is included to add or remove an item from an array, as follows:
+
+- Remove from array: { "remove": \["apple"\] }
+- Add to array: { "add": \["apple"\] }
+
+**Note:** Your Table/View must be set to convert nanoseconds (default in Snowflake) into microseconds (default in Cordial) in order to successfully transfer date attributes.
+
+
+## Enable Snowflake as a Data Source in Cordial
+Duration: 10
+
+You can enable Snowflake as a data source in Cordial’s UI.
+
+1. Log in to Cordial, navigate to **Integrations > Partners**, and select **Enable** on the Snowflake card.
+
+2. Fill in the required information:
+
+- Snowflake account identifier (format should be \[organization\]-\[identifier\])
+- Warehouse name
+- Username
+- Authentication method: Password or Saved key
+- Role name
+- Database name
+- Schema name
+- Table or View name
+
+**Note:** Connection parameters are case-sensitive and should match the exact case of the named objects—warehouse, user, role, database, Table/View, or schema—in Snowflake.
+
+
+
+3. To add a Table/View, click **Add Table/View**.
+
+4. Click **Test Connection**.
+
+5. If it's successful, select **Continue**.
+
+### Saved key authentication
+
+Select this method if you want to use [key-pair authentication in Snowflake](https://docs.snowflake.com/en/user-guide/key-pair-auth).
+
+1. You first need to create a secret (aka saved key) in Cordial by navigating to **Settings > Account Settings > Secrets Vault > New**.
+
+2. Your new secret will include a **Public key (PEM format)**.\
+
+
+3. Update the user in Snowflake by pasting in the Public key (PEM format) of your created secret.
+
+**Note:** Don't include the -----BEGIN PUBLIC KEY----- and -----END PUBLIC KEY----- that appear with your PEM key. Snowflake requires these markers to be removed in their environment.
+
+4. In the export job from Cordial, select **Saved Key** as the authentication method and choose your Cordial secret under **Saved key**.
+
+
+
+## Create Data Jobs in Cordial with Snowflake as a Data Source
+Duration: 10
+
+In Cordial, you can use Data Jobs to:
+
+- Import contacts or supplements.
+- Export contacts, events, orders, or supplements.
+- Sync your contacts with Facebook and Google Ads.
+- Create a Transformation: custom, scripted export, or scripted import.
+
+These steps unlock Cordial’s powerful automated messaging capabilities.
+
+### Create new Data Job in Cordial
+
+1. Once you've successfully enabled Snowflake to send data to Cordial, navigate to **Data Jobs > Create New Data Job**, select the appropriate Data Job, and fill in the required fields.
+
+
+
+2. In your Data Job, select **Edit** in the **Data Source** pane.
+
+3. Choose **External** under **Data Source**.
+
+4. Choose **Snowflake** under **Data location**.
+
+5. Choose the appropriate **Snowflake connection** and **Snowflake Table/Views**.
+
+**Note:** Cordial will automatically query Snowflake at a specified interval, updating modified records and inserting any new records since the last sync. You can configure your data refresh interval to occur every 15 minutes, every 30 minutes, every hour, every week, or every month to optimize access to real-time data.
+
+6. Choose the sync type: **Full refresh** or **Incremental**.
+
+### Sync types
+
+One-time Data Jobs only support full refresh syncs. Recurring Data Job Automations support both full refresh and incremental syncs.
+
+#### Full refresh
+
+- Used in one-time Data Jobs and recurring Data Job automations.
+- Selects all records from the Snowflake Table.
+- Query doesn't have WHERE and ORDER elements.
+
+
+
+#### Incremental
+
+- Used in recurring Data Job automations.
+- Cordial stores sequence (last updated date from last imported row) as {prevValue}
+- Select the desired **Cursor field** from the dropdown.
+- **The cursor value is not repeated between syncs** option controls how Cordial selects records for the incremental sync.
+
+\
+**Note:** If the cursor field has unique values, such as unique IDs, Cordial can simplify the process and select all the new records. But if the cursor field is not unique, such as a timestamp or date, Cordial skips one or more records with the maximum value.
+
+In the examples below, UPDATED_AT and ORDER_ID are cursor fields:
+
+- If you select **The cursor value is not repeated** checkbox, Cordial creates a query like this:
+
+```sql
+SELECT ... WHERE ORDER_ID {prevValue}
+```
+
+- If the checkbox is not selected, Cordial runs a query like this:
+
+```sql
+SELECT ... WHERE UPDATED_AT {prevValue} AND UPDATED_AT <(select
+max(updated_at)="max(UPDATED_AT)" from="FROM" {table})="{table})">
+```
+
+**Note:** The second example means Cordial doesn't import at least one row with max(UPDATED_AT)
+
+### API support
+
+The following Cordial endpoints support Snowflake as a data source:
+
+- [POST/v2/contactimports](https://support.cordial.com/hc/en-us/articles/203886058-Contact-imports-API#postContactImports)
+- [POST/v2/supplements/{supplement}/imports](https://support.cordial.com/hc/en-us/articles/204570687-Supplements-API#postSuppImports)
+
+Example JSON request:
+
+```json
+{
+ "source":{
+ "transport":"snowflake",
+ "connection":"same_name_used_in_marketplace_setup",
+ "tableview":"same_table_view_name_used_in_marketplace_setup"
+ },
+ "hasHeader":true,
+ "confirmEmail":"msmith@example.com"
+}
+```
+### Disable connection
+
+If you need to stop the sync, you can disable the connection by clicking **Configure** on the Snowflake card in Cordial (**Integrations > Partners**) and selecting the **Disable** button. When the connection is re-enabled, the job will continue looking for all records that were inserted or updated since the last sync.
+
+## Conclusion and Resources
+
+Congratulations! You have successfully learned how to create a two-way data share between Cordial and Snowflake, unlocking new opportunities for your team.
+
+### What you learned
+
+- How to set up a Secure Data Share between Cordial and Snowflake
+- The data that gets unlocked by integrating Cordial and Snowflake
+- How to send queries from Cordial to Snowflake
+- How to send data from Snowflake to Cordial for use in marketing campaigns
+
+### Related resources
+Want to learn more about Cordial and Snowflake? Check out the following resources:
+
+- [Cordial’s Snowflake Marketplace listing](https://app.snowflake.com/marketplace/listing/GZSTZ1D9SIF/cordial-messaging-data-personalized-user-profiles-events)
+- [Snowflake/Cordial partner page](https://cordial.com/partners/snowflake/)
+- [Why data sharing is important for real-time personalization blog](https://cordial.com/resources/why-data-sharing-is-important-for-real-time-personalization/)
+- [Cordial’s Snowflake Secure Data Sharing Knowledge Base article](https://support.cordial.com/hc/en-us/articles/9615168271629-Snowflake-Secure-Data-Sharing)