Skip to content

Commit d747941

Browse files
committed
add Snowflake callout to Linked Audiences page
1 parent bccdd4e commit d747941

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

src/engage/audiences/linked-audiences.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -153,6 +153,9 @@ See the step-by-step video on activating Linked Audiences:
153153

154154
[Destinations](/docs/connections/destinations/) are the business tools or apps that Segment forwards your data to. Adding an activation to your Linked Audience allows you to act on your data and learn more about your customers in real time. To fully take advantage of Linked Audiences, you must connect and configure at least one destination by creating an activation.
155155

156+
> info "Write to Snowflake"
157+
> To write to Snowflake, connect Snowflake to your Engage space, then add a Snowflake Activation from your audience to write enter/exit events to a schema and table you select. See the [Snowflake destination documentation](/docs/connections/storage/catalog/snowflake/) for connection steps and key-pair setup.
158+
156159
**Note:** Ensure you've [enabled your destination](/connections/destinations/catalog/) in Segment before you begin the steps below.
157160

158161
1. Navigate to **Engage > Audiences**.
@@ -214,6 +217,8 @@ As you're enriching your events in Linked Audiences, you should view a preview o
214217

215218
Segment attempts to automatically configure the data fields that will be sent to the destination. These fields are pre-filled with properties configured by default. Only required fields are displayed. All optional & pre-filled fields are hidden, though you can view hidden fields by clicking **Show hidden fields**. You can review and adjust these settings before enabling this event.
216219

220+
For Snowflake writebacks, Linked Audiences sends Track events and stores the full event payload in a single stringified JSON column in the target table.
221+
217222
## Step 3: Send a test event to your destination
218223

219224
Send a test event to ensure that everything is connected properly and your destination receives the event.

0 commit comments

Comments
 (0)