Understand the Blings app ecosystem and how each product surface fits the workflow
Blings has multiple product surfaces. The important first distinction is between the self-serve Blings app and the enterprise Platform and Studio workflow.
Use this guide to decide which app or tool owns the work in front of you.
Blings app
The self-serve app covered by the main Help Center.
You are creating template-based self-serve videos, managing simple projects, or following self-serve Help Center workflows.
Blings Platform
The enterprise operating workspace for MP5 projects.
You need analytics, editable content, flow management, data schema, live controls, catalog, simulation, integration, player settings, form data, or optimization.
Blings Studio
The enterprise visual editor for MP5 experiences.
You need to inspect or change scenes, layers, timing, assets, connector behavior, data bindings, flow maps, previews, or publishing state.
After Effects extension
The creator workflow for converting motion design work into MP5 project material.
A designer is building or updating animation in Adobe After Effects before sending compositions into Blings.
SDK and API tools
Developer implementation surfaces for embedding, controlling, and personalizing the MP5 player.
A website, app, CRM, backend, or custom integration needs to pass data or handle events programmatically.
CRM and marketing apps
External systems that deliver links, tokens, thumbnails, campaign messages, and viewer data.
A campaign is delivered through tools such as Braze, Salesforce Marketing Cloud, HubSpot, Iterable, Klaviyo, AJO, Marketo, or another CRM.
The self-serve Blings app is not the same workflow as enterprise Platform and Studio. Enterprise Flow Map, Studio connector setup, SDK implementation, and Platform operations belong in the enterprise docs.
Last updated
