Learn the core MP5 concepts behind personalized and interactive Blings videos
MP5 is the Blings runtime format for dynamic, interactive video experiences. Instead of playing one fixed video file, the MP5 player combines a template, data, logic, and viewer actions when the experience loads.
Use this guide to understand the core building blocks before opening Studio, Platform, or developer documentation.
An MP5 project is a structured experience:
Scenes define video sections, moments, or steps in the viewer journey.
Layers hold text, media, shapes, buttons, input fields, and other visual elements.
Connectors make layers dynamic or interactive.
Data provides viewer-specific and project-level values.
Lineups and flow maps decide which scenes play and in what order.
Player settings control runtime behavior such as loading, autoplay, timeline, colors, and story mode.
Analytics and events measure how viewers interact with the player.
The creative template can include placeholders or bindings for values such as:
First name.
Product image.
Offer amount.
Renewal date.
Store location.
CTA link.
Brand color.
Eligibility state.
At runtime, the player receives data from the configured delivery method. Connectors use that data to update text, media, colors, visibility, links, routing, and other behavior.
Interactive MP5 experiences can respond to viewer actions:
A button can open a link.
A choice can jump to another frame or route to another scene.
A condition can branch based on viewer data.
An input field can collect text.
A submit action can send form values.
A player event can trigger custom logic or analytics.
Fixed rendered file.
Runtime experience assembled from template, data, and logic.
Personalization usually requires many rendered files.
One project can support many viewer states.
Interactivity is limited to the surrounding web page.
Interactivity can live inside the video experience.
Updates often require a new render.
Approved data, content, controls, routing, and settings can be updated through Blings workflows.
Measurement often depends on basic video events.
Projects can track player events, scenes, CTAs, form submissions, and conversion behavior.
Last updated
