How to Map CRM Fields for Video Personalization: A Step-by-Step Guide

Map CRM data to video variables

To map CRM fields for video personalization, decide what should change in the video, give each change a stable variable name, then connect that variable to the matching value in your data. BHuman campaign data can come from a CSV or API; the mapping connects source columns or payload fields to template variables.

A useful mapping does more than match labels. It ensures each value fits the place it replaces, and that required values are present before you generate videos.

1. Choose what changes for each recipient

Start with the parts of the video that should vary by recipient. A variable can hold spoken text, a call-to-action URL, a background URL, an image, or another row-specific value. Keep fixed wording in the template and personalize only the changing part.

For example, if the template says “Hi {first_name}, welcome to {company},” the data should provide just the recipient’s name and company—not the full greeting.

• first_name: the recipient’s name
• company: the recipient’s organization
• cta_url: the next-step link
• asset_url: an image or video URL used in a background scene

2. Name variables clearly and consistently

Use readable, lowercase snake_case names such as first_name or booking_url. Name a variable for what it means, not for a single campaign example, and keep the name stable once a campaign or automation is live.

Use separate variables for different kinds of values. For example, booking_url and product_url are clearer than a generic url. Avoid spaces, punctuation, and names that differ only by capitalization.

3. Prepare your CSV or API data

For a CSV, use a header for each variable and put one recipient’s values on each row. For an API workflow, use payload fields that correspond to the template variables. BHuman campaign setup maps columns or payload fields to those variables; exact header matches can be selected automatically when possible.

Keep each cell or field limited to the value that replaces the variable. Empty rows in parsed CSV data are skipped. Check that the fields you intend to use are present and that each recipient has a value for every required variable.

4. Build a field-mapping worksheet

Before connecting data, list each template variable beside the CRM field or data value that should supply it. This worksheet is a planning aid, not an interactive BHuman tool. Use it to catch unclear names, mismatched value types, and missing data before campaign setup.

• Template variable: first_name | Source field: recipient first name | Example value: Erada | Check: name only, no greeting
• Template variable: company | Source field: organization name | Example value: BrushandChemistry | Check: company name only
• Template variable: booking_url | Source field: scheduling link | Example value: recipient-specific booking link | Check: link is intended for the next step
• Template variable: asset_url | Source field: background media link | Example value: image or video URL | Check: used only if the template has a matching background slot

5. Map fields in campaign setup

Start with a ready template that has a source video and at least one variable. Choose the campaign data source, load the CSV or connect the API payload, then map each template variable to its source column or payload field. Review the row preview before generating.

Campaign generation requires each required variable to be mapped, and each row needs values for the mapped variables. A blank mapping or missing mapped column stops generation before the render request is sent.

6. Test values before a full campaign

Generate sample videos with realistic test values and inspect the result before launching a batch. Check names and company references, pronunciation, timing, subtitles, and any background assets. If something looks wrong, fix the template, variable, or source data and test again.

Keep spoken replacements concise. Long values can be harder to time predictably. When a variable replaces words in a sentence, make sure its value does not repeat words already fixed in the template.

Choose CSV or API based on your workflow

Use CSV for a manual batch, a one-off campaign, or test rows. Use an API when your product, CRM, backend, or form handler needs direct control over generation. In either case, the core task is the same: match each data field to the right template variable and make sure the rows contain the needed values.

This describes data-source options, not a claim that a specific CRM has a native BHuman integration. Map the fields through the CSV or API workflow that fits your setup.