SitecoreContent Management and Web
Personalise the Page, Not the File
No Sitecore package exists for this, and none is needed. The connection is an embed code and a JavaScript widget placed inside a component, the same path the shipped WordPress and SharePoint integrations run on, and it works anywhere a page renders HTML. Sitecore composes large marketing sites where the page depends on who is reading it, and video is usually the heaviest thing on that page and the least governed. Nexus, the portal behind the Enterprise Video Platform (EnterpriseTube) solution, holds one copy of the media with its access rules, retention and analytics, while Sitecore goes on deciding what each visitor sees.
What you can do together
- Personalise the page rather than the file: Sitecore chooses which component a visitor sees, and every variant streams the same copy from Nexus, so a swapped video is a library change rather than a republish.
- Put a searchable library inside a section, so a resource hub grows without a template per recording.
- Ask the visitor something, with quiz and survey player widgets beneath the player in the same component.
- Attribute the views, since embed analytics report which sites embedded an item, the view count for each and the last playback from it.
How it connects
Personalisation stays a Sitecore concern. The content tree, the visitor profiles and the rules that pick a component are untouched, because the only thing that changes is what goes inside a component: a widget or an embed code, placed by a content author like any other markup.
The documented widgets cover video, audio, image, document, collection and playlist players, media library gallery and detail views, insights, transcription, maps, carousel and collage, quiz and survey players, and a mashup filter. A section can therefore carry a searchable library rather than a new template for each recording.
Configuration lives in Nexus. Embedding is restricted to approved domains, so each site you name is listed and every other host refused, and content URLs are signed and expire. Each embed resolves against the viewer's identity, so an item restricted in Nexus stays restricted however the page around it was assembled.
What does not exist is the other direction. There is no ingestion connector for Sitecore, so content held in Sitecore is not pulled into the library. Ingestion is a per-source connector and the built ones are SharePoint, OneDrive, Kaltura, Azure Blob, AWS S3 and Teams. Bringing a Sitecore media estate under governance is work scoped per engagement rather than a setting.
SitecoreContent Management and Web
A scenario
- SetupAn administrator adds the customer site and the broker portal to the approved domain list in Nexus, and uploads product explainers as public plus an underwriting briefing limited to brokers.
- LaunchA Sitecore author places the player widget in the product page component. A visitor reading about one policy sees the explainer for that policy, personalised by Sitecore, streamed by Nexus, with no file in the content tree.
- The same weekA gallery and a search widget go on the broker portal's resources page, and brokers browse and search every briefing there.
- An outside visitorSomeone reaching that page without broker permissions sees the page and not the video, because the embed resolves against the viewer.
- Quarter endThe marketing lead reads embed analytics and finds the broker portal, not the customer site, drew most of the views.
What stays where
Sitecore keeps the experience
Content tree, components, visitor profiles and personalisation rules stay in Sitecore, and no package is installed for a widget to render.
The media stays in the library
One copy, with its access rules, retention and analytics, rendered as a view rather than duplicated per variant.
Ingestion from Sitecore does not exist
Surfacing content on the site ships; pulling Sitecore's own media into the library is a connector that has not been built.
Processing runs where you deploy the platform
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 Sitecore instance.
We will show the connection made, the data moving and the output, then size it for your deployment.
Contact VIDIZMO
sales@vidizmo.ai
+1 571-969-2180
vidizmo.ai