Campaigns
Put generated videos on landing pages when the CTA needs context.
BHuman outputs can be used directly in email, SMS, CRM, or ads. Use a landing page when the viewer needs the video, a call to action, tracking, comments, or a branded destination together.
Decision
When to use a landing page
- Use no page when the channel can embed or link the generated asset directly.
- Use a page when the video needs a CTA button, form, calendar, or next-step destination.
- Use a page when you need branded URLs, custom domains, or engagement widgets.
- Use a custom page when your product owns tracking, authentication, or CRM handoff.
Options
Landing page options
- Direct generated asset
- Use the MP4, GIF, thumbnail, or share URL directly.
- BHuman-hosted page
- Use BHuman page settings and optional custom domain configuration.
- Custom landing page
- Use callbacks or polling to place the generated video into your own page with your own CTA.
Flow
Custom page implementation flow
- 01
Trigger generation
Send campaign or API data with enough metadata to identify the visitor or lead. - 02
Store the generation ID
Save the generated video ID returned by BHuman. - 03
Receive callback or poll
Wait for the generated asset fields to become available. - 04
Render the page
Place the video, thumbnail, GIF, or share URL into your page and show the CTA.
CTA
CTA data
CTA values should be treated as variables or metadata in your workflow. Use a clear field such as cta_url, booking_url, or next_step_url instead of a generic URL field.
Keep page generation asynchronous
A lead form can submit immediately, then show a pending state while the video renders. Do not block the entire form experience waiting for the final MP4.