You are here:
Configure Multi-Ad Server Support for Check Availability
Set up your Ad Server records to route check availability requests to different ad servers.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited editions with Media Cloud- Advanced |
| User Permissions Needed | |
|---|---|
| To configure multi-ad server support for check availability: | Media Cloud Designer |
Make sure that you create named credentials for each ad server's orchestration service base URL. Instead of a specific ad server, point the named credential to the base URL of the service that orchestrates callouts.
- Go to the ad server record that you want to configure.
- In the Named Credential Reference field, enter the named credential that points to the base URL of your orchestration service for this ad server.
-
In the Ad Server Properties field, enter a JSON string with these properties:
{ "CHECK_AVAILABILITY_API_PATH": "<your-api-path>", "API_TIMEOUT": 10000 }Where API_TIMEOUT is the timeout value in milliseconds for the API callout.
- Save the Ad Server record.
- Repeat steps 1–4 for each additional ad server.
- (Optional) To support targeting across multiple ad servers, create records in AdTargetSegmentValue with unique name and ServerIdentifier values for each ad server. Include an ad server identifier in the Name field to help users distinguish values in the targeting window.
- (Optional) For embedded targeting, configure ad server-specific targeting values in AdProductDefaultTargetValue for each ad server-specific product.
When users check availability for a line item, the system uses the callout details from the associated Ad Server record to route the request to the correct ad server.
Did this article solve your issue?
Let us know so we can improve!
