One Video Behind Every Personalized Variant
Bloomreach combines content management and personalization for commerce-led sites, where the same page is assembled differently per visitor. Personalization is the reason a video has to be a reference: a product story shown to six segments is one asset, not six uploads. The connection is the embed code and the JavaScript widget from Nexus, which ship and work in any front end that renders HTML, so no Bloomreach-specific module is involved. Bloomreach keeps the page and the personalization, and the media stays in the library.
How it connects
Video is referenced from Bloomreach content, and the JavaScript widget renders the player where that reference appears. The media is never copied into Bloomreach. 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 personalized block can carry a single video or a filtered library view.
Embedding is restricted to the domains you name, either as an allowlist or as everything except a blocklist, and the check runs on each request, so an embed code lifted to a host outside that list does not play. Content URLs are signed and expire after a set number of minutes, while the player refreshes its token so a long video plays through. On a commerce site that matters, because campaign assets circulate. Embed analytics report which sites carry an item, with the view count and the last playback from each.
The personalization decision stays in Bloomreach. It chooses which library item each segment sees, so the reference is what varies and the library stays a passive source. Access still resolves against the viewer, so an item a viewer may not open does not render for them. The direction is outward: the embed places library content on Bloomreach pages, and Bloomreach's own content stays in Bloomreach.
What you can do together
- Reference one library item across every personalized variant, so a video is produced once rather than per segment.
- See which sites carry an item, with view counts and the last playback from each, beside the item's own analytics in the library.
- Name the domains allowed to render, with signed URLs that expire, so campaign material cannot be shared onward indefinitely.
- Render a filtered library view inside a personalized block rather than only a single player.
- Withdraw an item once in the library and have every personalized surface stop rendering it for viewers who may no longer open it.
A scenario
- SetupAn administrator adds the storefront's domains to the portal's embed allowlist.
- The templateA component renders the widget from a reference field on the content item.
- PersonalizationBloomreach selects which reference each segment sees; one library item serves several.
- Reading itThe item's embed analytics list the storefront among the sites carrying it, with views and the last playback from each.
- A campaign endsThe item's access is changed once in the library, and it stops rendering for viewers who may no longer open it.
- A lifted embedA reseller copies the embed code onto its own site, which is not on the allowlist, and the player does not play there.
What stays where
Bloomreach remains the content and personalization platform
Content, segments and the personalization decision stay there.
The media stays in the library
Files, access rules, retention and analytics live there, and a page renders a view rather than a copy.
The widget is the whole connection
It works in any template that renders HTML, which is why no Bloomreach-specific module is needed.
Processing runs where you deploy the platform
That is shared or dedicated SaaS, your own cloud subscription, or on premises. Visitors reach the player over the network, so a public site needs a deployment reachable publicly.
Products and solutions
Next step
See it on your own Bloomreach 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/bloomreach