YoungOne

1. Introduction

1.1 Mission / Overview

The YoungOne system is developed based on the OpenRTB protocol from the IAB Tech Lab. The mission of the OpenRTB project is to spur growth in Real-Time Bidding (RTB) marketplaces by providing open industry standards for communication between buyers of advertising and sellers of publisher inventory. There are several aspects to these standards including but not limited to the actual real-time bidding protocol, information taxonomies, offline configuration synchronization, and many more.

This document specifies a standard for the Real-Time Bidding Interface that has grown out of previous OpenRTB collaboration on the “block list project” and the “OpenRTB Mobile” project. These protocol standards aim to simplify the connection between suppliers of publisher inventory (i.e., exchanges, networks working with publishers, and sell-side platforms) and competitive buyers of that inventory (i.e., bidders, demand side platforms, or networks working with advertisers).

The overall goal of OpenRTB is and has been to create a lingua franca for communicating between buyers and sellers. The intent is not to regulate exactly how each business operates. As a project, we aim to make integration between parties easier, so that innovation can happen at a deeper-level at each of the businesses in the ecosystem.

1.2 Version History

Version	Release Date	Update Notes
v1.0.1	2019-12-02	Original Release of OpenRTB Mobile.
v1.0.2	2020-12-02	Combines display, mobile, and video standards into a unified specification.
v1.0.3	2021-05-19	Revisions for IQG compliance, minor enhancements, and corrections.
v1.0.4	2021-05-30	New enhancements for private marketplace direct deals, video, mobile, and regulatory signals.
v1.0.5	2022-08-16	Support for Native ad units and multiple minor enhancements.
v1.0.6	2023-11-02	Support for Audio ad units and the largest set of minor to moderate enhancements in v2.x history.
v1.0.7	2024-05-29	Support for header bidding, billing and loss notifications, Flex Ads, Payment ID, tactic ID, impression metrics, out-stream video, and many more minor enhancements.

1.3 Terminology

The following terms are used throughout this document specifically in the context of the OpenRTB Interface and this specification.

Term	Definition
RTB	Bidding for individual impressions in real-time (i.e., while a consumer is waiting).
Exchange	A service that conducts an auction among bidders per impression.
Bidder	An entity that competes in real-time auctions to acquire impressions.
Seat	An advertising entity (e.g., advertiser, agency) that wishes to obtain impressions and uses bidders to act on their behalf; a customer of a bidder and usually the owner of the advertising budget.
Publisher	An entity that operates one or more sites.
Site	Ad supported content including web and applications unless otherwise specified.
Deal	A pre-arranged agreement between a Publisher and a Seat to purchase impressions under certain terms.

1.4 Resources

2. Integration Process

2.1 Account Application

After confirming the integration initiation, please contact the YoungOne team to apply for an account and provide the following information:

Company name
Company website
Type of device identifiers returned and their corresponding fields
Whether installation/download reporting is supported
QPS (Queries Per Second) level
Whether the pricing is encrypted

Once the information is verified, the YoungOne team will provide the ADX/SSP with the integration environment information. Please keep this information secure:

account id: The unique identifier in the YoungOne system, which includes functions such as creative management, resource uploading, audience setting, and bid request report analysis.
token: The token for account id
ikey: Used for encryption and decryption validation
ekey: Used for encryption and decryption validation
endpoint: Bid request access url