• Any HTML5 code submitted must be built to work correctly on HTML5 enabled browsers and environments.
  
  • The latest versions of Chrome, Firefox, Internet Explorer and Safari should be capable of properly displaying most HTML5 code.
  • A static backup image file (JPG, GIF, or PNG) is required. Any browsers incapable of displaying HTML5 will show the backup image.
  • All HTML5 code must adhere to the ad guidelines and specifications for the applicable ad unit.
  • HTML5 code must be submitted in accordance with the ad unit's submission lead time for proper testing and any necessary revisions. If errors occur, and are not repaired in time for launch, Edmunds reserves the right to start the ad flight by delivering the backup file.
  • Edmunds is not responsible for troubleshooting specific issues with HTML5 creative, such as appearance, functionality, debugging or reporting discrepancies.
  • When available, HTML5 rich media creative should be submitted in the form of a third-party tag from an approved vendor: Third-Party Serving & Rich Media
  • Please refer to the IAB's latest HTML5 standards for further guidance: https://www.iab.com/guidelines/html5-for-digital-advertising-guidance-for-ad-designers-creative-technologists/
  • Following is the Edmunds' option to be able to first-party serve HTML5 creative in Google Ad Manager (GAM):

HTML5 zip bundle is provided to Edmunds for Edmunds to host/first-party serve in GAM.  Please refer to these html5 requirements.

• All additional tagging for client tracking (impression, click, etc.) should be embedded in the code prior to delivery of creative. Tagging should be in accordance with GAM requirements. Please see the following for more information : https://support.google.com/dfp_premium/answer/7046799?hl=en&ref_topic=7041998
• If the location of files being called within the HTML5 code is broken or inaccessible, the ad may not display properly.