HMP GLOBAL MEDIA KIT

Digital Specifications

Below you will find up-to-date technical specifications, standards, and guidelines for the delivery of all digital web, email, video, and mobile advertising content across our HMP Digital properties.

Web Display Placements

Below are the specifications for web display placements.

PROFILE LEADERBOARD MEDIUM SQUARE SKYSCRAPER MOBILE MEDIUM SQUARE MOBILE FLOATER
DIMENSIONS 728x90 300x250 160x600 300x250 300x50 / 320x50
EXPANDABLE SIZE 728x315 600x250 600x600 N/A N/A
EXPANDABLE DIRECTION Down Left Right N/A N/A
Z-INDEX RANGE 0-4,999 0-4,999 0-4,999 0-4,999 0-4,999
MAXIMUM INITIAL LOAD 200 KB 200 KB 200 KB 200 KB 200 KB
MAXIMUM FULL LOAD 300 KB 300 KB 300 KB 300 KB 300 KB
VIDEO ALLOWED Yes (When Expanded) Yes (When Expanded) Yes (When Expanded) No No
SOUND ALLOWED Yes (On Click) Yes (On Click) Yes (On Click) No No
MAXIMUM ANIMATION TIME 15 Seconds (1 Loop) 15 Seconds (1 Loop) 15 Seconds (1 Loop) N/A N/A
FRAMES PER SECOND 24 FPS 24 FPS 24 FPS N/A N/A
FILE TYPE JPG, PNG, GIF, HTML5* JPG, PNG, GIF, HTML5* JPG, PNG, GIF, HTML5* JPG, PNG, GIF, HTML5* JPG, PNG, GIF, HTML5*
THIRD-PARTY SERVING Yes Yes Yes Yes Yes
THIRD-PARTY TRACKING Yes Yes Yes Yes Yes
SUPPORTED THIRD-PARTY AUTHENTICATION SERVICES* DCM, Comscore, DoubleVerify (Monitoring Only), and IAS DCM, Comscore, DoubleVerify (Monitoring Only), and IAS DCM, Comscore, DoubleVerify (Monitoring Only), and IAS DCM, Comscore, DoubleVerify (Monitoring Only), and IAS DCM, Comscore, DoubleVerify (Monitoring Only), and IAS

Special Notes

Asset Handoff: Please provide all assets 10 days prior to campaign launch for adequate testing time.

Audio Initiation: Must be user initiated (On Click: mute/unmute) Default state mute.

Video: 15 second maximum length (Unlimited user-initated). 1.1 MB additional file size allowed for host-initated video. Play, Pause, Mute required.

Video Creative with in-banner video must be third-party served. Auto-play video must utilize a polite download and must not exceed 30 seconds and 1.1MB. Auto-play video cannot be served via YouTube player. User-initiated video must not exceed 10MB. Video files must include "Play", "Pause", and "Mute" functions at minimum. Audio must be user-initiated only on click.

Expandable Units: "Close" or "X" on expanded panel and "expand" on collapsed panel. Minimum font size (8pt) 11px - 16(21px). Retract either click to close/expand or enable mouse-off retraction.

HTTPS Compability: All creative, including third-party tags and third-party tracking tags, must use secure protocol (HTTPS). Any creative that is not fully secure will be sent back for revisions.

Third-Party Tags: Must be In-house or approved third-party vendor.

Third-Party Authentication Services: Other services are supported. Please inquire with your sales representative to learn more.


HTML5 Package Guidelines

If sending an HTML 5 zip file, please make sure CLICKLINK tags are implemented. For guidance, please refer to our ad server documentation.

