Skip to content

Commit f69f680

Browse files
committed
Add new Engage use section to Snowflake destination
1 parent 038211c commit f69f680

File tree

1 file changed

+16
-0
lines changed
  • src/connections/storage/catalog/snowflake

1 file changed

+16
-0
lines changed

src/connections/storage/catalog/snowflake/index.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -243,6 +243,22 @@ To connect Snowflake to Segment:
243243
> info "Segment supports uploading one key at a time"
244244
> Although you can create up to two keys in Snowflake, Segment only supports authenticating with one key at a time. To change the key that is in Segment, return to your Snowflake destination's settings and upload a new key in the **Private Key** field.
245245
246+
## Use with Engage (Journeys & Linked Audiences)
247+
248+
After you connect Snowflake, you can add a Snowflake Activation from Engage. Linked Audiences writes audience enter/exit events to your warehouse, and Journeys writes journey step events.
249+
250+
Segment recommends key-pair authentication for the Snowflake user. For mor information, see [create a user that authenticates with a key pair](#create-a-user-that-authenticates-with-a-key-pair).
251+
252+
### Schema and table selection (beta)
253+
254+
When you create a Snowflake Activation from Engage, choose the schema and either select an existing table or enter a new table name. Engage writes to exactly what you specify.
255+
256+
### Sync behavior for Engage (beta)
257+
258+
For Engage writebacks, Segment starts a warehouse sync after each run completes (for example, when an audience run finishes). This replaces a fixed hourly cadence for these writebacks.
259+
260+
> warning ""
261+
> Changing the Snowflake destination’s general sync schedule does **not** affect Engage writebacks. Engage controls when these writes occur.
246262
247263
## Security
248264

0 commit comments

Comments
 (0)