Interactivity Basics

Plan buttons, links, branches, inputs, forms, and player events in an MP5 experience

Interactivity turns an MP5 from a personalized video into a viewer journey. A viewer can choose, click, type, submit, branch, or trigger custom behavior, and the project can route the next scene based on data or action.

Use this guide to understand the main interaction patterns before configuring connectors.

Interaction Types

Interaction	What it does	Main tools
Open a destination	Sends the viewer to a URL, email action, phone action, or dynamic link.	Open Link connector, data fields, tracking links.
Jump inside a scene	Moves the viewer to a specific frame or moment in the current scene.	Jump to Frame connector.
Branch to another path	Sends the viewer to another scene, timeline path, or lineup.	Branch Timeline connector, Scene Offset connector, Flow Map conditions.
Show or hide content	Changes what is visible based on viewer data, live controls, or logic.	Layer Hide connector, conditions, expressions.
Collect typed input	Lets the viewer enter text inside the MP5.	Input Field connector.
Submit a form	Sends viewer-entered values to Form Data or custom handling.	Submit Form connector, Platform Form Data.
Trigger custom code	Runs logic on player events or connector expressions.	Expression connector, Player Events connector, SDK event handling.

How to Plan an Interactive Flow

1

Define the Viewer Decision

Write the exact action the viewer should take: click a CTA, choose an answer, enter a value, submit a form, or continue to another path.

2

Choose the Runtime Result

Decide what happens after the action: open a link, show a message, jump to a frame, branch to a scene, save a form submission, or trigger custom logic.

3

Identify the Data Needed

List the fields, live controls, URLs, labels, answers, and submitted values needed to support the interaction.

4

Configure Connectors in Studio

Add the connector that matches the action and bind it to the right layer, field, fallback value, success state, and validation behavior.

5

Validate in Studio and Platform

Test normal actions, empty values, invalid values, repeated clicks, mobile behavior, alternate branches, and analytics expectations.

Interaction QA Checklist

Before launch, confirm:

• Every clickable layer is visible, readable, and easy to activate.

• Every branch has a clear next scene or fallback path.

• Every link has a valid destination and tracking plan.

• Every input has a field name, placeholder, empty-state behavior, and submit path if needed.

• Form submissions have approved storage or custom handling.

• Analytics and conversion events match the campaign goal.

• Platform simulation covers each important path.

Deep Dives

ConnectorsFlow Map basicsCollect Viewer Data