How to Plan Recipient Fields for a Personalized Video Campaign

Start with the video, not a long contact list

To plan recipient fields for a personalized video campaign, first decide what should change for each person in the video. Create a field only for a spoken phrase, link, image, background, or other value that your template needs. BHuman campaign rows supply variable values for individual generated videos.

Write down the personalized moments in the template, then list the value needed for each one. Keep fixed wording in the template rather than repeating it in a recipient field.

Choose clear, stable field names

Use lowercase snake_case names such as first_name, company, or cta_url. Name a field for its meaning, not for one campaign example, and keep the same name across the template and the data source. Avoid spaces, punctuation, duplicate names that differ only in capitalization, and vague names such as url when the field has a specific purpose.

Use separate fields when values serve different purposes—for example, booking_url for a scheduling destination and asset_url for a media asset. This makes the mapping easier to understand and maintain.

• Recipient name: first_name
• Organization: company
• Call-to-action destination: cta_url or booking_url
• Row-specific background media: a clearly named asset field

Match each field to a template variable

In AI Studio, select the phrase or media slot that should change and name it. In campaign setup, map that variable to the matching column or payload field. Exact header matches may be selected automatically; still review the mapping before generating.

Send only the replacement value. If the template says “Hi” before {first_name}, the field should contain a name, not “Hi” plus the name. Otherwise, the fixed greeting can be repeated in the video.

Prepare your recipient data

For a manual batch, you can use a CSV or Excel file; its headers become mapping options. BHuman also documents campaign inputs through Zapier, Leadr, Pabbly, and API workflows. Choose the input that fits how your team supplies campaign data.

Keep each row focused on one recipient’s values for the variables you mapped. Check that every mapped field has a value in each row. Empty rows are skipped when parsed, and a missing mapped column or blank mapping can stop generation before the render request is sent.

Test sample rows before generating the batch

Generate a few rows and review how each replacement sounds and fits. Check pronunciation, timing, subtitles, and any row-specific background assets. Short spoken replacements are generally easier to time predictably than long sentences.

For example, imagine a template that says, “Hi {first_name}, book a time here: {booking_url}.” A row might supply a first name and that recipient’s scheduling link. This is a hypothetical example; make sure the template’s fixed wording and your field values do not repeat each other.

Use this planning checklist

Before you launch, use this checklist to catch mismatches between the template and the recipient data.

• List every spoken or media element that changes by recipient.
• Create one clearly named variable for each distinct value.
• Use the same stable variable name in the template and data source.
• Map every required variable to a source column or payload field.
• Check that each campaign row contains the mapped values.
• Test a few rows and review speech, timing, subtitles, and media.