This checklist shows you the most important points that you should clarify and consider before going live with Inxmail Commerce. Detailed descriptions can be found in the linked articles. You can also use our Starter Guide to get started.
Checklist Inxmail Commerce
If you use Inxmail Commerce via the user interface, this checklist is the right one for you.
Basic settings
-
Open Inxmail Commerce at https://[alias].app.inxmail-commerce.com/#/login
You will receive the exact URL from your Inxmail contact person.
-
Optional: Create additional users
Configure source system
-
Install integration (Oxid, Magento, Shopware, SAP Hybris, Spryker)
or:
-
Connect Inxmail Commerce via REST API
Set up List-Unsubscribe header or List-Help header
-
Store a space-wide List-Help header as back-up. The space-wide List-Help header applies to all mailings that do not have their own List-Help header or List-Unsubscribe header.
-
Store a List-Help header or List-Unsubscribe header for your mailing.
-
Activate error notifications. This way, you will be notified immediately in case of problems with event configuration or dispatch.
No dispatch without unsubscription alternative: Mailings without List-Unsubscribe header or List-Help header cannot be sent.
Set up ‘Brand Identity Protection’
-
Configure technical settings for best deliverability
-
Optional: Set up BIMI
Set data – configure events
-
Create event XML
-
Set placeholders
-
Understand event tags
-
Create preview profiles
Create mailings
-
Create mailing, via HTML editor or via Mail Builder
-
Define sender address(es) based on your authenticated sending domain
-
Set List-Unsubscribe header or List-Help header depending on the mailing type.
-
Add modules and master modules (only for Mail Builder)
-
Make sure that legal requirements for email marketing are being met, e.g. data protection-compliant tracking
Note mailing size: We recommend that you keep your mailing size below 102 KB. This will help you avoid display problems with Gmail, as the Gmail email client will clip larger emails in your recipient's inbox.
If your average mailing size exceeds 150 KB per mail within a month, you will be charged for additional traffic for every 150 KB (see price list). A mailing including attachments must not exceed 6 MB in size so that it can still be sent.
Set up a workflow
Checklist mail relay
If you use Inxmail Commerce in the background as a dispatch system (= mail relay) and not via the user interface, this checklist is the right one for you.
Basic settings
-
Open Inxmail Commerce at https://[alias].app.inxmail-commerce.com/#/login
You will receive the exact URL from your Inxmail contact person.
-
Optional: Create additional users
-
Optional: Inxmail can enable the tracking of openings / clicks for you.
Note: Contact your Inxmail contact person or Care-Consulting@inxmail.de for more information.
Configure source system
-
Set up mailing delivery via SMTP or REST API
-
Optionally, you can set up email specific reporting via email header entries (so-called correlation IDs)
-
Make sure that legal requirements for email marketing are being met, e.g. data protection-compliant tracking
Note mailing size: We recommend that you keep your mailing size below 102 KB. This will help you avoid display problems with Gmail, as the Gmail email client will clip larger emails in your recipient's inbox.
If your average mailing size exceeds 150 KB per mail within a month, you will be charged for additional traffic for every 150 KB (see price list). A mailing including attachments must not exceed 6 MB in size so that it can still be sent.
Set up List-Unsubscribe header or List-Help header
-
As an additional unsubscription alternative, a List-Unsubscribe header or List-Help header must be set up for each mailing in the source system.
-
Activate error notifications. This way, you will be notified immediately in case of problems with event configuration or dispatch.
No dispatch without unsubscription alternative: Mailings without List-Unsubscribe header or List-Help header cannot be sent via mail relay.
Set up ‘Brand Identity Protection’
-
Configure technical settings for best deliverability
-
Optional: Set up BIMI
Set up return transfer of bounces and reporting data (or reaction data) to third-party systems.
-
Optionally, bounce data can be retrieved via REST API or forwarded via email.
-
If Inxmail has enabled the tracking of openings / clicks for you, recipient responses can be retrieved via REST API.
-
We also recommend that you retrieve complaints (spam complaints) via REST API or email in order to exclude recipients in the third-party system from future dispatch.
