Adobe Experience Manager

How it connects

Rendering is the JavaScript widget. An author places an embed in a component or an experience fragment, and every page or template built from it carries the player without the media entering the AEM repository. The documented set covers 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, so a page can carry a single video or a browsable library view. This is the same path the shipped WordPress and SharePoint integrations run on.

Because one AEM instance usually serves many domains, the approved-domain list is the control that matters. Embedding is restricted to the domains you name, so each published site renders video and anything else is refused, and content URLs are signed and expire rather than remaining valid once shared. Each embed resolves against the viewer's identity, so an item restricted in Nexus renders without its video for a visitor who may not see it, on a public site and behind a login alike.

Adobe also runs a hosted MCP server for AEM as a Cloud Service, and AI Intelligence Hub connects to MCP servers as a client. The connection is configured once with a name, the server URL, the transport and the headers carrying its credential, and the tool list is fetched when it binds rather than coded in. What an agent can read or change in AEM is bounded by what that credential is granted there, which is the thing to scope at setup.

What you can do together

• Place one embed in a component and have every page built from it carry the player, without a video file ever entering the AEM repository.
• Name the domains a video may render on, and refuse the rest, with signed URLs that expire so an address cannot be passed around.
• Keep an unpublished or restricted video governed in Nexus while its page publishes normally, the player simply absent for a viewer without access.
• Let an agent work against AEM content through Adobe's own server, so pages referencing a retired video can be found rather than hunted for.
• Read engagement per surface, so the same video's performance differs by the site it appeared on rather than being one aggregate number.

A scenario

1. AuthoringA developer builds a video component that takes a library reference. Authors use it like any other component.
2. PublishingA product page in three countries carries the same explainer through that component. One item in the library, three pages, no duplicated file.
3. Domain controlThe eleven production domains are on the approved list. A contractor's staging domain is not, so the embed there is refused.
4. An internal videoA compliance briefing is restricted in Nexus to staff. It is referenced from the intranet, which AEM also serves, and renders only for signed-in staff.
5. A retirementLegal withdraws a rate explainer. Access is revoked once in Nexus and every page stops playing it, with no AEM release needed. An editor then asks the assistant which pages still reference it, and fixes those in the next cycle.

What stays where

Products and solutions

• Nexus and AI Intelligence Hub
• Enterprise Video Platform

Next step

See it on your own Adobe Experience Manager 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/adobe-experience-manager