Two-Stage Playback for Embedded Video Monetization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content sharing platforms face challenges in accurately counting and monetizing views of embedded videos on third-party platforms, especially when autoplay is enabled, as they cannot determine user intent and may block video playback or fail to serve ads effectively.
Innovation Solution
A two-stage playback approach is implemented, where a user's intent to view a video is verified by generating and validating a secure token upon clicking a thumbnail, allowing the content sharing platform to increment view counts and serve ads only when the token is valid, thereby ensuring valid and monetizable views from third-party platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If autoplay feature is enabled for embedded videos on third party platforms, then user viewing experience is improved, but ability to verify user intent and accurately count views deteriorates
Solution Approach 1:
The system performs preliminary actions by generating and storing a token on the client device before video playback occurs. This token contains pre-validated information about user intent and video parameters, allowing the system to later verify whether the autoplay was legitimate without interfering with the user experience during actual playback.
Solution Approach 2:
A token is introduced as an intermediary element between the third party platform and the content sharing platform. This token carries verification information that proves user intent to watch the video, allowing the system to distinguish between legitimate autoplay (where user actually wants to watch) and illegitimate autoplay (where user does not want to watch), thereby solving the view counting accuracy problem while maintaining autoplay functionality.
2Measurement precision
If click-to-start playback is required for embedded videos, then view counting accuracy is improved, but autoplay functionality desired by third party services deteriorates
Solution Approach 1:
The system changes the parameter of video playback initiation from binary (either click or autoplay) to a spectrum that includes both. By introducing tokens with different validity conditions and playback behaviors, the system allows videos to be configured for either click-to-start or autoplay based on the specific context and third party service requirements, while maintaining view counting accuracy through token validation in both cases.
3Productivity
If whitelist approach is used to allow autoplay on third party platforms, then monetization capability is improved, but system security and abuse prevention deteriorate
Solution Approach 1:
Instead of relying on the content sharing platform to maintain and enforce a whitelist of trusted third party services, the system shifts the verification burden to the client device. Each client device independently generates and stores tokens that contain all necessary verification information, allowing the system to securely enable autoplay and monetization on any third party platform without centralizing trust management, thereby preventing abuse while maintaining productivity.
Data Source
AI summary
A method for facilitating monetization of an embedded video configured for automated playback includes detecting, via an iframe embedded in a user interface of a third party platform, an indication of a user intent to view the video configured for automated playback. The video is hosted by a content sharing platform and embedded in the user interface of the third party platform. The method further includes providing, to a client device, video related data pertaining to the automated playback of the video in the user interface of the third party platform, and upon receiving the video-related data, validating the automated playback of the video in the user interface of the third party platform.