# MailerLite Connect MailerLite as a data source: the API key it needs, how it imports your subscribers once and keeps them current in real time through webhooks, how MailerLite groups become lists you can segment on, and how its subscription status maps to consent. **Language:** en **Audience:** platform **TLDR:** Native connector with an API key: paste a MailerLite token and it imports your subscribers, groups and custom fields. Contacts are imported once on connect and stay current in real time through webhooks — new sign-ups, unsubscribes, profile changes and group moves — with a manual reimport as the recovery path. **Translation key:** platform.data-sources.connectors.mailerlite **Search keywords:** MailerLite, Mailerlite, API key, token, subscribers, groups, segments, email marketing, contacts, events, webhooks, connect MailerLite, MailerLite integration, MailerLite consent, SMS **Related pages:** /platform/es/data-sources/connectors/mailerlite, /platform/en/data-sources/connectors, /platform/en/data-sources/connectors/mailchimp, /platform/en/data-sources/managing, /platform/en/consent **Docs index (every page):** https://docs.instasent.com/llms.txt **This zone's index:** https://docs.instasent.com/platform/en/llms.txt **This page:** https://docs.instasent.com/platform/en/data-sources/connectors/mailerlite/ (HTML) · https://docs.instasent.com/platform/en/data-sources/connectors/mailerlite.md (Markdown) **Other language (es):** https://docs.instasent.com/platform/es/data-sources/connectors/mailerlite.md MailerLite is a native connector for your email-marketing audience. Once connected, it imports your MailerLite subscribers, groups and custom fields into Instasent and keeps them current in real time, so your email audience can drive SMS campaigns and automations alongside the rest of your audience. ## How to connect MailerLite connects with an **[API key](/platform/en/data-sources/connectors#api-key)**: you generate a token in MailerLite first and paste it into Instasent. There is a single key to copy. > **Warning**: Generate the key with a user that will not be removed — the key stops working if that > user is deleted. MailerLite shows the token only once, so copy it right away. > **MailerLite Classic accounts** (created before March 2022) are not supported. #### 1. Generate the API key in MailerLite In MailerLite, go to **Integrations > MailerLite API > Generate new token** and copy the token it creates. #### 2. Add the data source In **Data sources**, select **Add data source** and choose **MailerLite** from the Integrations section. #### 3. Enter the key and connect On the **Connect** step, fill in the connection name and paste your **API key**, then connect. #### 4. Initial import The connector imports your subscribers once, then keeps them current through webhooks. ![The Connect MailerLite page with the connector description, the data it syncs and the contact fields it maps](/platform/en/data-sources/images/mailerlite--1-connect.png) *The MailerLite connector page: what it brings into Instasent and the contact fields it maps, with Connect MailerLite to start.* After connecting, the wizard continues through **Mapping**, **Merge** and **Tags**, the same steps as a CSV import. ## What it syncs - **Subscribers** — your MailerLite contacts, with their custom fields. - **Groups** — MailerLite group memberships become **client lists you can segment on**. - **Events** — subscriber activity: new sign-ups, unsubscribes, profile changes, group moves and deletions. The direction is one-way, **from MailerLite into Instasent**, and contacts unify by email and phone — see [unification](/platform/en/data-sources/managing#how-unification-works). ### How it stays current MailerLite works best with accounts of up to **200,000 subscribers** and **no more than 10 groups**; larger accounts still import fine, but each group is read separately, so it takes longer. - **Subscribers are imported once**, when you connect. - From then on they stay current **in real time through webhooks** — sign-ups, unsubscribes, profile changes, group moves and deletions arrive as they happen, and can **trigger your automations**. - The **group, segment and custom-field catalogue** refreshes periodically on its own. - There is **no periodic re-import of contacts**. If your receiver was unreachable and webhooks were missed, a **manual full re-import** is the way to reconcile — run it from the data source's sync options. ## Field mapping MailerLite subscriber fields map to the matching Instasent attributes — email to `_email`, phone to `_phone_mobile`, and so on — and events arrive with their parameters. You confirm the mapping on setup; see [field mapping](/platform/en/data-sources/managing#field-mapping). > **Warning**: MailerLite phone numbers are **free text and optional**: subscribers without a valid > mobile number cannot be reached by SMS. ## Consent mapping MailerLite imports the **real email consent** of each subscriber. Its subscription status maps to Instasent's marketing-preference attribute (`_accepts_marketing_*`) following the consent golden rule: {/* VERIFY: confirm the exact MailerLite status → Instasent value mapping (active / unsubscribed / unconfirmed) against the connector's actual behaviour before treating the table as definitive. */} | MailerLite status | Instasent value | Meaning | | ----------------------- | --------------- | --------------------------- | | Active (subscribed) | `true` | Accepted marketing | | Unconfirmed / no status | `null` | No preference | | Unsubscribed | `false` | Actively declined marketing | Only an **active opt-out** (unsubscribed) in MailerLite becomes `false`. A subscriber who never confirmed maps to **no preference** (`null`), never to `false`. For what these values mean for who receives a campaign, see [Consent](/platform/en/consent/marketing-preference-vs-suppression). --- This is one page of the Instasent documentation. For the complete machine-readable index of every guide and API reference, fetch https://docs.instasent.com/llms.txt — start there for full context.