PRODUCT
Follow

Summary

When the Smart Versioning ad is displaying a default image, it is showing the default image of the master ad instead of the default image for each version.

Environment

  • Smart Versioning

Required information

  • Ad ID
  • Test page

Solution

  • We tried enabling the CORS header option on the site account and asking the AM to re-saved placement, re-attaching the ad. This didn’t work because this setting only affects Bursting Server, not Display Server, and the relevant xml files are located on Display Server.
  • Enabled the CORS header option on the site account and asked the AM to re-saved placement, re-attaching the ad
  • Try manually adding the Access-Control-Allow-Origin: * in the response headers using Fiddler
  • The non-IE browsers refuse to load the xml into js because the the js is running on the site domain whereas the xml is called from our ds.serving-sys.com domain

Case Examples

Ticket IDSummary
8269 The client saw the master ad backup image (not the version specific one) showing up on mobile impressions.
6184 The client is seeing a SV ad showing a backup image for the master ad instead of the individual version backup image.
12611 Client has a polite banner with no default-flash element, so it must show a default image while waiting for the rich-flash to download. In NCM it shows the ad-level default image, In OCM it shows the version-level default image.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments