Bidstream Optimizer

Onboarding docs for Bidstream Optimizer.

How Optimizer Works #.. for DSPs #.. for SSPs and Exchanges #.. at run-time # Optimizer subdirectory #.. for SSPs and Exchanges Optimizer trial one-pager Optimizer Strategies Case studies Onboarding Implementation Architecture Optimizing Optimizer Bidstream Data Enrichment Data Enrichment - How enrichment works - run-time workflow - what an enriched bid request looks like - bidder modification - data taxonomy - campaign targeting - reporting - billing and payment Developer API

How Optimizer Works

Bidstream Optimizer analyzes in real-time a stream of bid requests that passes from one ad platform to another (a "bidstream"), provides monitoring to determine the content of the bidstream and a set of controls to enrich or filter each bid request in the stream.

Optimizer is designed as a pre-processor to make generalised decisioning that doesn't interfere with the specific decisioning a customer platform makes.

Optimizer Architecture

Built for scale

Optimizer performs a very specific set of tasks very quickly. The objective is to provide control over the bidstream while adding negligible latency. Optimizer adds no more than 3ms of internal latency to any bidstream regardless of scale.

Distributed Architecture

Optimizer architecture is separated into run-time Optimizer Nodes that are a stateless and can be deployed into any data-center, and Central Services for analysis and model training.

Simple Implementation

Optimizer Nodes are generally co-located inside or near a clients data-center to reduce any connectivity latency between the Optimizer service and the Customer Platform. Read more about Deployment Scenario's.