Optimizely

How it connects

Video becomes a reference on the content item, and the JavaScript widget placed by the template renders the player wherever that reference is filled. The media never enters Optimizely. The documented widget set covers video, audio, image, document, collection and playlist players, library gallery and detail views, insights, transcription, maps, carousel and collage, quiz and survey players and a mashup filter, so a page can carry one video or a browsable library view from the same field.

Because variants multiply the surfaces a video appears on, the controls matter more here than on a single site. Embedding is restricted to the domains you name, as an allowlist or as everything except a blocklist, so each published property renders and anything else is refused. Content URLs are signed and expire after a set number of minutes rather than remaining valid once shared, and the player refreshes its token during playback, so a long video plays through while each URL stays short-lived. Embed analytics report which sites carry an item, with the view count and the last playback from each, and where two variants reference different library items, each item's figures belong to one variant rather than being pooled.

Optimizely stays the content and experimentation platform. Content items, variants and the experiment results are unchanged, and the video reference is one more field. The direction is outward: the embed places library content on Optimizely pages, and Optimizely's own content stays in Optimizely.

What you can do together

• Reference library items from many page variants, so experimentation does not multiply copies of the media.
• Give each variant its own library item where video performance is being compared, so each item's figures describe one variant.
• Name the domains allowed to render, with signed URLs that expire, so pre-release material cannot be passed around.
• Restrict an item in the library and have the page publish normally with the player simply absent for a viewer without access.

A scenario

1. SetupAn administrator adds the marketing site's domains to the portal's embed allowlist.
2. The templateA template component renders the widget from the reference field.
3. The experimentTwo variants reference different library items, with no media duplicated into the CMS.
4. Reading itEach variant's views are read from its own item's analytics rather than pooled with the other's.
5. A restricted itemAn unreleased feature video is limited in the library, and for an outside visitor the page renders without the player.
6. A copied linkA URL lifted from browser tools stops working once it expires, so the video does not travel past the test.

What stays where

Products and solutions

• Nexus
• Enterprise Video Platform

Next step

See it on your own Optimizely instance. We will show the connection made, the data moving and the output, then size it for your deployment.

Request a demonstration →  or write to sales@vidizmo.ai

sales@vidizmo.ai  ·  vidizmo.ai/integrations/catalog/optimizely