The following table shows the most common combinations for the parameters that manage subscription status of imported recipients that are already present on MailUp
|Action required on already existing recipients||ConfirmEmail||AsOptout||AsPending||ForceOptIn|| |
|No changes on subscription status||False||False||False||False||Default case|
|Pending become Subscribed ||False||False||True||FalseBad || practice, please take care with itIt's a bad practice to force subscription of pending recipients at import time, the recommended |
practice with double optin is that you import as pending and you let MailUp do this status change
when recipient actually clicks on the confirmation link.
|Unsubscribed become Subscribed||False||False||False||True||Except for recipients that were unsubscribed due to hard bounce |
or complaints feedback loop
|Subscribed become Pending||True||False||False||False||With this configuration the confirmation email is sent to both |
previously subscribed and previously pending
|Unsubscribed become Pending||True||False||Any||True||Except for recipients that were unsubscribed due to hard bounce |
or complaints feedback loop
Despite of its name, "AsPending" value is ignored here.
|Subscribed become Unsubscribed||False||True||False||False|| |
|Pending become Unsubscribed||False||True||True||False|| |
Method call fails when another import process is running. You can use GetProcessDetails method to check if a previously started process is still running; while an alternative solution consist of periodically retry the method call until it returns
Method response contains either a global ReturnCode or a specific ReturnCode for each import process that has been started by this method. Call is successful only when all ReturnCodes are equal to "0"
There is not a known size limit for xmlDoc field: it has been successfully tested with 1.2 million characters (in this case return value is quite immediate but the whole import process could take several minutes and other import requests will be denied during this period)
When using cloud services it can happen that your application must respect a size limit in API calls that is lower than the size of the XML that you would pass as xmlDoc parameter. In this case you can split your import data, call several times NewImportProccess
NewImportProcess with smaller recipient lists and then use StartImportProcesses (with empty xmlDoc parameter) to sequentially start all previously created import processes. This behavior requires MailUp 8.2.1 or higher. Please note that, when combining one or more calls to NewImportProcess and a final call to StartImportProcesses , the parameters of StartImportProcesses do not overwrite the import settings that were specified by each NewImportProcess request
With ConfirmEmail=true, MailUp automatically selects the confirmation request message (you can customize it on Settings > List Settings > Notifications > Confirmation request) and it creates a queue of recipients that will receive that message. Please note that queue creation takes a while (even a couple of minutes if you have 1M recipients to be imported and notified) and queued message is made "ready for immediate sending" but it IS NOT automatically sent to the recipients. To send a queued message you can use StartDelivery method. You could also use GetNewsletterQueues before calling StartDelivery in order to double check if queuing in "ImmediateSendingQueue" is completed.
Lists and Groups
You must specify either
listsGUIDs parameters. If you specify both fields, then the number of items in each parameter must match, and you must use semicolons to delineate empty values. We've provided examples below to help with understanding how to work with these parameters.