Beta Process

1. Set up Authentication.
2. An Exchange ID is assigned, and pushing deals to designated test partners is allowed.
3. Develop and test your integration.
4. The beta progresses on a per-DV360 partner basis. Exchanges identify an initial set of partners (fewer than 50) to enable for beta testing.
   1. All new deals for enabled partners must be pushed using the API.
   2. All updates for newly created deals are expected to be pushed using the API.
   3. Don't attempt to update legacy deals. Legacy manually created deals will continue to serve with no issues.
5. Monitor performance and enable additional partners.
6. General Availability (GA): All new deals must be pushed using the API.

Best practices

1. Push deals as soon as they are created by the exchange. This prevents delays for advertisers when viewing and accepting deals.
2. Coordinate with the DV360 team, advertisers, and publishers to monitor beta performance.
3. Be mindful of API usage. Contact the DV360 engineering team if you expect high traffic (rates exceeding 5 QPS should be discussed prior to integration).
4. Avoid sudden bursts of requests; distribute calls evenly where possible.