MailerLite

Review campaign and automation reports with real sample activity. MailerLite describes opens, clicks and other measures, but those published descriptions do not establish the metrics or results your own account will produce.

If you need forms and landing pages, test how subscribers are captured and placed into the right groups. Confirm the number of active forms and pages permitted by your plan before replacing an existing signup flow.

Count active subscribers over the whole billing cycle. MailerLite says an address that was active during the cycle still counts even after deletion; exceeding paid limits can cause a prorated upgrade. Model list growth and sends together, rather than treating today’s contact total as the full cost.

Free-plan limits can pause sending campaigns or automation emails. Pilot the campaign editor, segmentation and automation triggers with representative data, then check plan headroom before relying on a live signup or follow-up sequence.

Before a time-sensitive MailerLite campaign, check for content or account review notices and keep evidence of subscriber consent ready. MailerLite says reviews can pause sending; a campaign scheduled during an account review returns to Drafts after reactivation, while a content review can require rescheduling if the send time passes. Recheck the campaign schedule before relying on its launch date.

For the new MailerLite, plan a subscriber export with an account administrator before a migration. Its CSV export includes only fields visible in the subscriber list at export time; select Groups and other needed fields, and choose the required subscriber status group. Campaign subscriber activity and automation activity use separate export paths. Check a representative CSV for expected fields, group names and selected records before relying on it. No complete account archive or real subscriber export was tested here.

Before a bulk subscriber import into the new MailerLite, review consent, the destination groups and field mapping, and any active workflows tied to them. MailerLite's import settings let you choose whether newly imported subscribers start group-linked automations; its trigger guide says CSV or TXT imports can also start a field-triggered workflow when that option is checked. Decide the intended audience and automation setting before finishing the import, then verify a small approved sample. No account import or message send was tested here.

When collecting subscribers in the new MailerLite, check the signup path before relying on double opt-in. New forms have it on by default, while API or integration signups require a separate Double opt-in for API and integrations setting. MailerLite uses one API confirmation email across integrations, so review its wording for every connected audience and the follow-up workflow. Verify each path with controlled addresses before accepting live subscribers.

Before using the new MailerLite to clean a list, plan how mistaken unsubscribes would be corrected. MailerLite says reactivating an unsubscribed recipient requires clear, documented permission, and recipients cannot be reactivated in bulk; for multiple accidental unsubscribes, contact Support. Test with a controlled address and reconcile the affected contacts and consent evidence before assuming a bulk cleanup can be reversed.

Before scheduling a migration campaign from a custom domain, have the authorized domain owner finish MailerLite's authentication and confirm the domain shows as authenticated in the account. The new-account trial allows first campaigns before authentication, so a successful trial send does not establish continuing sender readiness. Coordinate the exact DNS records shown in the account with existing mail settings; no DNS change was made for this review.

For a geographically spread list, set a test campaign's time-zone delivery at least 24 hours ahead. MailerLite says newly imported subscribers have no location data at first, so their first campaign uses the account's default time zone. Check that default and inspect a controlled sample before assuming every imported contact receives the intended local send time.

Before turning off a long-running automation to edit it, inspect subscribers waiting on delay steps. MailerLite says reactivation within seven days after a scheduled delay advances them immediately, while later reactivation marks them Failed. Plan how to review those records and avoid unintended duplicate follow-ups before resuming; no workflow or subscriber was changed here.

After the first send to a migrated list, inspect the campaign bounce report and active-subscriber count. MailerLite removes hard bounces from the active list and treats three consecutive soft bounces the same way. Investigate the cause and consent history before treating those addresses as a reachable audience; an import count alone does not show how many can receive mail.

Before relying on an A/B test to settle a campaign or workflow choice, check how its winner is chosen. For a campaign test sent to sample groups, MailerLite can choose the version with the higher click or open rate at the end of the test period and send it to the remaining recipients. Its entire-list option splits the audience equally and selects no winner automatically. Automation A/B tests on Comfort and Power require someone to choose a winner in the workflow editor; new subscribers then follow that version. Assign an owner to review the results and decide when the workflow test should end.

Before cleaning a current MailerLite subscriber list, distinguish Delete from Forget. Delete removes a subscriber from the account but retains their information if they later re-subscribe. Forget removes the subscriber and schedules complete deletion of their information within 30 days; MailerLite says forgotten subscribers cannot be restored and must wait 30 days before being re-added. For a mistaken bulk Delete, ask Support about restoration. Decide whether temporary list removal or data erasure is intended before choosing the action.

On a MailerLite website or landing page, choose the form by the intended follow-up. A Contact form forwards an inquiry to the account email and does not add the visitor to the subscriber list; MailerLite says it is not a valid way to collect email subscribers. A Signup form adds subscribers and can trigger associated automations, subject to the opt-in and workflow settings. In a fictional page review, check the chosen block, consent wording and linked workflow before promising a welcome sequence.

With double opt-in in the current MailerLite, an address stays Unconfirmed until the person confirms and cannot receive newsletters. MailerLite says you cannot resend the confirmation email or contact unconfirmed people through its platform to prompt confirmation; another signup through a double-opt-in form sends a new confirmation. Its manual Move to active route requires the person's permission, and the guide warns against activation without confirmation. Check the Unconfirmed list and test the form with a controlled address before relying on a welcome sequence.

MailerLite's current unsubscribe-page setting can remove a subscriber from all groups or let them choose specific groups to leave and keep receiving newsletters from the others. Its new builder asks for groups to opt out of, whereas the older builder asked which groups to stay subscribed to. MailerLite documents unsubscribe-page editing for Comfort and Power. The separate paid Preference Center can change group membership through configured rules. If consent or audience routing depends on a topic-specific opt-out, have authorized staff use a controlled address in two sample groups and inspect its resulting membership and campaign targeting. Confirm the account's plan and whether it uses the new MailerLite or Legacy (Classic) before promising the behavior.

Before using a Joins a group automation in the current MailerLite as a repeat follow-up, check its re-entry setting. With Allow subscribers re-enter automation on, a subscriber can trigger again after leaving and rejoining the group, at most once every 24 hours; with it off, the workflow runs only once for that subscriber. Someone still in the group cannot rejoin it to retrigger. A separate exit option can stop an in-progress run when the person leaves all trigger groups or joins an excluded group. Map a fictional, permissioned subscriber through first join, exit and later rejoin, then review the expected message count and current account settings before enabling a live sequence. No real subscriber or email was used.