Journey Decisioning lets AI decide which marketing program to serve to which customer, so that your target outcome is maximized. Instead of relying on intuition, correlational data, or the limited optimization capabilities of downstream platforms, you define the variations on your journey canvas, select a metric to maximize, and GrowthLoop's decisioning algorithm continuously learns which path drives the best results -- automatically shifting traffic toward winning variations over time.

Because decisioning runs entirely in your data cloud, it is fully composable: no data leaves your environment, models are always fresh (training and inference run concurrently, so each decision uses the most up-to-date data), and the only limiting factor is the flexibility of the journey canvas itself. Any metric from the Metrics Builder can be optimized over, and user context can draw from any combination of customer features in your warehouse.

This feature builds on two other GrowthLoop capabilities:

• Metrics Builder -- define the KPI you want the decisioning node to optimize for
• Journeys -- build the multi-step customer journeys that contain your decisioning node

How it works

A Decisioning node is a special node type on the journey canvas that contains multiple variation paths (arms). When customers reach the decisioning node, GrowthLoop assigns them to a variation and tracks the downstream outcome using the metric you selected. Over time, the algorithm learns which variation -- and which customer characteristics -- drive the best results, and it shifts traffic allocation toward the winning paths.

Under the hood, GrowthLoop uses a Bayesian multi-armed bandit with Thompson Sampling, executed entirely in SQL within your data cloud. For 1:1 Personalization, expected reward is modeled as a function of customer features, and the algorithm maintains a posterior distribution over each variation's performance that updates continuously as new data arrives. This means the system makes an outcome-optimizing decision for each customer based on the context features you define.

For Global decisioning, each variation maintains an independent belief about reward likelihood for its arm.

Key properties of this approach:

• Always fresh -- training and inference happen concurrently with every journey run. There is no separate training schedule and no model staleness.
• Composable -- all model state, learning, and decision logic live directly in your warehouse. No data is copied to external model services.
• Transparent -- every assignment decision and its inputs are written to tracking tables you can query directly.

Unlike a standard Experiment node, which uses a fixed percentage or count split, the Decisioning node uses dynamic allocation that adapts as data comes in. You get the benefits of experimentation with the efficiency of real-time optimization.

What you can optimize

Because decisioning is limited only by what you can build on the journey canvas, it supports a wide range of optimization use cases:

• Next Best channel -- email vs. push notification vs. SMS vs. direct mail

• Next Best content -- different creative variants, offers, or product recommendations

• Next Best timing -- different delay intervals before outreach

• Next best product -- which product or category to recommend

• Omni-channel orchestration -- complex multi-step sub-journeys per variation

You can place multiple Decisioning nodes in a single journey, each optimizing a different decision point. Each node acts independently, giving you a "journey within a journey" level of flexibility.

📘

Note

The decisioning algorithm optimizes traffic allocation across the variations you define. It does not automatically discover or generate new variations -- you design the candidate paths, and the AI learns which ones work best for which customers.

Prerequisites

Before adding a Decisioning node to your journey, you need:

1. At least one metric created via the Metrics Builder that tracks a numeric value (e.g., revenue, purchase count, engagement score).
2. A journey connected to the same Dataset Group as your metric, so GrowthLoop can evaluate outcomes across your customer base.
3. This feature is only available for repeat journeys, not for One Time journeys
4. If you plan to use 1:1 Personalization, make sure the customer features you want to use are available in your primary dataset and have labels.

📘

Note

Only metrics where the underlying field is a numeric type (numbers, integers, decimals) can be used with decisioning. Non-numeric fields like text or dates are not eligible.

Set up a decisioning node

1. Open your journey on the journey canvas.
2. Drag a Decisioning node from the node library onto the canvas.
3. Connect the decisioning node to the preceding node in your journey by dragging from the parent node's output to the decisioning node's input.

Select a metric

4. Click on the decisioning node to open its settings panel.
5. Under Metric, select the metric you want the algorithm to maximize. If you do not have a metric yet, click Create a metric to maximize to open the Metrics Builder.

📘

Note

A metric must be selected before you can publish the journey. The decisioning node will not function without a target metric.

Configure decisioning settings

