Developers need to make a choice as to how they manage their data in conjunction with Maxemail before proceeding. This usually involves a decision between maintaining a single list within Maxemail, or creating a brand new list each time.
Our recommendation is where possible to maintain a single list in Maxemail and update this on a regular basis. This is because:
- Maxemail can handle unsubscribe preferences for you - creating a new list every time negates some of the useful functionality
- It is less work on your part, particularly if an email is to be triggered on the back of the import as the user can template the email with the single list attached rather than this being all handled by the integration
- It keeps the number of lists, and therefore clutter in the interface down. From experience, this reduces the likelihood of user error
If you are managing subscriptions outside Maxemail, then your subscription and unsubscribe processes should add the recipient to your primary list (or subscription-type list), or set the recipient's subscription flag to false on that list, respectively. Please see the list.insertRecipient and list.updateRecipient methods. You could even add unsubscribe complaints directly to the Global Unsubscribe List, so that it's impossible to send any emails to the recipient from your Customer Space.
Multiple lists
If you do decide to create a new list each time, use groups of folders to ensure clutter in the interface is minimised.
There is a limit on the number of lists allowed in a Customer Space. See list.insert.
Bulk import using the API
An integration between Maxemail and your system will make use of the API. To bulk import recipient data to Maxemail it must first be saved as a CSV file. This provides a consistent format to Maxemail, and you can test your output using the interface to Import a List.
To complete the same process on-demand using the API requires the following steps, for which you can see more information in each of the method descriptions: