> For the complete documentation index, see [llms.txt](https://help.blings.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blings.io/guides/blings-value-and-use-cases.md).

# Blings Value and Use Cases

Blings helps teams create personalized, interactive MP5 videos that render on the viewer device in real time. Instead of producing a separate static video for every viewer, one MP5 template can respond to data, viewer actions, runtime conditions, and project settings.

Use this guide to understand why teams choose Blings, which use cases fit well, and where to go next.

## What Blings Changes

Traditional video is usually fixed after rendering. If a name, offer, date, image, CTA, or route needs to change, a new file often needs to be produced or hosted.

Blings separates the experience into:

* **Creative template**: scenes, animation, media, text layers, interactions, and layout.
* **Data**: viewer fields, live controls, catalog rows, URLs, CRM values, SDK payloads, and form submissions.
* **Runtime player**: the MP5 player that combines the template and data when the viewer opens the experience.
* **Operations layer**: Platform tools for testing, delivery, analytics, editing, and optimization.

The result is one managed experience that can feel specific to each viewer without pre-rendering a unique MP4 for every person.

{% content-ref url="/pages/nTrHNC24U6PfxhINUbAi" %}
[MP5 Basics](/guides/mp5-basics.md)
{% endcontent-ref %}

## Common Value Drivers

| Driver          | What it means in a Blings project                                                                                              |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Personalization | Names, account details, products, offers, dates, locations, loyalty status, and other viewer data can change inside the video. |
| Interactivity   | Viewers can click, choose, type, branch, submit forms, open links, or move through alternate scene paths.                      |
| Speed to update | Approved copy, media, live controls, and project settings can be changed without rebuilding the entire creative system.        |
| Data alignment  | The project schema, connectors, integration payload, simulation profiles, and analytics all use the same field model.          |
| Measurement     | Plays, engagement, conversion, watched scenes, CTAs, and optimization results can be reviewed from the project.                |
| Scale           | Client-side rendering avoids a separate server-rendered file for each viewer state.                                            |

## Use Cases That Fit Blings

| Use case                  | Example                                                                                          |
| ------------------------- | ------------------------------------------------------------------------------------------------ |
| Onboarding                | Welcome a new customer by name, show the right first steps, and route them by product or plan.   |
| Loyalty and retention     | Show points, tier status, renewal dates, usage milestones, or next-best offers.                  |
| Promotions                | Personalize discounts, product recommendations, availability, campaign deadlines, and CTA links. |
| Customer education        | Branch the viewer into different explainers based on profile, answers, or product context.       |
| Feedback and lead capture | Ask questions, collect preferences, submit contact details, or route viewers after a response.   |
| Transactional updates     | Turn account, order, appointment, renewal, or service data into a visual update.                 |
| CRM campaigns             | Insert tokenized links or thumbnails into email, SMS, WhatsApp, or marketing automation flows.   |
| Product or web apps       | Embed the MP5 player with SDK data and event handling inside an application surface.             |

## When Blings Is a Strong Fit

Blings is a strong fit when the video experience depends on at least one of these:

* Viewer-specific data.
* Branching or interactive choices.
* A form or submitted response.
* A campaign that needs testing, analytics, or optimization.
* A delivery channel that benefits from personalized links or thumbnails.
* A creative template that should be reused across many viewers, brands, markets, or segments.

If the experience is a single fixed brand video with no data, no interaction, and no need for runtime measurement, a regular MP4 may be enough.

## Where to Go Next

Read the ecosystem guide to understand which Blings app owns each part of the workflow.

{% content-ref url="/pages/CfL2TwMhsVPG5F5VAub3" %}
[Ecosystem and Apps](/guides/ecosystem-and-apps.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.blings.io/guides/blings-value-and-use-cases.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.