6. Open Decisioning Settings by clicking the settings icon on the decisioning node.
7. Choose a Type:
   • 1:1 Personalization -- the algorithm learns which variation works best for each customer based on their individual characteristics. This is the default and recommended option for most use cases.
   • Global -- the algorithm learns which variation performs best across all customers without considering individual characteristics. Use this when you want a single "best" path for everyone.
8. If you selected 1:1 Personalization, choose a Features mode:
   • Selection -- you manually choose which customer features the algorithm should consider. When selected, a feature picker appears where you can choose up to 25 features from your primary dataset.

💡

Tip

Start with 1:1 Personalization and Automatic features. This gives the algorithm the most flexibility to find patterns. Switch to Selection only if you have domain-specific knowledge about which customer attributes should drive the optimization.

Add variations

9. Add variation paths by clicking the + icon on the decisioning node. Each variation represents a different journey path that customers can be sent down.
10. Name each variation by double-clicking its header text (e.g., "Email Offer," "Push Notification," "SMS Reminder").
11. Build out the downstream journey for each variation -- connect destination nodes, delay nodes, criteria nodes, or any other node types as needed. Variations can be simple (a single destination node) or deep (multi-step sub-journeys with criteria, delays, and multiple destinations).
12. (Optional) Add Custom Attributes to your variation nodes to write back which arm a customer was assigned to. This is useful when the downstream destination needs to know which treatment the customer belongs to -- for example, to serve different content in Braze or Iterable based on the assigned variation.
13. Save and Publish your journey to activate the decisioning node.

Once published, GrowthLoop begins assigning customers to variations, tracking metric outcomes, and writing optimization data to tables in your data cloud. The algorithm does not need to "see" the exact content served by downstream destinations -- it is agnostic to treatment context and learns purely from the metric outcomes.

Decisioning types explained

1:1 Personalization

In this mode, the algorithm considers individual customer characteristics when deciding which variation to assign. Two customers with different profiles may be routed to different variations, even at the same point in time.

For example, if you are testing an email offer against a push notification, the algorithm might learn that customers with high engagement scores respond better to push notifications, while less-engaged customers convert better through email offers.

This is what makes GrowthLoop's decisioning fundamentally different from downstream optimization tools (such as those built into ESPs): the algorithm has access to the full breadth of customer context in your data warehouse -- not just the limited signals available to a downstream platform. Combined with the ability to optimize across omni-channel journeys (not just a single channel's content or timing), 1:1 Personalization delivers more effective decisioning because it operates on richer data and a wider scope of interventions.

How features work

When using 1:1 Personalization, the algorithm needs customer attributes (features) to learn from. You have two options:

• Automatic -- GrowthLoop automatically determines which features to use for personalization. No configuration needed.
• Selection -- you pick specific columns from your primary dataset. Use this when you have strong hypotheses about what drives variation performance. You can select up to 25 features.

📘

Note

Features must have labels assigned in your primary dataset to appear in the feature picker. If no features appear, add labels to your dataset columns first.

Global

In Global mode, the algorithm treats all customers the same and learns a single "best" variation across your entire audience. Customer characteristics are not considered. Each variation maintains its own estimate of expected reward, and the algorithm shifts traffic toward the variation that performs best on average. Use Global when personalization is not expected to matter or when your audience is very homogeneous.

Read the results

As your journey runs and customers flow through the decisioning node, GrowthLoop collects data and refines its allocation strategy. You can monitor performance through Step Metrics on the decisioning node, which show how each variation is performing against your target metric.

The decisioning node tracks:

• How many customers have been assigned to each variation
• The observed metric value for each variation
• How the allocation is shifting over time as the algorithm learns

GrowthLoop writes detailed evaluation data to tracking tables in your own data cloud, within the GrowthLoop system schema. Your data never leaves your environment.

Example: optimizing a cross-sell journey

Here is a concrete example -- determining the best channel for a cross-sell offer.

1. Create a metric called "Cross-Sell Revenue" in the Metrics Builder. Choose the transactions Dataset, select the purchase_amount field, set the calculation method to Total, and pick order_date as the date field.
2. Create a journey for customers who recently purchased Product A. Set the entry criteria to customers with a purchase in the last 14 days.
3. Add a Decisioning node after the entry node. Select "Cross-Sell Revenue" as the metric to maximize.
4. Configure settings -- choose 1:1 Personalization with Automatic features.
5. Create three variations:
   • Variation 1: Email destination with a personalized product recommendation
   • Variation 2: Push notification with a limited-time discount code
   • Variation 3: SMS with a direct link to the recommended product
