Considerations for Using Multi-Ad Server Support for Check Availability

Use a multi-ad server configuration when your organization integrates with more than one ad server for checking inventory availability. If you use only a single ad server, continue to use the standard integration definition AdServerIntegrationForAdSalesManagement to configure external callout details.

For both check availability and order integrations, the system first reads callout details from integration definition attributes. Specifically to check availability, Salesforce then checks whether the NamedCredentialReference and AdServerProperties fields on the ad server record contain values. If both fields contain values, the system uses those values to support the multi-ad server feature. Select the ad space specifications for the ad server for each line item. This configuration makes sure that Salesforce applies the correct ad server context when checking availability.

To support targeting values across multiple ad servers, create multiple records in the AdTargetSegmentValue object with different ServerIdentifier values for each ad server. Here's an example where you configure Sports Enthusiasts across two ad servers:

Note Include an ad server identifier in the Name field when creating targeting admin data in AdTargetSegmentValue. Your users can distinguish between ad servers in the targeting configuration window. For embedded targeting, configure ad server-specific targeting values for ad server-specific products in the AdProductDefaultTargetValue object.

The AdTargetSegmentValue object doesn’t contain ad server information. No system validation exists to verify that a targeting value matches the intended ad server. Verify how duplicate targeting values for multiple ad servers render on the user interface, specifically for geo targeting.