HTML5 provides introduces new options for developing ads. The IAB has developed "HTML5 for Digital Advertising" ( http://www.iab.net/html5) to help ad designers provide ads in HTML5 unit that will perform more successfully across the display advertising ecosystem. Please review this document and adopt its recommendations to help improve HTML5 ad performance in the industry.

Email Placements

PROFILE ENEWSLETTER LEADERBOARD ENEWSLETTER SQUARE
DIMENSIONS 728x90 300x250
NUMBER OF AVAILABLE PLACEMENTS 2 1
MAXIMUM FILE SIZE 256 KB 256 KB
FILE TYPE JPG, PNG JPG, PNG

Special Notes

Please Note: Sponsored eNewsletters require an individual 1x1 tracking placement for the top, middle, and bottom placements. Our eNewsletters consist of two 728x90 placements and one 300x250 placement.

Video Placements

SCRIPT COMPLEXITY SUPPORTED FORMATS DIMENSIONS FILE SIZE LIMIT VIDEO FORMAT HOSTING
iFrame or Javascript (Flash not accepted) HTML5 620/360 / 480x320 (16:9 Ratio) 500 MB MP4, MPEG, MOV Self or Third-Party Hosting Accepted

Annoucement Bar

MAXIMUM CHARACTERS LINK CAPABILITY SCROLL IMAGES
80 Yes No No

Custom Email/eBlast

Below are guidelines for best practices for custom email/eBlast deployments. Please review this guide when developing and designing an email deployment.


Best Practices: Guidelines

  • All custom eBlast assets and subject line must be submitted three (3) business days prior to deployment.
  • HMP will deploy a test deployment to the requested seed list once internal testing has concluded and internal QA is complete.
  • The subject line is subject to approval and must be no longer that 150 characters. Please refrain from using all capital letters, single word, SPAM triggering words, or characters requiring encoding.
  • Custom copy provided by the client must be final/regulatory approved. Once the final materials are received, we will provide you with a test deployment for approval prior to scheduled deployment.
  • HMP will not fix or make any changes to assets provided by the client. All requested changes will require updated assets from the client.
  • All tags must be implemented prior to HTML package hand off.
  • HMP reserves the right to reject any content that can affect the campaign response, hinder deliverability for future campaigns, or prevent messages from properly rendering.
  • All assets must be pre-formatted in an HTML document. We do not accept image-only, PDF, or Word documents.
  • A standard footer will be automatically included at the bottom of each deployment. The unsubscribe link is generated by our email system. Users who click the unsubscribe link will be directed to a page to confirm they wish to unsubscribe. An example of our footer is provided below:

    {{BRAND PLACEHOLDER}}
    70 E. Swedesford Road Suite 100,Malvern PA 19355
    This email was sent to email@address.com
    View in web browser
    Click here to unsubscribe
    Privacy Policy


  • Deployments sent from the Psychiatry & Behavioral Health Learning Network will also have the following language appended above the standard footer:

    The opinions and recommendations expressed do not necessarily reflect the views of Psychiatry & Behavioral Health Learning Network, Psych Congress, or HMP.

Best Practices: Design

  • Emails should be 600-700 pixels in maximum width. This will improve behavior within the preview-pane size provided by many clients.
  • Use grid-based layers and avoid complicated elements that require HTML floats or positioning.
  • Assume images will be initially blocked by email clients, or that certain images will completely fail to load.
  • Avoid using any background images.
  • Don’t design an email that’s essentially one large, sliced-up image. This hinders performance and also improves the likelihood the email will be filtered as SPAM.
  • Use basic, cross-platform fonts such as Arial, Verdana, Georgia, and Times New Roman.
  • Avoid elements that use JavaScript.
  • Verify your image links contain proper alt tags and display a clear call to action.
  • Ensure images are compressed to their full potential to prevent slow load times. The estimate breakdown of content should be 70% text and 30% image based.
  • Use only .GIF and .JPG formats for your images. Any other image formats will be rejected.
  • Be considerate of mobile devices and user accessibility. Is your email readable at arm’s length on a small screen? Will images slow down load time on a mobile device? Are your links easily accessible with the tap of a finger?

Best Practices: Development

  • Code all structure using the table element. For more complicated layouts, you should nest tables to build complex structures.
  • Please keep total email size under 100kb to avoid SPAM blocking.
  • Use element attributes (such as cellpadding, valign, and width) to set table dimensions. This forces a box-model structure.
  • Keep your CSS simple. Avoid absolute positioning and compound style declarations (IE: “font:#000 12px Arial, Helvetica, sans-serif;”), shorthand code (IE: #000 instead of #000000), CSS layout properties (IE: slot, position, clear, visibility, etc.), complex selectors (IE: descendant, child or sibling selectors, and pseudo-elements)
  • Use inline CSS for styling and don't link CSS from remote locations.
  • Use only absolute links for images and host your images on a reliable server.
  • Avoid JavaScript or Flash—these technologies are unsupported by email clients.
  • Account for mobile-friendliness, if possible. Use media queries to increase text sizes on small screens, provide thumb-sized (~46x46px) hit areas for links. Make an email responsive if the design allows for it.
  • Emails must use Unicode: UTF-8 to ensure special characters display in HTML. Any HTML content created or saved in Microsoft Word or Publisher and saved as HTML will not be accepted.
  • Test your code using a service such as Litmus.
Last Updated: Jan 26, 2021