6. Publish the journey. GrowthLoop begins assigning customers to variations and tracking revenue outcomes.
7. Monitor results over the following weeks. The algorithm will learn which channel drives the most cross-sell revenue for different customer segments and automatically shift traffic toward the winning paths.

Why composable decisioning

Traditional approaches to marketing decisioning fall into two categories, both with significant limitations:

• In-house / intuition-based -- decisions are made based on correlational data or institutional knowledge. Without causal measurement, these approaches are as likely to decrease performance as to improve it.
• Downstream platform decisioning (e.g., built into ESPs or point solutions) -- models are trained off-premises on limited data, restricted to the intervention dimensions the platform controls (e.g., email content and timing only), and can grow stale between reverse-ETL sync cycles.

GrowthLoop's decisioning is composable: all model training, inference, and decision logic execute directly in your data cloud alongside your complete customer data. There is no external model service, no data leaving your environment, and no separate training schedule -- the model learns continuously with every journey run.

This means you can optimize over the full scope of your marketing programs (omni-channel, multi-step journeys) using the richest possible customer context, without the data integration overhead that downstream decisioning tools require.

Decisioning vs audience experimentation

GrowthLoop offers two approaches to intelligent experimentation, each designed for a different use case:

Use Decisioning when you want to continuously improve which journey path customers take. Use Audience Experimentation when you want to prove that a campaign is driving real, incremental impact.

Best practices

• Start with at least two variations that are meaningfully different -- different channels, different messages, or different timing. Small cosmetic differences are unlikely to produce learnable patterns.
• Choose a metric that reflects your campaign goal. If you are running a re-engagement journey, optimize for login count or session frequency rather than revenue.
• Give the algorithm time to learn. Meaningful optimization typically requires enough customers to flow through each variation. Avoid making changes to the journey or metric configuration while the algorithm is actively learning.
• Use 1:1 Personalization for diverse audiences. If your audience spans different customer segments with different behaviors, personalization gives the algorithm more signal to work with.
• Use multiple Decisioning nodes when your journey involves several independent decision points (e.g., which channel to use and which offer to show). Each node optimizes its own decision independently.
• Don't change the metric mid-journey. If you need to track a different KPI, create a new journey with the updated metric instead.

Frequently asked questions

How long until the algorithm starts optimizing? The algorithm begins learning from the first customers that flow through the decisioning node. Meaningful optimization typically starts once enough data has accumulated across all variations -- usually after several hundred customers have been assigned. The exact timeline depends on your journey's traffic volume and the variance in your metric.

How many variations can I add? You can add as many variations as you need. However, more variations means the algorithm needs more data to learn which ones perform best. We recommend starting with 2--4 variations for the best balance of exploration and optimization speed.

Where is the optimization data stored? GrowthLoop writes all decisioning and evaluation data to tracking tables in your own data cloud, within the GrowthLoop system schema. Your data never leaves your environment.

Can I use Decisioning with any journey schedule? Yes. Decisioning works with all journey schedule types -- one-time, always-on, recurring, and manual. The algorithm adapts to whatever traffic pattern your journey produces.

Does the AI need to know what content is served downstream? No. The decisioning algorithm is agnostic to treatment context -- it learns purely from the metric outcomes observed for each variation. You can use Custom Attributes on variation nodes to write back which arm a customer was assigned to, so downstream destinations can serve the appropriate content.

Can I have multiple Decisioning nodes in one journey? Yes. Each Decisioning node operates independently, optimizing its own set of variations against its own metric. This lets you make multiple optimized decisions within a single journey flow.

What happens if I change the journey after publishing? If you modify the journey structure or the decisioning node configuration, the algorithm may need to re-learn. Avoid making changes to a running journey unless necessary.

Congrats on setting up your first decisioning node! You're now automatically optimizing your journey paths for maximum impact.

📘

Note

Experiencing any issues? Reach out to us at [email protected] and we'll help resolve the matter.