Working in NEXUS

Planning your work in NEXUS

Use the following questions when planning editorial or production work.

1. Which channel are you planning for?

Start by identifying the target channel.

2. What kind of content are you promoting?

Identify whether the content is editorial, OTT, or mixed.

3. Is the content free or gated?

Plan whether users can access the content freely or whether they need to register, sign in, or subscribe.

Free and gated content can appear together on the front-end. Gated content can be recognizable to users through visual indicators such as a lock icon or badge.

However, producers do not see complete license and subscription information in FORGE when placing OTT-specific modules or mixed editorial modules. If you need to confirm whether OTT content is free or gated, check the configuration in VESPER.

4. Who controls the content and who controls the placement?

Separate content ownership from front-end placement.

5. What user journey are you supporting?

NEXUS is designed to support unified digital and OTT journeys. When planning a page, campaign, or content collection, define the user journey before choosing modules or selections.

For example, you may be planning a journey where users:

1. Read a free editorial story.

2. See a promoted premium video in a carousel.

3. Select the gated video.

4. Register or sign in.

5. Choose a subscription.

6. Watch a video.

7. Continue browsing related editorial and OTT content.

This planning step helps editors and producers align content curation, page composition, and monetization goals.

OTT taxonomy in FORGE and VESPER

OTT content synchronized from VESPER to FORGE keeps the same taxonomy.

For example, if a VESPER VOD has the tags free and promotional, the synchronized VOD entity in FORGE receives the same tags.

Tag synchronization rules

Tag synchronization from VESPER to FORGE stops if editors change synchronized tags in FORGE.

This happens when editors:

• Delete tags transferred from VESPER.

• Add new tags to the synchronized VESPER entity in FORGE.

Important

Do not manually change VESPER-originated tags in FORGE unless you intentionally want to stop tag synchronization for that entity.

Typed tags (not available in FORGE)

VESPER supports typed tags. Typed tags are localizable key-value pairs that can add structured meaning to OTT content.

FORGE does not support typed tags. When VESPER content is synchronized to FORGE, only standard tags are synchronized.

Promotion and personalization

What drives promotion in FORGE

In FORGE, promotion is driven by editorial curation and page composition.

Editors can use editorial selections to group content around campaigns, events, topics, or user journeys. Producers can then place those selections, rows, carousels, or OTT-specific modules on web and mobile pages.

What drives personalization in VESPER

Personalization is available in VESPER.

Editors can define VESPER buckets that deliver personalized OTT content based on user profiles. Those buckets can then be synchronized to FORGE and promoted on web or mobile.

If a page or campaign depends on personalized OTT content, confirm the personalization setup in VESPER before planning the FORGE presentation.

Live coverage

Editors can promote live events by publishing VESPER Live Event Video entities.

The live coverage workflow is controlled in VESPER. FORGE can promote synchronized live event video entities, but the video workflow itself remains in VESPER.

When planning live coverage, check:

• Whether the live event video exists in VESPER.

• Whether the event metadata is complete.

• Whether the event is free or gated.

• Whether the license and subscription configuration is correct.

• Whether the synchronized entity is available in FORGE.

• Where producers need to place the live event on web or mobile.

• Whether webTV coverage must be planned separately in VESPER.

Publishing across touchpoints

What “the same experience across devices” means

In NEXUS, the same experience across devices means that users can follow a consistent content and subscription journey across supported channels, while each channel uses a layout and interaction model suitable for that device.

For example, producers can create web and mobile site structures that promote the same campaign, but adapt the presentation to each device.

Can editors publish once to multiple touchpoints?

Publishing across touchpoints depends on how producers organize the site structure in FORGE.

Producers can define site structures that support reuse across web and mobile. This can reduce duplication and help teams publish content across multiple touchpoints more efficiently.

Editors should confirm with producers how the relevant site structures are configured before assuming that a content update will appear across all touchpoints.

Are there device-specific editorial controls?

Yes, producers can organize site structures to promote content differently by device.

For example, producers can configure a page so that specific content appears on mobile but not on web, or on web but not on mobile.

Editors should plan device-specific needs before content is placed, especially for campaigns, live coverage, or premium video promotion.

Are there device-specific licensing controls?

Yes, producers can define licenses based on devices.

For example, producers can decide that some video content is "subscription only" on TV but "register to watch" on mobile or web.

Preview and user segmentation

Editors and producers do not have user segmentation visibility in FORGE.

This means they cannot preview the front-end experience by user type, subscription tier, or entitlement state directly in FORGE.

If you need to validate what different users see, coordinate with the teams responsible for VESPER configuration, entitlement setup, or front-end validation.

Measurement and success

How editorial efficiency can be measured

The main NEXUS goal is to monetize digital and OTT content by giving users a unified channel for both editorial and premium video content.

Editorial efficiency should therefore be measured by how effectively editorial and production work supports that goal.

Useful indicators include:

• Reduced fragmentation between editorial and OTT journeys.

• Fewer duplicated content operations across channels.

• More reuse of editorial selections, synchronized VESPER entities, and page structures.

• Faster setup of mixed editorial and OTT promotions.

• Clearer handoff between editors, producers, and OTT teams.

• Increased visibility of premium content inside editorial journeys.

• Higher conversion from editorial or campaign touchpoints to registration, sign-in, subscription, or purchase.

• Higher engagement with mixed editorial and OTT modules.

• Better performance of campaigns that promote gated or premium content.

In practice, teams should connect editorial efficiency metrics to monetization outcomes. A page or campaign is efficient when it helps users discover, access, and purchase relevant premium content with less operational effort from the editorial and production teams.

Analytics editors can use

Editors can use two main analytics sources to understand performance.

Use Google Analytics 4 to understand how users interact with web and mobile front-end experiences. Use VESPER Analytics and Insights to understand OTT performance.

Governance and operations

Who owns the combined editorial and OTT experience?

Ownership is shared across editorial, production, and OTT teams.

For web and mobile:

• Editors manage editorial curation and mixed content planning in FORGE.

• Producers manage front-end placement in FORGE Page Builder.

• OTT editors or operators manage OTT content, licensing, subscriptions, and personalization in VESPER.

For webTV:

• Editors and OTT teams manage the experience in VESPER.

A successful NEXUS workflow depends on clear coordination between these roles. Editors and producers should agree early on which content is needed, where it should appear, whether it is free or gated, and which team owns the required configuration.

What apps do editors and producers need to access?

Access depends on the channel and task.

Editorial teams working on web and mobile usually need FORGE access. If they also need to inspect OTT details, manage playlist composition, check licenses, or manage subscription setup, they need VESPER access as well.

Editorial teams working on webTV need VESPER access.

What are the OTT failure and fallback scenarios?

Open support tickets to the VESPER team in case of OTT troubles.

FAQs