Open Bidder is configured using the online user interface which
is broken down into the sections below.

Step 1: Create Project

Click Create a New Project in the Open Bidder
home screen or click on Select a Project and then click
Create New Project. The user interface will guide you through
the steps necessary to create a new project.

Under Application type, select Web application, enter a Name and set the Restrictions
(optional), then click Create.

The OAuth client ID and secret appear.

Step 2: Authorize Open Bidder

The next step is to authorize your project. Your Open Bidder
project will need OAuth 2.0 credentials in order to:

Retrieve reports from DoubleClick Ad Exchange.

Start, stop, and query bidders on Google Compute Engine.

To authorize your project, click Authorize. Once
authorization has been completed, you can revoke the authorization by
clicking the Revoke Tokens button.

You must be sure that the account you log in with when
you authorize Open Bidder has been granted access to an Ad Exchange account.
You will not be able to authorize Open Bidder if you are signed in with an
account that isn't associated with an Ad Exchange account.

Step 3: Configure DoubleClick integration

To configure bidding for your project, you will need the following
information:

Encryption Key and Decryption Key

These keys are necessary to decode winning prices from impressions,
as well as hyperlocal and device ID information from bid requests.

Buyer Account

This is the DoubleClick Ad Exchange Buyer account for registering
running bidders to configure quota. Please ask your Ad Exchange Technical
Manager or see the Ad Exchange Buyer REST
API for more details.

Cookie Match URL

The cookie matching URL prefix. This value is tied to the buyer
account selected above.

Once you have filled in the information, click Update Project
and proceed to Step 4.

Step 4: Configuring bidders

VM Parameters

JDK VM parameters passed to the Open Bidder server.
Typically used for JVM tuning, such as garbage collection parameters.

Main Parameters

Custom main parameters that are provided to your bidder server at
start-up. These can be used to set properties of your bidder server or
interceptors.

Additional Bidder OAuth 2.0 Scopes

A list of additional OAuth 2.0 scopes that will be used by your
bidders to access other Google services.

This is a list of the fully-qualified path names of your bid
interceptors. Enter each value on a separate line. These interceptors
will be loaded by your bidder server and will respond to incoming
BidRequests. To receive valid responses from your bidder
server, you must set at least one interceptor for each type of
request.

Impression Interceptors

A list of the fully-qualified path names of the impression tracking
interceptors. Enter each value on a separate line. These interceptors
will be loaded by your bidder server and will respond to incoming
ImpressionRequests.

Click Interceptors

A list of the fully-qualified path names of the click tracking
interceptors. Enter each value on a separate line. These interceptors
will be loaded by your bidder server and will respond to incoming
ClickRequests.

Pixel Matching Interceptors

A list of fully-qualified path names of the pixel-matching
interceptors. Enter each value on a separate line. These interceptors
will be loaded by your bidder server and will respond to incoming
MatchRequests.

When you have finished filling in these values, click
Update Project.

Note: When providing any kind of
interceptor in this step, you need to have included it in the bidder
server project that was uploaded to Google Cloud Storage.
See
Creating Your Bidder Server for more information.

Network and Firewalls

Open Bidder leverages the Google Compute Engine
network and firewall features for its basic security. The bidder's
default configuration binds the following ports: 80 (http), 443 (https),
and 9090 (http for status requests). You must create firewall rules to
open these ports, see the
Google Compute Engine documentation.

Bidder Management

Click on Bidding to add bidders.
You will be presented with a list of Google Compute Engine zones.
Start bidders by clicking on the zone for which you want to make allocations.
When you click on the link, you will see information about the bidders
for the zone, as well as information about the zone itself.

There should be an A record for each bidder's external IP address
(or their
load balancer), bound to the zone's host name. This host name
will be the one registered with the DoubleClick Ad Exchange and will be
used in the impression and click callbacks handled by the Open Bidder.
Once the zone is registered, updating zone host is not allowed.
Please unregister the zone before the update.

Registration

You need to register your bidding zone with the DoubleClick Ad
Exchange to receive bid requests. Please set your Ad Exchange Buyer
Account Id in the Edit Project page before you proceed.

Bid Protocol

You need to choose which RTB protocol will be used; Ad Exchange
supports both its native protocol and multiple versions of OpenRTB.

Maximum QPS

You need to set the maximum number of queries per second that Ad
Exchange should send to each bidder URL for this account.

Register

Once you have set the Maximum QPS, you can click the Register
button to register your bidding zone with DoubleClick Ad Exchange.

Bidders

Shows a summary of existing bidders for the selected zone including
the name, internal IP, external IP, machine type, and status of the bidder.
Click on the name of the bidder to view more details.

To create a bidder:

Select an instance type.

Click Add Bidder. If you are deploying more complex
interceptors, then you will want to select an instance type that has more
CPUs allocated for it. The Status of the bidder will
change to Provisioning, Staging, and finally,
Running.

Caution: Bidder configuration is
static; once a bidder is created, changes to the project or network
configuration will not affect existing bidders. If necessary, delete the
old bidders and create new ones to pick up the new configuration.

Managing users

Once you have selected or created a project, you can click
Manage Users on the project menu to define who will have access
to your project.

Next steps

You have just installed Open Bidder, configured both an
interceptor and bidder server project, packaged and uploaded your bidder
server, and deployed it to Google Compute Engine. From here on, you should
now be able to create your own projects, although if you would like to
learn more, we have additional topics covered in our guides.