Personalized Video Campaign CSV Preparation Checklist

Start with the video template

Before building your CSV, check which parts of the video change for each recipient. In BHuman, campaign data maps to variables in an AI Studio template, so the template determines what your file needs to contain.

• List each personalized value, such as a recipient’s name, company, or call-to-action URL.
• Give each variable a clear, stable name, such as first_name, company, or cta_url.
• Add a CSV column for each variable you plan to map.

Name and organize your headers

Use one column per variable and keep headers consistent with the template. BHuman recommends lowercase snake_case names, with no spaces or punctuation. Stable, distinct names make columns easier to map and maintain.

• Good: first_name, company, booking_url.
• Avoid duplicate headers or names that differ only by capitalization.
• If you use a background asset for a personalized scene, include a separate column for its URL or other required asset value.

Put only the replacement text in each cell

Each cell should contain only the value that replaces the variable—not the fixed words already spoken in the video. If the template says “Hi {first_name},” enter “Erada,” not “Hi Erada.” Otherwise the greeting could be repeated.

• For a company variable, enter the company name, not a full sentence such as “welcome to BrushandChemistry.”
• Use short replacement text where possible; long spoken values can be less predictable for timing.
• Check spelling, capitalization, and pronunciation in names and other spoken values.

Check rows and any asset columns

Review every row you intend to use. BHuman’s campaign checks require values for mapped variables, and its documentation says empty rows are skipped when parsed. If you use background mode, make sure the needed background columns and row-specific assets are present before generation.

• Look for blank values in required mapped columns.
• Check that each row’s value belongs to the right recipient and variable.
• If using background mode, check the asset values for the relevant timed scenes; campaign validation checks for valid URLs or uploads.
• Keep reserved output columns—such as status, share, download, GIF, or thumbnail—from being mistaken for input variables; BHuman ignores these reserved headers.

Run a small test before the full batch

Start with a small test CSV, then upload it and preview the rows. Map each template variable to the intended column and generate a few videos before using the full list. Review pronunciation, timing, subtitles, and any background assets.

• Confirm every required template variable has a mapped column.
• Check that mapped columns exist and contain the intended replacement values.
• Review the generated videos for repeated words or awkward timing.
• Fix the file or mapping and test again before sending a larger batch.

Example CSV structure

For example, imagine a template with the spoken line “Hi {first_name}, welcome to {company},” plus a booking link. A simple file might look like this:

• first_name,company,booking_url
• Erada,BrushandChemistry,https://example.com/book
• Sam,Northstar,https://example.com/meeting

CSV or another data source?

CSV or Excel works well for batch generation, quick tests, and one-time lists. If another app should trigger generation, BHuman also documents Zapier; Pabbly and API are options for object-style webhook or product-controlled workflows. Choose CSV when you want to prepare and review a list as a batch.