The following disclaimer will be added to the footer of each message above the opt out statement if you do not add it to your message. If possible, leave a blank row with the word ‘opt-out’ on the bottom of your message:

Disclaimer: This email is being sent on behalf of (Exhibitor/Sponsor Name) and is not part of the official APIC26 program as planned by APIC. This content is neither sponsored nor endorsed by APIC.

Opt-Out Statement:  You are receiving this email because of your relationship with APIC. If you do not wish to receive communications from the APIC 2026 Annual Conference industry partners such as this email, you may unsubscribe at any time. An opt-out from this email will opt you out of ALL emails from APIC 2026 Annual Conference exhibitors and sponsors.

This message was sent by the APIC
1400 Crystal Drive, Suite 900 | Arlington, Virginia, 22202 | United States

If you would like to add this yourself, please place the following text at the bottom of your email. The unsubscribe link will be added once testing begins-

This email is being sent on behalf of (Exhibitor/Sponsor Name) and is not part of the official APIC26 program as planned by APIC. This content is neither sponsored nor endorsed by APIC.

You are receiving this email because of your relationship with APIC. If you do not wish to receive communications from the APIC 2026 Annual Conference industry partners such as this email, you may unsubscribe at any time. An opt-out from this email will opt you out of ALL emails from APIC 2026 Annual Conference exhibitors and sponsors.

This message was sent by the APIC
1400 Crystal Drive, Suite 900 | Arlington, Virginia, 22202 | United States

Use of the APIC26 logo in all email messages must be approved in advance.

All event mentions in marketing materials, including the subject line and preheader, must appear as follows:

APIC 2026 Annual Conference
APIC 2026
APIC26

All marketing materials are subject to approval prior to distribution.  Messages should be in .html format but can be submitted via PDF at this stage. 

• The disclaimer and opt-out statement above will be added to the footer of every message.
• All mentions of the APIC Annual Conference on eblasts (including the subject line and pre-header text) or other communications must be displayed as outlined above.
• All links must be live.
• All images should be included.

Email Message: All messages must be in .html format and include the required disclaimer above.  A text version is requested, but not required.

If you require assistance with creating your message in HTML format, please contact us for more information.

• HTML Version: (.html file format). All images should be hosted. Image hosting is available for a small additional fee.  If you would like assistance, please inquire for a quote.
• Plain text version: no dynamic links (they should all be spelled out), no images or special characters. (.txt file format).  This is not required but is suggested for recipients that have high-security settings and only receive plain text messages.

View Online Link:  If you would like a view online link added to the top of your email, please include a blank row on top with the following text: 'View Online' or "View in Browser".  For the link use: # (we will edit & add the link) or  (this tells the system to add the link automatically once your email is set up).

CAN-SPAM Footer (Opt Out Text):  We add the opt-out text.  Please include a blank row at the bottom of your email as a placeholder.

From Line: The from line of each message will say: APIC on behalf of (Your Company Name Here)

Subject Line: Create a subject line for your message. You are encouraged to keep it under 50 characters to avoid truncating on computers. See section below form more information about subject lines on desktop and mobile devices.

Snippet/Pre-Header Text: When viewing an inbox, an email snippet is the very first line of text that your email recipient will see, following the email subject line. Some good practices when determining your snippet:

• Snippets should remain between 30-70 characters in length.
• They should be a continuation of the subject line.
• Include a specific, actionable CTA to encourage readers to open the message.

See section on Subject Lines & Preheader text below for more information.

Seeds/Decoy Email Addresses: Email addresses for yourself and colleagues (if requested). These email addresses will be used to send a test of each message for approval as well as the final deployment of your message.

All submissions should be sent at least two weeks in advance of your approved deployment date.

Please Note:

• This is not the form you already completed when you registered and/or paid.  This form simply requests the information needed to setup your eblast for testing and deployment.
• Each transmission includes 2 test messages. Additional tests will incur an additional fee per test.
• Creative services are available. Fees will apply to convert messages to HTML or remove coding from a 3rd party system. Inquire for details.
• Transmission reports will be sent for each eblast after the event.

1. General Email Coding Guidelines

• Use tables for layout instead of divs, as many email clients do not support complex CSS positioning.
• Stick to basic HTML (avoid JavaScript and external CSS, as most email clients block them).
• Keep your design simple by using table-based layers and avoiding HTML floats or positioning.
• The width of your emails should be 600-800 pixels (must be a whole-number pixel value).

2. Inline CSS for Styling

• Use inline styles instead of external stylesheets.
• Keep styles simple: font styles, colors, padding, and margins.
• Use fallback fonts to ensure consistency across email clients (e.g., font-family: Arial, sans-serif;).

3. Fonts in Emails

• Use whole-number font sizes (e.g., 10px instead of 9.5px).
• Email-Safe Fonts: Arial, Courier New, Georgia, Helvetica, Lucida Sans, Tahoma, Times New Roman, Trebuchet MS.
• Web-Safe Fonts: Lato, Open Sans, Oswald, Oxygen, Poppins, Quicksand, Merriweather, Raleway, Roboto, Rubik, Ubuntu.
• Custom fonts may not display properly in all email clients. Limit their use to logos or images.

