...
```
##### Does not meet technical requirements
In this example, creative **HTML code returned by Google** is obfuscated
in the bid response provided by an exchange and *does not appear verbatim in
the bid response*. Google-provided HTML code may get rendered by an
exchange-provided wrapper in the browser.
```
```
#### VAST video creatives
To be eligible for the discrepancy resolution, an exchange is required to
use one of the following approaches to populate `VASTTagURI` in
VAST XML responses:
1. An exchange can preserve the value of `VASTTagURI` element as part of VAST XML document returned by Google in the `BidResponse.seatbid.bid.adm` field **as is**, with exchange-specific macro expansions that normally apply.
2. DV360 can populate the `BidResponse.seatbid.bid.adm.nurl` field with a VAST document URL in bid responses to an exchange. An exchange can then pass that value with the `VASTTagURI` tag, with exchange-specific macros expanded normally as needed.
An exchange can specify additional VAST event and error trackers within VAST
XML document if necessary.
##### Meets technical requirements
In this example, Google (DV360) **creative VAST URI from the bid response
is passed verbatim**, with an exchange adding its specific VAST event and
error trackers.
```
XBid
```
##### Does not meet technical requirements
In this example, creative **VAST code or URI returned by Google**
*does not appear verbatim in the bid response* , and instead, an
exchange-specific VAST wrapper is used. Google-provided VAST code may be loaded
by an exchange-provided VAST wrapper (as defined in `VASTAdTagURI`
element, `https://video.exchange.example.com/creative?...`) upon SDK
loading an ad.
```
VideoExchange
```
## Deals
Exchanges participating in Open Bidding can use
[Preferred Deals](https://support.google.com/authorizedbuyers/answer/2604595)
(PD), [Private Auctions](https://support.google.com/authorizedbuyers/answer/2839853)
(PA) with Open Bidding. The deal ID and type must be specified as follows:
| Field | Description |
|---|---|
| `BidResponse.seatbid.bid.dealid` | The deal ID from the exchange's namespace associated with the bid and reported to publishers. This is arbitrary UTF8 text and must be no more than 64 bytes. |
| `BidResponse.seatbid.bid.ext.exchange_deal_type` | An enum specifying the type of deal. This is reported to publishers and affects how the deal is treated in the auction. Possible values are: ``` OPEN_AUCTION = 0; PRIVATE_AUCTION = 1; PREFERRED_DEAL = 2; EXCHANGE_AUCTION_PACKAGE = 3; ``` |
The following is a sample bid response for PD/PA.
```
id: "ECHO_BIDREQUEST_ID"
seatbid {
bid {
id: "BID_ID"
impid: "1"
price: 1.23
adm: "AD_TAG"
adomain: "DECLARED_LANDING_PAGE_URL"
cid: "BILLING_ID"
crid: "CREATIVE_ID"
dealid: "DEAL_ID"
w: 300
h: 250
[com.google.doubleclick.bid] {
impression_tracking_url: "IMPRESSION_TRACKING_URL"
exchange_deal_type: "DEAL_TYPE"
}
}
}
```
## Cookie matching
In order to populate Google-hosted
[match tables](https://developers.google.com/authorized-buyers/rtb/cookie-guide#match-table),
Open Bidding participants can use any of the options below that best suit their
needs:
- Cookie Matching: Buyer or exchange-initiated matching [Learn more](https://developers.google.com/authorized-buyers/rtb/cookie-guide#how-it-works).
- Pixel Matching: Google-initiated matching [Learn more](https://developers.google.com/authorized-buyers/rtb/cookie-guide#pixel-matching).
- Cookie Match Assist: Exchange-initiated matching with their bidders [Learn more](https://developers.google.com/authorized-buyers/rtb/cookie-guide#cookie-match-assist).
**Note:** Open Bidding participants are not able to create, populate, or target user lists at this time.
## Managing latency
You should use the trading locations found in the
[Peering Guide](https://developers.google.com/authorized-buyers/rtb/peer-guide#trading_locations)
to estimate the latency your bidder endpoints will have when responding to
incoming bid requests.
> [!IMPORTANT]
> Inventory is generally sent through the closest trading location, but this isn't guaranteed. The only way to guarantee access to all impressions is to have bidder endpoints in all trading locations.
Large exchanges that receive a high volume of bid requests should consider
entering into a peering arrangement with Google to reduce latency and latency
volatility. [Learn more about peering](https://developers.google.com/authorized-buyers/rtb/peer-guide#peering).
## Click macros
We recommend that you implement click macros. These will allow reporting
that includes clicks and click-derived metrics for your account and for the
publishers you work with. [Learn more](https://support.google.com/authorizedbuyers/answer/3187721).
## APIs
Open Bidding customers can use the [Authorized Buyers REST APIs](https://developers.google.com/authorized-buyers/apis/guides/start)
to access data that may be useful for troubleshooting purposes. Only the
following API resources are currently accessible:
- [v1.4 Performance Report](https://developers.google.com/authorized-buyers/apis/v1.4/performanceReport/list)
- [v2beta1 RTB Troubleshooting](https://developers.google.com/authorized-buyers/apis/guides/v2/rtb-troubleshooting)
You can contact your Technical Account Manager to configure your account
for accessing these APIs, and to retrieve the account ID needed to make API
calls. For technical support in using these APIs, you may contact the
adxbuyerapi-support@google.com support alias.
## Additional resources
- [Best practices for managing connections](https://developers.google.com/authorized-buyers/rtb/practices-guide#managing-connections)
- [Using bid URL macros](https://developers.google.com/authorized-buyers/rtb/request-guide#Bid-URL-Macros)
- [Decrypting price confirmations if you use the WINNING_PRICE macro](https://developers.google.com/authorized-buyers/rtb/response-guide/decrypt-price#scenario)
- [Testing recommendations and best practices](https://developers.google.com/authorized-buyers/rtb/test-guide)
## Sample bid requests and responses
Bid request and response samples for all supported protocols can be found in
the [Request](https://developers.google.com/authorized-buyers/rtb/request-guide#sample-bid-requests)
and [Response](https://developers.google.com/authorized-buyers/rtb/response-guide#sample-bid-responses)
guides.