Real-time Ad Tracking Proxy for Streaming Manifests
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Multimedia delivery systems lack real-time tracking of ad playback events, leading to a lack of awareness for operators about the success rate of ad insertion and limited control over the tracking process.
Innovation Solution
A method involving a manifest manipulator that generates a manifest with callback URLs for tracking playback events, which are received by a tracking proxy that forwards tracking information to the asset decision system, enabling more comprehensive ad tracking and data collection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If tracking responses are forwarded directly to the ADS bypassing the MDC, then the tracking process is simplified, but the multimedia delivery system operators lose awareness of ad insertion success rate and control over the tracking process
Solution Approach 1:
The patent introduces the MDC as an intermediary component between the client device and the ADS. The MDC receives tracking responses from the client device and forwards them to the ADS, while also maintaining visibility of the tracking process. This intermediary role allows operators to monitor ad insertion success rates without complicating the direct tracking response flow between client and ADS.
2Adaptability or versatility
If external third party ADS are used to select ads, then ad selection capability is enhanced, but the multimedia delivery system operators have limited control over the tracking process and data
Solution Approach 1:
The patent implements a feedback mechanism where the MDC receives tracking responses from client devices and forwards them to the ADS. This feedback loop allows operators to monitor ad insertion success rates and maintain control over the tracking process while still utilizing external third-party ADS for ad selection. The MDC acts as a control point that preserves operator oversight.
3Measurement precision
If callback URLs are added to the manifest for tracking playback events, then real-time tracking capability is improved, but the manifest structure and processing complexity increases
Solution Approach 1:
The patent incorporates callback URLs directly into the manifest file before it is sent to the client device. By pre-configuring the tracking mechanism in the manifest, the system establishes real-time tracking capability without requiring complex runtime processing. The client device simply needs to execute the callback URLs when playback events occur, simplifying the overall implementation despite the added manifest elements.
Data Source
AI summary
A method provides for tracking client playback events when playing an asset specified in a manifest for streaming adaptive bit rate (ABR) content. The method includes generating, with a manifest manipulator, a manifest that includes an asset URL inserted at a marker denoting a placement opportunity in a content manifest requested by a client. The manifest also includes callback URLs for tracking playback events to be returned by the client. The manifest manipulator sends the manifest to the client. At least one of the callback URLs is received by a tracking proxy associated with the manifest manipulator, indicating that the event has been performed by the client. In response, a tracking URL is obtained by the tracking proxy. The tracking URL is sent to at least one asset decision system participating in an asset decision process that resulted in providing the asset URL to the manifest manipulator.