Add Engage -> Snowflake Public beta updates [DOCS-275]

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

@@ -243,6 +243,26 @@ To connect Snowflake to Segment:
   > info "Segment supports uploading one key at a time"
   > 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.  
 
+## Use with Engage 
+
+After you connect Snowflake, you can add a Snowflake Activation from Engage. [Linked Audiences](/docs/engage/audiences/linked-audiences/) writes audience enter/exit events to your warehouse, and [Event-Triggered Journeys](/docs/engage/journeys/v2/) writes journey step events. 
+
+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).
+
+### Schema and table selection (beta)
+
+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.
+
+### Sync behavior for Engage (beta)
+
+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.
+
+> warning ""
+> Changing the Snowflake destination’s general sync schedule does **not** affect Engage writebacks. Engage controls when these writes occur.
+
+### Data format and limits
+
+Engage writebacks use Track events. The full event payload is stored in a single stringified JSON column in the target table. 
 
 ## Security
 
@@ -324,6 +344,9 @@ Queuing - you can use a different Warehouse for Segment, or use the recommendati
 
 {% include content/warehouse-sync-sched.md %}
 
+> info ""
+> Engage writebacks (Journeys and Linked Audiences) start a sync **when an Engage run completes**. The schedule controls below apply to Connections, Profiles Sync and other warehouse deliveries, not to Engage-triggered writebacks.
+
 ![sync schedule image](/docs/connections/destinations/catalog/images/syncsched.png)
 
 ### I'm encountering a "JWT token is invalid" error. What do I do?

src/engage/audiences/linked-audiences.md

@@ -17,7 +17,6 @@ With Linked Audiences, you can:
 
 To learn more about specific use cases you can set up with Linked Audiences, see [Linked Audiences Use Cases](/docs/engage/audiences/linked-audiences-use-cases/).
 
-
 See how you can [use Linked Audiences with Braze](/docs/engage/audiences/linked-audiences-braze/) and [Iterable](/docs/engage/audiences/linked-audiences-iterable/) to better understand how you can utilize Linked Audiences for your destinations.  
 
 ## Prerequisites
@@ -153,6 +152,9 @@ See the step-by-step video on activating Linked Audiences:
 
 [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.
 
+> info "Write to Snowflake"
+> 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.
+
 **Note:** Ensure you've [enabled your destination](/connections/destinations/catalog/) in Segment before you begin the steps below. 
 
 1. Navigate to **Engage > Audiences**.
@@ -203,7 +205,6 @@ Click **Copy to use in Braze Cloud Mode (Actions)** to copy the personalization
 > info ""
 > This feature is in beta for customers using Braze. Some functionality may change before it becomes generally available. This feature is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}.
 
-
 #### Show/hide preview 
 
 As you're enriching your events in Linked Audiences, you should view a preview of the event payload schema based on the properties you select. It might look like the following:
@@ -214,6 +215,8 @@ As you're enriching your events in Linked Audiences, you should view a preview o
 
 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. 
 
+For Snowflake writebacks, Linked Audiences sends Track events and stores the full event payload in a single stringified JSON column in the target table.
+
 ## Step 3: Send a test event to your destination
 
 Send a test event to ensure that everything is connected properly and your destination receives the event. 

src/engage/journeys/v2/event-triggered-journeys-steps.md

@@ -241,6 +241,9 @@ The **Send to Destination** step lets you send journey data to one of your [conf
 
 This step supports Actions Destinations (excluding list destinations) and destination functions. It doesn't support storage destinations or classic (non-Actions) destinations.
 
+> info "Send journey step events to Snowflake"
+> If your team analyzes journey performance in the warehouse, you can write step events from a journey to Snowflake. Connect Snowflake to your Engage space, then add a Snowflake Activation for the journey and choose the schema/table you want to write to. See the [Snowflake destination documentation](/docs/connections/storage/catalog/snowflake/) for connection steps and key-pair setup.
+
 ### How Send to Destination works
 
 When a journey reaches the Send to Destination step, the journey packages the relevant data and sends it to your chosen destination. This could be a third-party platform, like a marketing tool, or a custom destination built using [Destination Functions](/docs/connections/functions/destination-functions/). The data that Segment sends includes key attributes from the journey context, profile traits, and any mapped fields you’ve configured.
@@ -266,6 +269,8 @@ Here’s how to configure this step within a journey:
 
 Before activating the journey, **send a test event to verify that the payload matches your expectations** and that it reaches the destination successfully.
 
+For Snowflake writebacks (beta), Journeys sends Track events and stores the full event payload in a single stringified JSON column in the target table.
+
 ### Destination event payload schema
 
 The events that Segment sends to destinations from Event-Triggered Journeys include an object called `journey_context` within the event’s properties. The `journey_context` object contains: