Separate connected journey per matching product (Product Scoping Rules)
This release introduces a new configuration option for Product Scoping Rules of type Connected Journey, allowing you to control whether matching products are grouped into a single connected journey or launched into separate connected journeys.
What’s new
A new toggle is available on Scoping Rules Configuration for Connected Journey rules:
- Separate journey per matching product
- Off (default): Current behaviour is unchanged. All products matching the rule are grouped into one connected journey
- On: When the Product Journey Launchpad task is triggered, the platform creates a separate connected journey for each individual product that matches the rule
Why this matters
Previously, connected journeys were always grouped per matching rule, which is efficient for region or product-family rollups. This enhancement supports scenarios where each product must follow its own parallel process from launch, even when scoping characteristics are shared.
How it works
- The toggle is available only for Product Scoping Rules of type Connected Journey.
- The toggle does not apply to Product Scoping Rules of type Task Display.
- Behaviour is evaluated when the Product Journey Launchpad task runs and evaluates products against Connected Journey Product Scoping Rules.
Versioning and backwards compatibility
- The toggle is Off by default for:
- new rules
- new versions of existing rules
- The toggle is also visible in read-only views of historical published versions created before this release (for consistency and auditability).
Permissions
No new permissions are introduced. Viewing and editing this toggle is governed by existing permissions for creating and editing Product Scoping Rules.