Personalized Video Campaign Example Using Fictional Data

A fictional personalized video campaign example

Imagine a fictional sales team preparing a short video for three fictional recipients. Its template includes a variable called `first_name`, and its CSV contains a `first_name` column with the values Maya, Jordan, and Sam. Each row supplies the replacement value for one personalized video; the fixed words in the template stay in the template. This is an illustrative example, not a real campaign or a claim about results.

Prepare the template and recipient data

Start with a ready AI Studio template that has a source video and at least one variable. For the example, the template variable is `first_name`. Create a small CSV with one column for that variable and one fictional recipient per row.

Keep the column header stable and use one column per variable. Put only the text that replaces the variable in each cell: enter `Maya`, not a full greeting such as “Hi Maya.” Before using a full list, test with a small CSV and preview its rows.

Map the CSV and generate a small batch

In BHuman, create a campaign from the ready template, choose CSV or Excel as the data source, and load the small test file. Map each template variable to its matching column; exact header matches may be selected automatically. Check that every required variable is mapped and every row has a value before generating.

Choose Mini or Max for the viewing mode. Mini places the presenter over backgrounds and needs background coverage for personalized moments; Max produces full-screen HD and may be restricted by plan limits or face-distance checks. Review the campaign’s validation and account quota before you submit. Generation runs asynchronously, so check the generated results for statuses such as queued, processing, succeeded, or failed.

When an API workflow fits

Use the API when your product, CRM, backend, or form handler needs to control generation. The documented REST flow works with an existing AI Studio template or campaign; it does not create a presenter video from a prompt. Prepare the source video, configure its variables, and create the campaign in AI Studio first.

For a fictional one-recipient example, an API request could pair the variable `first_name` with the value `Maya`. The API uses ordered variable names and recipient rows, and generation is asynchronous. API access remains in beta, and production REST release verification is on hold; fresh-account access and some credential and credit scenarios are not fully qualified. Confirm your use case with support before production use.

An accepted request only queues work. Save the returned generation ID and check its status rather than treating acceptance as a finished video. Review the campaign’s credit cost and available balance first; repeating a paid POST can create additional work and charges, and the documentation does not provide an idempotency key.

Choose the workflow that matches your campaign

For a one-off list or a quick test, CSV or Excel is the direct choice. If a connected app event should trigger generation, Zapier is intended for that workflow. For product- or backend-controlled generation, the API is the documented route, but its beta and production-access restrictions matter. Choose based on how recipient data reaches BHuman and how much control your workflow needs—not on assumed performance results.

Keep the example honest and useful

Label sample names and scenarios as fictional wherever you reuse them. Don’t present this example as a customer story, testimonial, measured outcome, or guarantee. When planning a real campaign, map only the variables you need, test a small batch, and review the template, data, backgrounds, and available quota before generating.