A variable is a field of your audience
Name, city, company — whatever your list carries. It becomes a variable the moment you use it, whether as on-screen text or as a slot of clips.
Personalization
"Hi Adam, welcome to Warsaw" is one script, one slot swapped, and a finished file waiting for each person.
Name, city, company — whatever your list carries. It becomes a variable the moment you use it, whether as on-screen text or as a slot of clips.
Order the pieces once. Each slot is either a clip everyone sees or a clip chosen per viewer, and the build works out every combination for you.
A viewer who matches nothing gets the default value, and text with nothing to fill in reads the variable's own name instead of an empty gap.
Renders are made up front, not stitched while someone waits: the build enumerates every combination your script implies and renders each one, so at play time the viewer is served a finished file. That also means the arithmetic is worth watching — three variables with ten values each is a thousand renders.
The variables inventory is a section of the project, not a register you fill in first, and a variable is born from use: a text element, a slot in a script, or a column you named during a CSV import.
Give them a way to say it. We'll walk through what Wall of Voice could look like for your audience.
See what Wall of Voice could look like for your audience.