How personalized video works
There are two fundamentally different approaches to generating personalized video content.
Server-side rendering
In the server-side model, a batch process runs before the campaign is distributed. The platform pulls customer data, renders a unique video file for each recipient, stores those files in cloud infrastructure, and distributes links to individual recipients. By the time a customer clicks and watches, they are watching a pre-existing video file.
This approach gives creative teams high control over cinematic output, and it is well-suited to one-time campaign productions. Its limitations become significant at scale: the cost of rendering grows linearly with volume, every video file contains data that was accurate at render time (not at view time), and the customer’s PII is processed on a third-party server.
Client-side generation (On-Device Generation)
In the client-side model, no video is rendered in advance. The platform stores a Dynamic Master Template: the visual design, animation logic, and data schema for the personalized content. When a recipient opens the communication, the template pulls live data from the client’s own CRM or CDP and generates the personalized video directly on the viewer’s device, at the Moment of Open.
This is the architecture that Blings pioneered with its MP5 Format. An MP5 file is not a traditional video file. It functions like live code: always current, always connected to the live data source, and never stored as a static asset in a third-party environment.
The consequences of this approach are significant:
- Data accuracy at the Moment of Open: A loyalty email opened three weeks after send shows the customer’s current points balance, not the balance from three weeks ago. This eliminates Data Decay.
- Zero-Knowledge Architecture: Because the video renders on the viewer’s device using a live connection to the client’s own infrastructure, the personalization platform never sees or stores the customer’s PII.
- Scale economics: One Dynamic Master Template generates millions of unique versions without proportional cost increases. Infrastructure Pricing replaces per-render fees.