iPost Essentials: Managing Assets, Data, and Email Content


Asset Library Requirements

  • Maximum File Upload Size:

    • Images: 292 KB
    • All Other File Types: 1 MB

  • File Name Requirements:

    • Must be unique within the Asset Library.
    • Cannot contain spaces (some email clients do not support spaces in image names).

Supported File Types:

  • Images: .gif, .jpeg/.jpg, .png, .svg (Max size: 292 KB)
  • Documents: .pdf, .doc/.docx (Max size: 1 MB)
  • Styles & Fonts: .css, .woff, .woff2, .ttf, .eot (Max size: 1 MB)

Data & Data Tables

Data Table Names:

  • Can contain only letters, numbers, and underscores.
  • Cannot start with a number.
  • Example: DataTableName_YYYYMMDD → MonthlyEmailData_20250101

Attribute Names:

  • May only contain letters, numbers, and underscores.

Available for Sending:

  • Enables the data table to be used for email sending.
  • If using a unique identifier (UID) instead of an email address, select the UID field as the Recipient Key.
  • The designated Email Column must have a Data Type of Email.
  • Selecting "Default to All Contacts" as the email column will only send to individuals who have already been sent an email. Instead, select the Email Attribute Name within the Data Table.

Testing:

  • Enables the data table to be used for test sending.
  • Maximum 20 contacts (rows) allowed in a testable table.

Date Format:

  • Must follow the 'YYYY-MM-DD HH:MM:SS' format.
  • Can be customized in Account Settings.

Email Drag & Drop Editor

  • Default Email Width: 500px.
  • Customization: To adjust, go to Settings → Content Area Width and enter your desired dimensions.

iTL Merge Variables

Purpose:

iPost Template Language (iTL) allows for:

  • Personalization
  • Dynamic content
  • Conditional formatting
  • Scripting within iPost emails

Case Sensitivity:

  • iTL is case-sensitive, so ensure exact syntax is used when adding personalized merge fields.

Test Mailing

  • Select Test Sendable Data Table(s):
    • Entering an Email Address will send to each record that contains that email address.
    • Instead, choose a data table with testing enabled to send only to contacts in that table.
    • This ensures the test accurately pulls in merged variables from the data table attributes for a more precise preview.