Channels

Overview

The "Channel" object in our ad server is a key component in the supply-side integration, acting as the bridge between traffic sources and ad tags within an optimized waterfall system. This documentation outlines the attributes of the Channel object and their roles in the ad serving process.

Attributes

  1. Name: A unique identifier or name for the channel, used for easy reference and management within the system.

  2. Tags: Represents a collection of ad tags associated with the channel, determining the ads eligible for serving through this channel.

  3. Macros: Predefined variables dynamically replaced with specific values when an ad is served, enhancing targeting, personalization, and tracking capabilities.

  4. Publisher: The entity or individual responsible for the channel, important for identifying traffic sources, managing revenue distribution, and reporting. See more info on Publishers section

  5. Channel Type: Can be either Vast/RTB or Player, defining the ad serving method and the type of ads that can be served.

    • Vast/RTB: Indicates support for video ads through VAST or real-time bidding.

    • Player: Implies integration with a specific media player for ad delivery.

  6. Force Traffic: A setting to control traffic direction through the channel, allowing for manual overrides to meet specific ad delivery objectives.

  7. API Endpoint: An API endpoint that can be given to the publisher for API live reporting. Example endpoint

    https://app.privateadserver.com/api/statsapi?startDate={YYYY-MM-DD}&endDate={YYYY-MM-DD}&token=auto_generated_token

Advanced Settings

  1. Impression Cap: Limits the number of ad impressions.

  2. Request Cap: Maximum ad requests allowed.

  3. Queries Per Second Cap: Rate limit for ad queries.

  4. Revenue Model: Specifies the type of revenue model the advertiser is engaged with. It can be either a 'Fixed Price' model where the payment terms are set in advance or a 'Revenue Share' model where the payment depends on the performance of the ads.

  5. Revenue Split: This field details the percentage or terms of revenue sharing between the advertiser and the platform, applicable in the case of a Revenue Share model.

Third Party Pixels

See Third Party Pixels (TPP) section for more info

Targeting

See Targeting section for more info

Utilization

The Channel object is vital for ad operations teams to manage and optimize ad delivery. It ensures the appropriate ads reach the intended audience through the most effective channels, enhancing the efficiency and effectiveness of the ad serving process.

Last updated