Personalized Video Campaign Recipient Data Checklist

Start with a ready video template

Before you prepare a recipient list, make sure you have an AI Studio template with a source video and at least one variable. A campaign uses that template and recipient data to create personalized videos.

Decide which template variables need recipient-specific values. Your file columns or API fields must supply values for those variables.

Choose how to supply recipient data

Use CSV or Excel for a batch list, a one-off campaign, or a quick test. Use an API when your product or backend needs to control generation. Other supported routes include Zapier, Pabbly, and Leadr; choose based on how your workflow sends data to BHuman.

The setup interface currently exposes CSV/Excel, Zapier, and Leadr. Pabbly and API are integration paths, so they may not appear as choices in that interface.

• CSV or Excel: prepare a spreadsheet with one column per variable.
• API: send variables as ordered fields and each recipient as a row of values.

CSV and Excel checklist

For a spreadsheet campaign, keep the headers clear and stable, then use one column for each template variable. BHuman previews uploaded rows so you can map columns to variables before generation.

Try a small test file before uploading a full list. If you use background mode, include the needed URL columns for those assets.

• Use a header for each variable you plan to map.
• Trim header names and keep them consistent.
• Make sure every row has a value for each mapped variable.
• Send only the replacement text—not fixed words already in the video script. For example, use “Erada” for a first_name variable, not “Hi Erada.”
• If using background mode, prepare the required asset URLs or uploads for each timed segment.

API checklist

API campaign data uses an ordered variables array and a names matrix: each nested array represents one recipient, with values in the same order as the variables. Keep background asset rows in the same order as recipient rows if you use API background assets.

REST API access is in beta, and production REST credential provisioning is on hold pending qualification. Fresh-account access and some other integration areas are not fully qualified. Confirm your use case with support before production use. The REST path requires an existing AI Studio template or campaign; it does not create a Speakeasy presenter video from a prompt.

• Check that each recipient row has one value for every variable, in the matching order.
• Send only replacement values, without the template’s fixed words.
• For structured campaign requests, explicitly set generation_mode to keep_original or full_script.
• Start with one recipient row; the API guide recommends beginning with one.

Check mappings before you generate

Before generation, verify that every required template variable maps to a column or payload field, that each mapped field exists, and that every row has a value for it. BHuman’s campaign setup validates the campaign before sending it to the render pipeline.

If your campaign uses background mode, check that the needed backgrounds are covered. Generation also depends on account availability and sufficient quota.

• Confirm your source video and data source are attached to the campaign.
• Check the required variable mappings and recipient values.
• Check background coverage and required background assets if applicable.
• Review account availability and quota before generating.

A simple choice rule

Choose CSV or Excel when you have a list to upload, want to test a few rows, or are running a one-time batch. Choose an integration route when another app or your own product should trigger generation. An API gives your product or backend direct control, but it requires integration setup and, for REST, access qualification before production use.

Next step: map a small test batch

Once your recipient data is ready, connect it to a campaign, map each variable, and review the row preview before generating. For the documented CSV/Excel workflow, a small test file is a useful way to check the mappings before uploading a full list.

See BHuman’s [campaign setup guide](https://www.bhuman.ai/docs/campaigns) and [data-source guide](https://www.bhuman.ai/docs/data-sources) for workflow details. If you are considering the REST API, read its beta and qualification notes before planning production use.