Overview
This article describes the enhanced monetization model supporting TVOD (Transactional Video on Demand) and SVOD( Subscription Video on Demand) for events, games, VODs, series, and playlists across Web, Mobile (iOS/Android), Tablet, and Connected TV platforms. Administrators can configure plans in the CMS; end-users interact with dynamic tags, badges, and call-to-action (CTA) flows.
1. CMS Admin Configuration
1.1. Supported Platforms
This feature is applicable & configurable for following platforms and devices -
iOS Mobile & Tablet App
Android Mobile & Tablet App
Desktop Web and Mobile Web Browser
CTV Platforms
Apple TV
Fire TV
Roku
Android TV
Smart TV - Samsung / LG / Vizio
Xfinity
XBOX
1.2. Content Tagging with Monetization Models
For any content type (event, VOD, series, playlist), navigate to:
CMS > Content > Select Content type (Video, Live Series etc.) > Monetisation ModelSelect TVOD and/or SVOD models to attach to the content. Multiple plans (e.g., SVOD, TVOD Buy, TVOD Rent, PPV, TVE) can be mapped simultaneously.
Based on the monetization plans attached in the CMS, tags/badges are automatically displayed below content or event thumbnails for users.
The possible tags/badges and their triggers are:Buy: When only a TVOD Buy plan is attached.
Rent: When only a TVOD Rent plan is attached.
Subscribe: When only an SVOD plan is attached.
Subscribe or Buy: When SVOD and TVOD Buy plans are attached.
Subscribe or Rent: When SVOD and TVOD Rent plans are attached.
Subscribe or Purchase: When SVOD and both TVOD Buy & Rent plans are attached.
Tags and Badges are API-driven and their labels cannot be changed from the CMS
Tags/badges are always shown dynamically based on the attached plans in the CMS.
The display of tags and badges is controlled by country rules set manually in the CMS. If content is marked as free for a particular country, no badge will be displayed to users from that country. If the content requires a TVOD or SVOD plan in that country, the appropriate badge will be shown to guest users and users who have not yet purchased or subscribed.
1.3. CTA Button Configuration
Go to App CMS > Template Builder > Modular Page (Home/ Game detail) > Monetisation CTA’s.
For each content detail page:
Add and sequence available plans as primary and secondary CTA options.
If more than two plans are associated with the content, the primary and secondary CTAs will be shown prominently, and a third CTA labeled “More options” will be provided. Clicking this opens a popup listing the additional available plans.
The CTA label shows the plan, title and price. The sub-label displays a short description.
Button styling (font, color, size) is customized for each event/card and may differ by platform.
1.4. CTA Button Display
CTA Button Labels and Styling:
All CTA (Call to Action) button labels, states, background colors, and text colors are fully configurable from the CMS. Font styling such as typeface, size, and weight can also be managed within the CMS to ensure consistent branding and design.<global level add ss>Display Logic:
For the Primary and Secondary CTAs, the user can choose from:
Free
SVOD
Buy
Rent
TVE
Not applicable
Multiple plans can be configured under each option. The first mapped plan in each category will automatically be applied to the selected CTA.
For example, if the user selects SVOD as the Primary CTA and Buy as the Secondary CTA, the first SVOD plan (attached to the content) will appear as the Primary CTA and the first Buy plan will appear as the Secondary CTA. Any remaining plans will appear under “Other Options.
Multiple Monetization Plans:
When more than two monetization plans are configured for a piece of content, the primary and secondary CTA buttons will be displayed prominently on the detail page, based on CMS configuration. A third CTA button labeled “More options” will also appear; clicking this opens a popup listing all additional monetization plans mapped to the content, allowing users to explore and select from all available offers.
1.5. Managing and Modifying Plans
Monetization models and mapped plans can be updated per content, per user country.
Changes to tags/badges or plans are reflected instantly across Watchlist, Search, My Library, and detail pages for all platforms.
2. End-User Experience
2.1. Home Page & Content Browsing
Users (guest or registered) see dynamic badges under content/event thumbnails in carousels and trays:
Badge text reflects the attached monetization model (Buy, Rent, Subscribe, etc.).
No badges are shown if the user has already purchased/subscribed.
Clicking “Go to details” takes users to the appropriate detail page (event, VOD, series, playlist).
Country rules affect badge display; admins manage this manually.
2.2. Detail Page & Monetization Flow
On event, VOD, series, or playlist detail pages, users see available monetization CTA buttons per the plan configuration:
Guest users clicking a CTA are redirected to sign up/sign in, then to the purchase flow.
Registered users clicking a CTA land on the payment pages directly.
With more than two monetization plans, primary and secondary CTAs are shown, along with "More purchase options" in a popup for additional plans.
Platform-Specific Flows:
iOS / TV OS:
When users interact with a TVOD CTA (Buy or Rent) on iOS, they are redirected to a “View Plans” screen filtered to the Buy or Rent category, where detailed purchase options are presented.
When users tap an SVOD CTA on iOS, they are taken to the “View Plans” screen filtered to the Subscription category, allowing them to choose applicable subscription plans.
If multiple monetization plans are available beyond the primary and secondary CTAs, tapping the “More purchase options” button opens a popup listing all remaining plans.
Selecting a plan from this popup leads the user to a detailed plan view, from which they proceed to the native payment page to complete the purchase.
Android, Web, TV:
When users on Android devices, web browsers, or connected TV platforms interact with monetization CTAs (such as Subscribe, Buy, or Rent), the following occurs:
Onboarding: If the user is not signed in, they are first prompted to sign in or register before proceeding with any purchase.
Payment Flow:Once the user is signed in, clicking a monetization CTA initiates the payment process tailored to the platform. This may involve entering payment details, selecting plans, and confirming purchases.
UI Variations: Although the core monetization functionality (entitlement checking, purchase validation, badge updates) is consistent across Android, Web, and TV platforms, the user interface elements—such as button layout, screen transitions, and dialog appearance—may differ to adhere to platform design standards and optimize usability.
2.3. My Library & Post-Purchase
After successful purchase/rental/subscription, the user’s My Library screen updates instantly to show new content by category (Buy/Rent).
Purchased/rented content can be played back from My Library; if there is no content, users see a “No content available” message.
Billing & Payment screens show detailed transaction history, filterable by Buy, Rent, Subscription.
2.4. Badge & CTA Updates
All badges and CTA states are updated instantly across Watchlist, Search, and Library once a user's entitlement changes.
Badge and CTA styling may differ by device or platform as dictated by CMS branding, but feature parity is maintained.