The Content Store is the central library for files and HTML content in Mapp Engage. You store an image, a document, or an HTML snippet once and use it in emails and landing pages. Each item in the Content Store is called a content store element.
What You Can Store
You can upload files or create HTML content directly in the Content Store. Mapp Engage sorts each element into a tab based on its file type (MIME type).
Tab | Contains |
|---|---|
Images | Image files, for example JPEG, PNG, and GIF |
Text | Text-based files and HTML content, for example HTML, CSV, XML, and plain text |
Media | Video and audio files |
Other | All other file types, for example PDF |
All Files | All elements |
Mapp Engage does not accept files that can contain executable or malicious code, for example .exe or .lnk files. Every upload is scanned for viruses. If an image is rejected because of suspicious content, see Why does uploading an image to Content Store fail with XSS error due to suspicious content?
File Size
By default, you can upload images of up to 1 MB. Mapp Engage removes unnecessary metadata from uploaded images.
If you need a higher limit, contact your account manager. The limit can be raised in steps of 1 MB up to 4 MB. The request needs approval from engineering.
For emails, keep images small. The recommended size is 100 KB per image. Large images and attachments hurt deliverability and increase data costs for contacts on mobile networks.
Use 72 dpi for images that recipients view on screen and 300 dpi for images that recipients print.
Add Elements to the Content Store
Create an Element
Go to Content > Content Store and click Create.
Enter a Name.
Optional: Enter a Description. For images, the description is used as ALT text when you insert the image into a message.
Under Content / Attachment, select Upload File and click Browse to select a file. To create HTML content instead, select HTML / HTML Editor.
Optional: Set an Expiration Date. See Expiration below.
Click Save.
For all fields, see Compose Content Store Element.
Images Stored Automatically
Images can also get into the Content Store without a manual upload:
HTML emails: If an HTML email references images that are not yet in the Content Store, Mapp Engage can ask you to upload them in the Upload Missing Images window. The uploaded images are stored as content store elements. The element name is taken from the image name in the HTML code. For the image handling options, see Add and Configure Images in HTML Emails.
CMS emails: Images that you upload in a paragraph of a CMS email are saved to the Content Store and can be reused in other messages.
Use Elements in Messages and Landing Pages
Each element has an ID and two placeholders. To see them, click the element in the Content Store. The Details section opens below the list.
Placeholder | Inserts |
|---|---|
| The element itself |
| A link to the element |
The Details section lists the placeholders for emails under Placeholder for Email and for landing pages under Placeholder for Website. Both use the same format. For the steps, see Use a Content Store Element in an Email.
To attach a file from the Content Store to an HTML email, see Add Attachments to an HTML Email.
Expiration
By default, an element is deleted 180 days after it was last used. Each use restarts the 180 days, for example when a recipient opens an email that loads the image.
If you turn off Automatic Expiration Date and set a date, the element is deleted on that date, even if it is still in use.
Warning
When an element is deleted, emails that were already sent show a broken image instead. See Image Missing After Sendout Due to Expired Content Store Element.
Categories
Use content element categories to group related elements, for example all images of a campaign. An element can belong to several categories. See Organize Content Store Elements with Categories.
Permissions
Permission | Allows |
|---|---|
245 CMS: Edit own content store elements | View and edit your own elements |
246 CMS: View all content store elements | View all elements in the system |
244 CMS: Edit all content store elements | Edit all elements in the system |
311 System Administration: View categories | View all categories, including content element categories |
310 System Administration: Create and edit categories | Create and edit all categories, including content element categories |
If Visible to Everyone is set to No for an element, access to it depends on these permissions. For all permissions, see Global Permissions List.
Related Topics
Reference for the Content Store screens: