Yield-Op (Third-Party Application)

Prev Next
The following minimum Service Requirements apply to the YIELD-OP service as a THIRD-PARTY APPLICATION.

Client Digital Inventory

Client shall not edit, alter or modify, in whole or in part, the submitted Advertisement(s) in any way, including, but not limited to, resizing the Advertisement, without Service Provider’s prior written approval. Client shall not cover, replace or do any act or omission which would interfere, refrain or prevent, in whole or in part, the delivery of the submitted Advertisement(s) to an End User, without Service Provider’s prior written approval.

Companion Banner Space

Many Advertisements can be delivered with a companion banner that could be included in the received VAST or DAAST XML. If technology permits, Client shall make available the necessary real-estate allowing for the display and delivery of the said companion banner, in compliance with the banner specifications in the Advertising Technical Specification and/or the Triton SDK. The companion banner can be of variable sizes so therefore the real-estate space made available shall support one (1) and/or ALL of the defined spaces as described by the Interactive Advertising Bureau (“IAB”) on the following websites:

IAB Display Guidelines: http://goo.gl/9KIBG (Universal Ad Package [UAP])

IAB Mobile Creative Guidelines: http://goo.gl/s0ce4S (Image)

In the event Client uses the Yield-Op Service, the companion banner must be at least 300 x 250 position for a web player, and 320 x 50 position for a mobile application.

Companion banner can be available in one of the three renderings : IFrame, HTML, or Static Resource. Web players shall support both IFrame and HTML Resources, as it is supported by all on-demand ad sources.

Web players that are unable to support HTML and IFrame Resources shall implement support for static resources, but this will limit the number of banners that can be displayed as only Tap can return static resources.

Any change to the availability and/or size of the said “real estate” shall be notified in writing to Service Provider at least thirty (30) days prior to implementing such changes. For clarification, if a 300 x 250 position available as “real estate” is changed to a 728 x 90 position, this shall constitute a change to the availability and/or size of the said “real estate”.

The requirements for companion banner space shall not apply to a digital player integrated in a motor vehicle (“In-Dash Player”). Notwithstanding the foregoing, Client acknowledges that: (i) the Advertisements could be delivered with a companion banner in an In-Dash Player; and that (ii) for safety reasons, Service Provider does not recommend the display of companion banner in an In-Dash Player. Under no circumstances shall Service Provider be liable for any damages caused by or associated with a companion banner displayed in an In-Dash Player. Client will hold harmless, indemnify, and defend Service Provider, as well as its Representatives, in respect of any third-party damages, liabilities, penalties, claims, actions, suits, proceedings, costs, expenses (including reasonable attorneys’ fees and court costs), arising out of, connected with or resulting from a companion banner displayed in an In-Dash Player.

Format Change

Client shall notify Service Provider prior to any change made to the broadcast format or music genre of any audio Client Content. Notwithstanding the notification provisions of the Agreement, such notification shall be made by way of email to supportdesk@tritondigital.com.

On-Demand API and/or Triton SDK

Should the web player(s) or mobile application(s) used by Client to deliver Client Content be developed and hosted by Client or a third-party (“Client Application”), Client shall install and integrate all Client Applications with the latest version of Service Provider’s On-Demand API and/or Triton SDK, as provided to Client by Service Provider. Service Provider grants Client a free, limited, non-transferable, non-sublicensable, non-exclusive and worldwide right to use and reproduce Triton SDK for the sole purpose of: (i) connecting Client Applications with Service Provider’s Network during or in relation with the Agreement; and (ii) deliver the Advertisements provided by Service Provider through Client Applications during or in relation with the Agreement.

Client is solely responsible to ensure that Client Application complies with and implement at all times the specifications and instructions provided to Client by Service Provider, including without limitation the Triton SDK, the Triton Digital Advertising Technical Specification, or the Triton Digital On-Demand Specification. Service Provider does not guarantee the Service and is not responsible for any damages arising out of, connected with or resulting from a failure to comply with such specifications and instructions. For clarity, and without limiting the generality of the foregoing, failure to properly implement the specifications and instructions provided to Client may affect the following functionalities of the Service and under no circumstances shall Service Provider be responsible for any damages (including, without limitation, loss of advertising revenue) arising out of, connected with or resulting from a failure to comply with such specifications and instructions: (i) ad request service; (ii) creative format compatibility; (iii) ad delivery; or (iv) ad impression recording.

“Client Ad Server” means the advertising server used by Client to call Service Provider’s ad network to display Advertisements on Client Digital Inventory, whether owned by Client or a Third-Party Provider.

“On-Demand API” means the latest version of the application programming interface developed by Service Provider in connection with Service Provider’s on-demand ad services, which enables the communication between Client Ad Server and Service Provider’s ad network. The On-Demand API includes, without limitation, all related documentation and specifications.

“Triton SDK” means the latest version of Service Provider’s technical documentation and software code designed to share Listener ID collected from the End User to Service Provider.

Tracking Technologies

When applicable, Client shall implement the necessary Listener ID Tracking Technologies as defined in, and in compliance with, the Triton Digital On-Demand Specification, Triton Digital Advertising Technical Specification, and/or Triton SDK, in the following order of preference: device advertising identification; cookie-based advertising identification; and (when either of the first two preferences are not available) app-generated identification. The Listener ID can be from one or multiple sources/providers and Client agrees to implement any such Listener IDs. Client shall make the Listener IDs available to Service Provider in compliance with Triton Digital Advertising Technicial Specification and/or Triton SDK.

Geographical Location

For targeting purposes, Client (i) shall provide either the IP Address or the Truncated IP Address of the End User, at Client’s sole discretion; and (ii) shall make best efforts to provide the geographical location (latitude and longitude) of the End Users.

“IP Address” means a unique string of numbers separated by periods that identifies each computer using the Internet Protocol to communicate over a network.

“Truncated IP Address” means an IP Address where the last 8 bits are set to 0

Server-to-Server Integrations

Client shall be responsible for collecting and passing all the End User information that would affect advertisement selection from the “on-demand ad service” when used in a server environment where the service does not directly interact with End Users. The collected data must include, when available: IP Address, HTTP referrer and user agent string.