Flow Map basics

Build and review lineups, scene routing, and publishable Flow Map changes

Flow Map controls how viewers move through an MP5 experience. Use it to connect scenes, create lineups, keep the project map readable, and save routing changes to the project draft before publishing.

The Flow Map surface belongs to the Platform project workspace and is also available from Studio. When you select Flow Map in Studio, Studio opens the same Platform Flow Map for the project so routing stays in one shared place.

Open from Studio

Open the project in Studio, then select Flow Map from the project bar. Use the Studio entry point when scene edits, connectors, data bindings, or visual changes need to be checked against the full project flow.

Open from Platform

How the Flow Map Works

Every item on the canvas is a node. Every line between nodes is a connector. The player follows connectors from left to right unless a condition or A/B test sends the viewer to a different branch.

Flow Map canvas with lineups, scenes, condition branches, and publish controls.

Element	What it does
Lineup	A named playable flow. A project can have one main lineup and additional lineups for alternate entry points or reusable sequences.
Scene node	Represents a scene viewers can watch. The scene can contain text, media, personalization, buttons, and interactive elements.
Connector	Sends the viewer from one node to the next. A regular connector continues the default path. A branch connector follows a named condition or variant outcome.
Condition node	Evaluates viewer data or a date rule and sends the viewer to the matching branch. See Conditions.
A/B test node	Randomly assigns viewers to variants according to the traffic percentages you define. See A/B tests.
Canvas layout	Stores where nodes appear on the canvas. Moving nodes changes readability, not playback logic.

A lineup starts the path, then connectors send viewers through the scene sequence.

Disconnected nodes can stay on the canvas as drafts, but viewers do not reach them until they are connected to a lineup path.

Build a Basic Flow

1

Open Flow Map

Open Flow Map from Platform or from the Studio project bar. The canvas shows the lineups, scenes, connectors, and any branching nodes already configured in the project.

2

Choose the Starting Lineup

Find the lineup that should start the viewer journey. The main lineup is usually the primary entry point for the project.

3

Connect the First Scene

Drag from the lineup output handle to the scene input handle. The connector tells the player where to go first.

4

Add the Next Scenes

Continue connecting scenes in playback order. Keep the main path moving left to right so it is easy to scan.

5

Preview the Path

Preview the experience and confirm that each scene appears in the expected order. Test again after every branching change.

Add and Arrange Nodes

Use the canvas controls to add lineups, organize the map, and adjust visual grouping. A lineup is added as an unsaved draft node until you save the Flow Map.

Add a lineup from the top-left canvas control.

Use Auto organize and Scene colors from the bottom-left canvas controls.

Recommended layout practices:

• Keep the default path moving from left to right.

• Put branch outcomes vertically above or below the condition that creates them.

• Give scenes outcome-based names, such as Welcome - New Customer or Offer - Returning Customer.

• Keep unused draft scenes disconnected until they are ready for viewers.

• Use Auto organize when the map becomes hard to scan.

• Use Scene colors when visual grouping helps distinguish scene groups or branches.

Add Branches and Tests

Use conditions when routing depends on viewer data, dates, URL parameters, or other runtime values. Use A/B tests when the viewer should be assigned to one of several variants by traffic percentage.

ConditionsA/B tests

Save, Preview, and Publish a Flow

Flow Map edits are saved to the project draft. Publishing makes the draft flow available to viewers.

Save draft changes first, then publish when every path has been tested.

Before publishing:

• Preview the main lineup from the start.

• Test every condition branch, including fallback branches.

• Test each A/B test variant path.

• Confirm disconnected nodes are intentionally unused.

• Check that every path reaches a valid ending.

• Confirm personalized fields used in conditions are available in your project data.

Draft Preview and PublishingSimulation