On-Demand Specification

Prev Next

Introduction

This document describes the Triton Digital On-Demand Ad Service and its usage. The techniques for ad delivery and listener tracking described herein are capable of providing added value to your audio publishing by enabling features such as advertising frequency caps and detailed listener measurement. Please consult your company's legal team with regard to any user agreements, privacy policies, or other matters that might conflict with the capabilities of the Triton Digital On-Demand Ad Service.

The Triton Digital On-Demand Ad Service allows an application to request ads targeted to a given listener. In contrast with in-stream ads, these requests do not require a streaming connection, and they can request ads in a stand-alone fashion.

The On-Demand Ad Service can serve audio pre-roll, mid-roll, and post-roll ads from Triton Digital's TAP and TAP Programmatic (formerly Yield-Op). This document reflects the generic interface but includes aspects specific to TAP and TAP Programmatic where applicable.

The On-Demand API supports both client-to-server integrations (an application running directly on a listener's device, such as a smartphone, computer or other) and Custom Streaming Environments (streaming server, media server or other).

For advertising technical specifications and requirements, see the Advertising Technical Specification.

Depending on which Triton Digital services you use, you might also find these documents useful:

  • Advertising Technical Specification. This document describes how to properly support the advertising functions of the Triton Digital on-demand, live streaming, and podcasting services.

  • Streaming Specification. This document describes the Triton Digital Streaming Service and its usage, including techniques for streaming, listener tracking, and ad delivery.

  • Guidelines for Measurement. This document describes the Triton Digital measurement services. It includes player and app guidelines, and information about the methodologies used by Triton Digital.

During your initial activation, and periodically afterwards (depending on revisions to the service and this specification), Triton Digital will validate your player-to-server or server-to-server implementation using the Player Activation Form (player-activation-validation-<version-number><date>.xlsx). You may or may not be asked to participate in this validation process; there is nothing for you to do unless you are given further instructions by a Triton Digital Solutions Specialist or Client Success Manager.

Flow Diagram: Direct Client Integration

FlowDiag-player-to-server

Flow Diagram: Server-to-Server Integration

FlowDiag-OD-server-to-server

For more information, see Custom Streaming Environments and Global and Regional CMOD Endpoints. Also, be aware that some impression tracking companies (such as DCM) require SSAI vendors to be authorized in order to accept impression tags fired from those SSAI servers.