Destination Node

Destination nodes activate your marketing tools. In real-time journeys, destinations fall into three categories based on how they process.

---

Instant destinations

Composable destinations process in real time. When a user reaches the node, GrowthLoop triggers the selected campaign or template within seconds.

Instant sends require the campaign triggers feature to be enabled for your organization. In the destination node, choose an export action such as Send Email or Send Push instead of Add to List Only.

Field sources for instant sends

Map fields from:

• Real-time event payload — Values from the triggering message (order ID, product name, etc.)
• Synced warehouse fields — Profile attributes from your Personalization API sync (first name, last name, opt-in status, etc.)
• Warehouse-enriched fields — Primary dataset values that GrowthLoop fetches when the destination requires them.
• Flexible query values — Values resolved from configured warehouse queries.
• Custom attributes — Text and counter values set upstream in the journey, including from trigger response fields

For platform-specific template and recipient setup, see the Composable Campaigns guides for Braze, Iterable, OneSignal, Sailthru, SFMC, and SendGrid.

Choose a match-field source

The match-field picker identifies the source of each value. Depending on the destination, you can choose:

• Event — A field from the message that triggered the journey.
• Personalization — A field cached by a Personalization API Sync.
• Warehouse — A field fetched from the primary dataset through real-time enrichment.
• Custom attribute — An upstream text or counter custom attribute.

GrowthLoop keeps the selected source with the mapping so it can request the field from the correct system. For instant sends, if a field can be supplied by more than one runtime layer, GrowthLoop checks enriched values first, then the triggering event, and then journey custom attributes. Use a synced profile or warehouse field when the event does not contain the value required by the destination.

The match-field picker identifies cached Personalization profile fields separately from real-time event fields. Make sure the selected profile field has been populated by a successful Personalization API Sync before publishing the journey.

For a hybrid or batch destination, an event-sourced match field must also have an event-to-dataset field mapping so GrowthLoop can normalize it for the warehouse export. An unmapped event field cannot be used by that destination.

---

Personalization API destination

Route users to the Personalization API destination to write attributes to a user's profile in real time. Use this to update offers, flags, or variants during an active session.

See Same-session personalization for an end-to-end walkthrough.

---

Batch destinations

Destinations that export lists or use non-composable configurations run within minutes rather than instantly. This includes:

• Add to List Only exports
• Destinations without a configured email template and match fields
• Most standard warehouse-backed destination exports

When a user hits a batch destination, they are recorded in the journey state table and the export runs within minutes. All downstream nodes from a batch destination node, will be processed in batch as well.

CRM action nodes always run as batch destination nodes.

---

Related guides

• Syncing warehouse fields
• Real-time enrichment
• Custom attributes