Configuring the Extension
After installing the extension you will need to configure a few settings. To do so:
- Log into your Magento admin console and navigate to Newsletter > MailUp > Settings & Field Mapping (v2.3 and above)
- In previous version of the extension, the navigation used to say Newsletter > MailUp > Connect to MailUp
- You can reach the name page under System > Configuration > MailUp
You will now be able to configure the MailUp Extension Settings
With version 2.3 and above, the MailUp extension supports multi-store installations. You can now set at the store view level:
- MailUp settings (e.g. which list in MailUp to connect the store to)
- Field mappings (which fields in the MailUp account to map the store fields to)
Settings set at the higher level (e.g. at the Default or Website level) can be used "as is" or overwritten at the store view level.
Here is a description of what the settings are and what they do.
Enable module debugging log
|Admin Console URL|
This URL is unique for each MailUp account. It’s the domain portion of the URL shown in your browser address field when you are using your MailUp admin console. It looks like something like g4a0.s03.it or ddbd.emailsp.net.
To locate it, just log into your MailUp account, launch the admin console, and look at the URL in the browser address field.
|Web Service User Name||Your MailUp API User Name. To retrieve your MailUp API user name and password, log into your MailUp admin console and navigate to Manage > Web Services|
|Web Service Password||Your MailUp API Password. Same as above.|
|List||The List within your MailUp account that you wish Customers to be subscribed to, by default.|
|Enable subscription checkbox during checkout|
Select yes if you wish to show the newsletter sign up checkbox during checkout. Here is how it is displayed:
The text shown can be edited as any other text string shown in the storefront (see how).
|Enable Automatic Data Export||Select yes to enable automatic data export from Magento into your MailUp list. Additional details.|
|Export Frequency||Select how often data will be updated and exported. (e.g. choose "Hourly").|
|Webhook crypt key||If you are encrypting webhooks, enter the encryption key that you used in the MailUp admin|
|Enable module debugging log||Enable the debugging log if you are experiencing any problems and need to communicate with our support team|
|Disable Newsletter Subscription Notification||This setting disabled the email that otherwise Magento sends by default to customers that subscribe to the store's newsletter. Since a subscription confirmation will be sent by MailUp when the customer confirms their subscription, this email sent by Magento represents a duplicate and could create confusion. We recommend therefore setting this flag to Yes.|
MailUp API Credentials
Once you've connected your Magento store to MailUp, the next step is to map fields between the two applications. This is done in the lower part of the Settings & Field Mapping page.
Here too, you have the ability to handle multi-store implementations of Magento:
- You can map fields at the Default settings level
- You can then override those mappings at the Website or Store View level
You can map a number of customer fields, and then several order-related fields.
Notes & Limitations
The date format used in the data that is exported to MailUp (E.g. order date) is always dd/mm/yyyy.
- This is true both for the data that is exported automatically (e.g. hourly data transfer from Magento to MailUp) and manually (using the customer segmentation feature of the extension)
- Keep this into account when configuring triggered messages in your MailUp account.
- Note that the date shown in Magento will reflect the Locale of the store (e.g. a US-based store will use dates in the mm/dd/yyyy format when using the customer segmentation feature of the extension)
MailUp is a multi-list environment, but recipient fields are shared across the various Lists in the same account, and each account comes with 40 customizable fields (so fields are limited in quantity). That means that if recipient "firstname.lastname@example.org" has the phone number in field 5 of List 1, the same data will appear if the same recipient exists in List 3. If the data were the "latest order date", this could be a problem in some scenarios as data for an order placed in storefront 1 (connected to List 1) would be overwritten by an order by the same customer (same email) placed in storefront 3 (connected to List 3 in MailUp), if the "latest order date" piece of information is mapped to the same field in MailUp.
This means that if you have multiple storefronts in Magento, you may not be able to map storefront-specific fields to a single MailUp account as you might run out of fields. Of course, there is no issue if you are using different MailUp accounts. The issue is just if you are using different Lists within the same account, connected to different storefronts in Magento.
For example, let's say you have 3 storefronts. If you map 20 fields for storefront 1, and 20 fields for storefront 2, you would not have enough fields left to map 20 fields for storefront 3, because you would need 60 unique fields, but MailUp only has 40.
That said, this limitation is somewhat limited in scope and most users are not affected by it. Here is why.
- It only applies when you need to uniquely map fields in different storefronts to different Lists in the same MailUp account. In many cases, this is not needed. Specifically, you do not need to uniquely map fields if the visitor to a certain store is likely never a visitor to another storefront. Think of different store views where each store view is a different language: it's unlikely that Mr. Smith would place an order on a store in German (different store view, connected to a different List in the same MailUp account).
- It only applies if you have to use just one MailUp account. However, nothing prohibits you from using multiple MailUp accounts (it's just a matter of cost, the cost is often limited).
Some additional limitations were recently removed.
- Lack of multi-store support was removed with version 2.3, which now supports multi-store implementations
- Lack of the newsletter subscription checkout during checkout was removed with v2.2, which adds this feature as a setting that can be turned on and off