Supplied HTML Eblast Process and Requirements


  • All supplied HTML files provided to PMMI Media Group should be ready-to-send. Please carefully review all PMG requirements, your HTML code and all email content prior to submitting your file.
  • After submitting the completed HTML file to your Client Success Manager (CSM), your CSM will verify the file meets all specifications and run the file through an email testing tool.
  • Your CSM will inform you if testing is successful. If your file does not pass testing or does not meet specs, the CSM will return the file to you for revision.
  • We reserve the right to refuse files that do not meet our requirements. 
  • Please note: PMMI Media Group will not perform HTML consulting or coding/design support.


  • We will track up to 10 links in your email.
    • Additional links can be purchased if needed – reach out to your sales rep to purchase.
  • Advertisers must remove their own footer information. The advertiser’s company-specific privacy policy and opt-out links and cannot be included in any supplied HTML email sent by PMG.
  • Client supplied HTML file must include PMMI Media Group’s footer, consisting of PMG mailing address, disclaimer, unsubscribe/opt-out and privacy policy links.
  • Email content mentioning PACK EXPO (copy and images) must use the proper spelling of the trade show name. If an official PACK EXPO logo image is included, the image must be from PACK EXPO’s multimedia gallery web page. Trade show names include:
    • PACK EXPO International
    • PACK EXPO Las Vegas
    • PACK EXPO East



  • Use a secure web server to host all images. Images hosted on an unsecured web server run the risk not rendering in the final, delivered eblast.
  • Use tables. Email clients live in the past so all emails must be built using tables for layout. Example: <table>, <tr> and <td>
  • Use inline styles. Use of external stylesheets is not supported, so to ensure your styling is visible, use inline styles.
    • Example: <tr style="padding-bottom:20px;">
  • Test your code. Check your code in multiple browsers and in multiple email clients to make sure all users get the same experience when viewing your email. Each email client and browser reads code differently, therefore the same code is not always displayed the same way across email clients.
  • Use text buttons for a "call for action".
  • Make sure the HIML code Includes a doctype declaration.
  • Make sure to include the Title HTML tag, with a title that's different from the default one created by many HTML editors (e.g., 'Untitled' or 'New page').
  • Always include one or more links so you can track activity on the
    message but limit the number of links to 10 or less.
  • Avoid using special characters. Instead use the HTML equivalent
    • Example: &amp; is the code for '&'
  • Always set links to open in a new window by using the target attribute set to _blank. Otherwise, you risk having the destination URL open within the current frame of the Web-based email client the customer may be using.



  • Don't use JavaScript, ActiveX, or Flash. You cannot include any type of JavaScript – no fancy pop-ups or auto-scrolling emails please! This increases the likelihood of your email being sent to a junk folder.
  • Don't use <p>, <div>, <ul>, or <li> tags. Stick to tables when building your HTML for email clients. Other tags don't have universal support across all email clients, so it's best to keep it simple to ensure that your email performs well for everyone.
  • Don't use Dreamweaver to edit or create your HTML. Dreamweaver is not a program that was designed for editing or creating code for emails. It will create code that doesn't follow the best practices listed here.
  • Don't use background images. They are often not displayed.
  • Don't use absolute positioning.
  • Don't position images using X-Y coordinates.
  • Don't use the image "low source" attribute (lowsrc).
  • Don't use the image "roll-over" attribute (hsrc)
  • Don't use the image map "shape" attribute: image maps should not be used at all due to inconsistent support.
  • Don't use anchor links.
  • Don't use pop-ups.