Branch Timeline

Configure interactive routing from one scene path to another scene or timeline entry point

Use Branch Timeline when a viewer action should send the experience to another scene or timeline path. This connector supports interactive stories, choice-based flows, quizzes, product paths, and alternate narrative routes.

Options

Option	What it controls	Notes
Trigger layer	The clickable or interactive layer that chooses the branch.	Use a clear button, hotspot, or interactive element.
Target scene	The scene that should play after the interaction.	Confirm the scene exists and starts at the intended moment.
Entry point	The exact point in the target scene or timeline path.	Use when the branch should enter after an intro or at a specific frame.
Timeline sequence	The new scene order after the branch.	Validate the full path, not only the first target scene.
Duplicated scenes	Alternate scenes created for different branch outcomes.	Duplicate only when the branch needs different content or timing.
Data or expression source	Optional logic that chooses a branch from data or code.	Use when the path depends on viewer data instead of a direct click.
Fallback path	The path used when no branch is selected or the source value is invalid.	Keep a default route so the experience can continue.

Configure a Branch

1

Define the Branch Outcome

Decide what each viewer choice or data state should lead to before editing the connector.

2

Select the Trigger Layer

Choose the layer that represents the viewer action, such as a button for Dogs or Cats.

3

Set the Target Scene

Choose the scene and entry point that should play after the interaction.

4

Confirm the Timeline Path

Review the sequence that follows the target scene so the branch continues coherently.

5

Preview Every Branch

Test each branch outcome, including the default path and any missing-data state.

Success Checks

Before publishing Branch Timeline, confirm:

• Every visible choice has a valid target scene.

• Each branch starts at the intended entry point.

• Returning or continuing from the branched scene follows the expected timeline.

• The default route works when no branch is selected.

• Platform flow and simulation checks still match the Studio routing.

Data in Studio