Personalized video is a paid service that allows you to better connect with prospects, customers, and supporters by weaving unique details about each person into a video.
In coordination with Vidyard's Professional Services Team, you'll create a video that can be used with our personalized video API. When finished, you'll have gained a unique, one-of-a-kind asset that you can use to deliver an engaging, human, and more authentic message to your audience(s).
Want to see some personalized videos? Need some inspiration? See our Video Inspiration Hub to learn how others have used personalized video with Vidyard.
How does personalized video work?
The technology of personalized video revolves around a unqiue set of characters called the
vycustom_id is what Vidyard uses to associate a set of personalized details (information about each of your recipients) with the video that you've produced.
When appended to a video embed code or sharing page link, the
vycustom_id pulls a personalized version of the video for the viewer to experience.
URL without vycustom_id
URL with vycustom_id
There are two ways in which the
vycustom_id can be delivered:
- pre-rendered (batch)
- on-demand (API).
How you intend to use your personalized video determines how the
vycustom_id(s) are produced.
|Use case||Type of render|
|Inbound marketing: use PV on a landing page or as a follow-up to website visits and downloads||on-demand (API)|
|Prospecting and selling: use PV to send tailored, one-off video messages to prospects and key contacts (via the GoVideo app)||on-demand (API)|
|Outbound marketing: use PV to send an individualized message to contacts, prospects or supporters as part of an email or nurture campaign||pre-rendered (batch)|
If you require additional assistance or have questions about how you might use personalized video, contact the Vidyard Professional Services Team. We're always here to help you along the way with technical knowledge, best practices, and hands-on guidance.
Looking to develop applications around our personalization engine? See our API documentation for further information.