GETTING STARTED GUIDE: How to set up a new connection?
ALL FEATURES EXPLAINED: All our features/functionality explained in detail - no app-specifics.
MailerLite is an email marketing service provider with focus on simplicity, excellent customer support and beautiful email designs. Create and share email campaigns, track results, manage subscribers and unsubscribers, and so much more.
Below you'll find detailed information, specifically for MailerLite integrations:
SUPPORTED MAILERLITE INTEGRATIONS
HOW TO AUTHORIZE MAILERLITE IN PIESYNC
We simply ask your login details and your permission. For MailerLite, we need your API Key. This key can be found in your account menu (top right) → 'Integrations' → 'Developer API'.
If you already authorized MailerLite account(s) in the past or in any other PieSync integration, you'll be able to the first part of the authorization and choose from your CONNECTED ACCOUNTS.
SUPPORTED FILTERS TO DETERMINE THE CONTACT SUBSET(S) TO SYNC WITH = IF
- IN/OUT OF GROUP
- ACTIVE/NOT ACTIVE
- CLICK/OPEN RATE
- FIELD VALUES (INCLUDING CUSTOM FIELDS)
- ALREADY EXISTING IN APP YOU SYNC WITH
SUPPORTED TRIGGERS = THEN
- ADD TO/REMOVE FROM GROUP
- UPDATING FIELD VALUES (INCLUDING CUSTOM FIELDS)
DEFAULT FIELD MAPPING
Depending on the other app you're syncing with, you'll see a number of standard MailerLite fields being mapped by default. For instance, in a connection with Office 365 Outlook.com, the default field mapping looks like this:
PieSync syncs the default name field(s) that come with the apps. Sometimes they have a different structure in both apps you connect. E.g. first and last names are separate in app A and joint in one field in app B. In the background, PieSync joins first and last names together from app A to B and separates them again from app B to A. Our algorithm is smart about which part it updates in app B.
CUSTOMIZABLE FIELD MAPPING
You can custom map your MailerLite Custom Fields and any additional standard fields that aren't included in the default mapping yet. Bear in mind a mapping between two fields can only exist if the types of fields are compatible and the particular compatibility will determine the direction of the mapping as well. More information on Customizable Field Mapping HERE.
*The availability of these features is app and connection dependent. If the feature box (screenshots above) is not there to tick, it's simply not possible. We need to be able to detect deletions on one side and at the same time be able to create add the tag 'PieSync Trash' on the other side.
Thanks to the feedback we have already received, we created a list of popular apps that we’re going to work on very soon. By voting them up in our pipeline, YOU decide which connectors we’ll release first. If you don’t see your app on the list or need any further help, drop us a line - firstname.lastname@example.org.
Don't forget to read our blog for the latest in productivity, apps, and technology!