How to Keep Personalized Video Details Accurate: A Pre-Send Workflow

Start with the exact detail each video should change

To keep personalized video details accurate, define what changes per recipient, check that each source value matches its intended variable, and review test videos before generating the full campaign.

In BHuman, variables connect a template to campaign rows or API payloads. They can represent spoken text, a call-to-action URL, a background URL, an image, or another row-specific value.

1. Name variables by meaning

Mark the phrase or media slot that should change in your template, then give it a stable, readable name. Use lowercase snake_case, such as first_name, company, or booking_url.

Use separate variables for different meanings. For example, avoid a generic name like url if one value is a booking page and another is a product image. Keep names stable after a campaign or automation is live.

• Use one clear variable for each changing detail.
• Avoid spaces, punctuation, and names that differ only by capitalization.
• Use separate variables when text and media need different values.

2. Prepare recipient data to match the template

For a CSV or Excel campaign, make each column header correspond to the variable it supplies. In API data, match payload field names to the template variables. BHuman can select exact header matches automatically when possible, but you still need to review the mapping.

Check each row for the right value in the right field. A first_name value should contain the recipient’s name, not a greeting that is already fixed in the video template. Empty rows are skipped when parsed.

• Check spelling, company names, links, and any other details you plan to personalize.
• Remove fixed template words from spoken-variable values. If the template says “Hi” before {first_name}, send a name such as “Erada,” not “Hi Erada.”
• Use the right kind of value for each variable, such as a destination link for booking_url.

3. Map every variable to its intended source

In campaign setup, choose a data source and map each template variable to the matching CSV column or payload field. Check the mapping by meaning, not just by similar-looking names.

Campaign generation requires at least one configured variable. If a mapping is blank or its source column is missing, generation stops before the render request is sent. Campaign validation also checks that each row has values for mapped variables.

4. Test a few rows and watch the details

Generate a few representative rows before a larger batch. Review the replacement in the video for pronunciation, timing, subtitles, and any background assets. A correct cell can still sound or look wrong in the finished video, so check the rendered result.

Keep spoken variable replacements concise when you can; short variables produce more predictable timing than long sentences. If subtitles or manual timing are used, review transcript timing too.

• Include a typical row and any row with unusually long names or text.
• Check that fixed words are not repeated in the spoken replacement.
• Confirm personalized links or media appear in the intended places.

5. Review campaign readiness before generating

Before submitting a campaign, check the source video, data source, variable mappings, and row values. If you use Mini mode, BHuman’s campaign checks also require background coverage for personalized moments. Background-mode rows need valid URLs or uploads for each timed segment.

Generation is asynchronous. After submitting, use the generated videos page to monitor statuses such as queued, processing, succeeded, failed, or needs-review. This helps you spot rows that need attention; it does not replace checking that the recipient details are correct.

• Confirm the selected source and mappings are the ones you intend to use.
• Review row values and any row-specific media or links.
• After generation, inspect results marked failed or needs-review and review video content for accuracy.

Choose the right level of checking

For a small, one-off batch, manually reviewing the spreadsheet and a few test videos may be practical. For repeated campaigns or API-driven workflows, stable variable names and repeatable field mappings make the process easier to maintain—but they do not guarantee that incoming data is correct.

Use a deeper review when mistakes would be especially disruptive, such as when a spoken name, company, or destination link must be right. Check both the input value and the rendered video.