How personalized video data flows from your CRM to the screen

Every personalized video starts as a row in your CRM. The customer’s name, their plan, their nearest store, and the number of points they have left all live in the system you already use every day. This post explains how that data becomes a video on the customer’s screen, and what happens to it along the way.

The short version: the data travels the same path your text personalization already takes. If you can merge a first name into a subject line, you already understand most of how a Smart Video gets personalized.

Where the data starts: your CRM

Nothing new has to be collected. A Smart Video reads from the same contact, account, and event fields your email and SMS campaigns already use. In Blings, these mapped fields are called Dynamic Data, and each one has a name that matches a field in your CRM.

Before a campaign goes out, you confirm those field names once in the Blings Platform. After that, the CRM remains the single source of truth. When a customer’s points balance or plan changes in your system, the next video they open reflects the change, because the data is read at open time rather than baked in weeks earlier.

How the data moves: merge tags and the Smart Video Link

The connection between your CRM and the video is a link: the Smart Video Link. You paste it into an existing campaign the same way you paste any other URL. What makes it personal is the merge tags you attach to it.

A merge tag is the placeholder your CRM already swaps for real values at send time, such as a first name token in a subject line. Blings uses those same tags. You keep the parameter name that Blings expects, and you fill the value with your CRM’s own merge-tag syntax. The result looks like this:

https://yourbrand.mp5.live/onboarding?first_name={{ contact.firstname }}&plan={{ contact.plan }}

When the recipient clicks, the CRM resolves the tags into real values and the Smart Video receives them as part of the link. No export, no upload, and no separate video file. For channels where a short link matters, such as SMS, several fields can be packed into a single compact token instead of a long string of parameters.

What happens at the Moment of Open

On-Device Generation means the video is assembled on the recipient’s own device the instant they open it. Blings calls this moment the Moment of Open. There is no queue and no waiting for a server to produce a file for each person.

This is why the approach scales. A brand with hundreds of thousands of contacts does not generate hundreds of thousands of video files. It publishes one Smart Video template, and each viewer’s device assembles their version on demand from the data in their link. The creative and the data stay current without a re-send.

Where your customer data actually goes

This is the question most data and security teams ask first, and the answer is short. Because the video is generated on the device at the Moment of Open, Blings never sees or stores your customer’s personal data. The values travel from your CRM, through the link, to the viewer’s device, and the assembly happens there.

This is the Zero-Knowledge Architecture. If a field is sensitive enough that it should not appear in a URL at all, you have two options: pack it into a compact or signed token, or use a CRM-hosted landing page that injects the data into the player after the page loads so it never touches the link. Both keep the data under your control.

A worked example, field by field

Here is the same journey for four common fields, from the row in your CRM to what the customer actually experiences.

Every value is a field you already hold. The video simply reads it at the moment the customer presses play.

What you need to get this running

• The fields you want to use, mapped once. Confirm the Dynamic Data field names in the Blings Platform so they match your CRM.
• The Smart Video Link, copied from the Platform. This is the URL you will place in your campaign.
• Your CRM’s merge-tag syntax for each value. Keep the Blings parameter name, and fill the value with your tool’s token.
• One end-to-end test send. Send a real message to a test contact, open it, and confirm every tag resolved.

That is the whole journey. Your data never leaves your control, your CRM stays the source of truth, and the customer sees a video built around them the instant they open it. Build once, personalize forever.