4. Responsive Design (Mobile-Friendly)

• Use media queries for responsiveness (note: not all email clients support them).
• Make sure text and images are mobile-friendly (use a 600px width for the email body).
• Ensure links are easily visible and clickable on mobile devices.

5. Images & Accessibility

• Use img tags with alt text for accessibility and fallback support.
• Keep image file sizes lightweight. Example: A complex JPG at 500px by 500px should be around 100kb.
• Suggested image width- 600-800px. (some larger images may not load quickly)
• Make sure image dimensions use whole-number pixel values.
• Do not design an email that is one large image—this increases the risk of spam filtering and reduces accessibility.

6. Avoid Unsupported Features

• No JavaScript (most email clients block it).
• Avoid complex CSS like flexbox, grid, and background images (they may not render properly).
• Do not use Flash-based elements. If you need animation, use a .GIF instead.
• Do not use a PDF-to-Email converter or Word processing software—they generate incompatible code.
• At this time, email platforms do not support Canva email templates, as iframe content cannot be displayed in sent emails.

7. Additional Best Practices

• Use as few columns as needed to keep emails simple and readable.
• Avoid overlapping visual elements.
• Include text content in the email—never send an email with only an image.
• If you'd like a view online link, include a blank row at the top with one of these: "View Online" or "View in Browser"
  • Use # as a placeholder, or to have the system generate the link automatically.
• Include a contact method—the send/reply address is not monitored in real-time.

8. Opt-Out & Compliance

• An opt-out statement is provided; you are not required to add one. It is appreciated, but not required, to include a blank row at the bottom as a placeholder. If you require a copy of this text to get approved internally, please contact us.

9. Need Help?

Email coding is not as advanced as web design. You're encouraged to use a program dedicated to build your email in HTML format. Plan Bee Direct offers this service for an additional fee. Please contact us for more information and a quote.

Want inspiration? Check out this example email template: View Example or view some of the past templates we have built here.

We use a universal system font by default on our email designs because email clients only support a limited set of fonts. While custom fonts might display correctly in some email clients, they will default to a standard system font if not supported.

• Email Safe/Friendly Fonts: Arial, Courier New, Georgia, Helvetica, Lucida Sans, Tahoma, Times New Roman, Trebuchet MS
• Web Safe Fonts: Lato, Open Sans, Oswald, Oxygen, Poppins, Quicksand, Merriweather, Raleway, Roboto, Rubik, Ubuntu.

Web-safe fonts and email-safe fonts are different. Web-safe fonts are specifically made for use on websites and can’t be found in operating systems or software. They’re added to websites using special tools. Email clients, like Gmail or Outlook, have their own set of email-safe fonts. These fonts may not be the same across all email clients. For instance, Gmail supports fonts like Open Sans and Roboto, but Outlook and Apple Mail don’t. However, if an email client doesn’t support a specific font, it will use a default font instead:  Apple Mail: Helvetica, Gmail: Arial, Outlook: Calibri.

Quick Reference

Our responsive email templates ensure your emails look stunning and function correctly on any device. We specialize in creating adaptable designs that automatically adjust to various screen sizes, providing an optimal viewing experience for your audience.

1. Text Content: Include all the text and any links you’d like to incorporate in the message, clearly indicating their placement.
2. Images: Upload your logo and any other images you’d like to feature in the message.
3. Message Example (Optional): If you have an example or template in mind for how you’d like the message to look, feel free to upload it below. This will ensure we create a message tailored to your vision.

Follow this link to receive a quote in advance.

• Use images sparingly.
• Use standard web fonts.
• Keep the message focused on a single objective.
• Drive more clicks to your landing page with a clear & focused call to action.
• Include Links to Your Social Media Profiles.

Yes. We send a test once the content has been approved & setup form is received.

Yes. This is strongly encouraged since the send address is not monitored daily.

Yes. Plan Bee Direct can build your message as a responsive HTML email. We offer this service at a discounted rate for these types of deployments. After you approve the proof, we load it into our email system and send a test email for your final approval. Find out more here.

Yes and no. You can send your message in Word or PDF format at the approval stage, but if you have images in your email (and/or hyperlinks, special characters, etc.), your email needs to be in HTML format. Plan Bee Direct can build your message as a responsive HTML email. We offer this service at a discounted rate for these types of deployments. After you approve the proof, we load it into our email system and send a test email for your final approval. Find out more here.

No, attachments cannot be sent. If you want to share a PDF or another document, host it on your website and include a link in the email so readers can download it.

All content is due 2 weeks before your reserved deployment date, unless otherwise noted.

No. We add an opt out statement to each message.

Yes. While the disclaimer does not need to be displayed prominently, it must be displayed on each email. If you do not add it to your message, we will add it above the opt out statement.

Yes. Reports with open and click rates are sent within two weeks after the conference ends.

No. The sending domain is used for all sponsors. Releasing any information to a third party campaign manager will expose metrics for every campaign. The only reliable way to access your own tracking is through tagged links (UTM codes) in the message. These feed into your own Google Analytics or Campaign Manager setup.

When creating the HTML, you will need to add your own UTM codes to each link and test them to make sure they work before submitting the HTML to us. This way you can track your campaign on your end.