Find answers to frequently asked questions about integrating with the
Display \& Video 360 Deal Sync API.

## Q: What is my Exchange ID?

A: The exchange ID is assigned by the Display \& Video 360 team during
authentication setup.

## Q: What is the purpose of the Order and Product hierarchy?

A: This hierarchy allows publishers and advertisers to negotiate multiple
deals and submit them together as a single negotiation object. There are
restrictions: all products under an order must share the same transaction type
and pricing type. **It's fine to always use a 1-order, 1-product setup.**

## Q: Is there a deal type available for ALL advertisers?

A: The Deal Sync API is designed for private deals. For public deals curated
for all advertisers, see [Auction Packages (Inventory
Packages)](https://developers.google.com/display-video/seller/guides/auction-package/overview).

## Q: What happens if a deal has no end date?

A: An end date is required, so setting a date in the future works fine. The
maximum allowed year is 2036. End dates can be updated or extended in the
future.

## Q: Does the dimensionCreativeConfig field allow for multiple sizes?

A: Yes, but only a single creative type is allowed per product.

## Q: Are Native creatives supported for Programmatic Guaranteed (PG) deals?

A: No. Reservation (guaranteed) deals don't support Native creatives
(`CREATIVE_TYPE_NATIVE`).

Contact your Google representative if you want to run
Programmatic Guaranteed deals that accept Native creatives.

## Q: Do you accept auction pricing for reserved transactions?

A: No. Reservation (guaranteed) deals only support fixed pricing.

## Q: Is duration required for video Programmatic Guaranteed (PG) deals?

A: No. If left unset, duration defaults to `ANY`.

## Q: Do any Order statuses cause a deal to stop transacting?

A: No. The Order is purely a negotiation object. Changes don't take effect for
ad serving until the advertiser accepts the Order.

## Q: What happens to an accepted deal if the exchange sends an update call?

A: The deal continues serving under its previously accepted terms. Once the
advertiser accepts the updated terms, the deal begins serving with the new
terms.

## Q: Will a deal continue to serve if updated terms haven't been accepted yet?

A: Assuming the CPM has already changed on the exchange side and is reflected
in the bid request:

1. **For reservation deals:** The deal won't spend until re-accepted by the advertiser. Line items are generated based on deal terms; updates remain in negotiation until accepted by the advertiser.
2. **For non-reservation deals:** Serving depends on the line item targeting the deal. If bid requests match the line item criteria targeting this deal, serving continues.

## Q: Can we reuse a deal ID across multiple deals?

A: No. `external_deal_id` must be unique across all products.

## Q: Can a deal have multiple partners?

A: If you want to associate a deal with multiple partners, send your deal to a
Central Partner.

## Q: Can the partner ID associated with a deal change after creation?

A: No. The partner can't be changed once an Order has been created.

## Q: Do you support multiple publisher names in an Order?

A: The publisher name field is a string used for informational purposes for
the advertiser. You can specify multiple publisher names separated by commas,
or state "Multiple publishers from Exchange X".

## Q: What is the difference between "CANCELED" and "ARCHIVED" Order statuses?

A: Users can archive and restore orders. Once canceled, an order can't be
reactivated or uncanceled.

## Q: What are "Instant Deals"?

A: Instant Deals are a separate integration effort using the Seller API
endpoint. Ignore attributes specific to Instant Deals; they aren't related to
the Deal Sync workflow.

## Q: What should I check if I receive a Bad Request error?

A: The following are several common causes:

1. Check the reference guide to ensure all required fields are populated.
2. Verify that `external_deal_id` is unique across all products.
3. Ensure reservation deals don't specify auction pricing.

If the issue persists, test the request with an HTTP client such as
[Postman](https://www.postman.com/) to inspect detailed error messages in the
response body.

Contact the Display \& Video 360 Seller API support team if none of the
preceding solutions resolve the issue.