✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for MailerLite Pro: forms, groups & sync state as tables

MailerLite Pro keeps API tokens, form-to-group mappings, automation triggers and a sync-log option in wp_options and wp_postmeta. SleekView gives that scattered local state a real audit table that legal, marketing and engineering can each scan.

♾️ Lifetime License available

SleekView table view for MailerLite Pro for WordPress

MailerLite Pro is a SaaS bridge with WordPress state

MailerLite Pro is the premium WordPress plugin for MailerLite. Subscribers, campaigns and automations live in MailerLite's SaaS. The plugin's WP-side footprint is meaningful though: the API token, connected account ID, capture-script enable flag and sync timestamps live in wp_options as a serialized array. Per-form group mappings and automation-trigger configs sit in wp_postmeta when a Gravity, Fluent, Contact Form 7 or WPForms integration is enabled.

The default Pro plugin UI handles each surface separately. Form mappings, automation triggers and sync state each have their own screen. There is no list view of every bridge across the site, no filter for forms whose target group was archived in MailerLite, and no diff between staging and production capture configs. Multisite operators have no portfolio view, so confirming every subsite is wired the same way means logging into each one in turn.

SleekView reads each storage path directly and renders MailerLite Pro as one workspace. Capture rows at the top, form-bridge rows in the middle, automation-trigger rows below, with consent text, payload shape and a status pill on every row. Edits route through the plugin's options API where supported so MailerLite's hooks and dependent integrations continue to fire as expected.

Workflow

MailerLite Pro options and postmeta as a workspace

1

Pick the storage paths

Point SleekView at the MailerLite Pro settings option and the _ml_* keys in wp_postmeta. Settings, form bridges and automation triggers render as one joined table.
2

Compose audit columns

Pivot the settings blob into named columns. Add per-form group ID, per-trigger automation ID, payload shape and consent text from postmeta. Group rows by surface type.
3

Save the integration views

Save filters for stale group targets, missing consent text, capture-script disabled on key pages, custom payloads without a matching MailerLite schema. Each becomes a reusable audit.
4

Edit inline or bulk-update

Change a form's group ID, repoint a trigger to a new automation, or update consent copy across every form in one bulk edit. Hooks fire through the options API where supported.

Sample columns

A typical MailerLite Pro forms & sync view

Settings live in wp_options. Per-form group mappings sit in wp_postmeta.
Source: wp_options + wp_postmeta (MailerLite Pro settings, sync state, form group mappings)
Surface Form/trigger MailerLite target Consent text Last sync Status
Capture script (global) site-wide Default Apr 24 Loading
Form bridge Newsletter group:newsletter Default Apr 23 Synced
Automation trigger Trial signup automation:onboarding Custom Apr 22 Firing
Form bridge Old promo group:archived Default Feb 11 Group missing

Comparison

Default MailerLite Pro plugin UI vs SleekView

Default MailerLite Pro plugin UI

  • Form, automation and sync surfaces each have their own screen
  • No filter for forms whose group_id was archived in MailerLite
  • Sync timestamps aren't joined to the form they relate to
  • Consent-string overrides aren't auditable in one column
  • Multisite operators must log into every subsite to compare configs

SleekView

  • Forms, automations and sync state in one joined table
  • Filter by archived group_id against MailerLite's active set
  • Per-form last-sync timestamp as a sortable column
  • Inline-edit consent text and target group IDs
  • Multisite roll-up across every client in the network

Features

What SleekView gives you for MailerLite Pro for WordPress

Unified bridge audit

Forms, automation triggers and capture-script settings live as one row-per-surface view. Sort, filter and group by status so the integration health check is one screen instead of three.

Group-target audit

Every group_id a WP surface posts to, filterable against MailerLite's active group set. Archived targets surface as red rows so cleanup is one bulk edit.

Consent-text governance

Custom consent strings drift as legal copy gets revised. SleekView surfaces every override in one column so legal can catch stale wording across forms and automations.

Audience

Who uses SleekView for MailerLite Pro

Lifecycle marketers

Inventory which WP surfaces feed which MailerLite groups and automations. The mapping table is the bridge between marketing operations and the SaaS-side lifecycle.

Privacy & legal

Audit consent strings and capture flags across forms and automation triggers in one column. Legal reads the WP-side state without needing MailerLite dashboard access.

Agencies

Multisite roll-up gives a portfolio-wide audit of every client's MailerLite Pro wiring on one screen. Kickoff and renewal reviews use the same table.

The bigger picture

Why MailerLite Pro WP-state audits earn their keep

Most SaaS-first WordPress integrations are intentionally narrow on the WP side because the SaaS is supposed to be the source of truth. That model holds until the WP-side state quietly drifts from the SaaS-side state without anyone noticing. Groups get archived in MailerLite and mapped forms keep posting into the void.

Consent copy gets rewritten in the SaaS but the WP-side override carries the old wording. Capture scripts get disabled on a page during a launch and never re-enabled. Sync timestamps stop advancing after a token rotates without anyone noticing because the timestamp lives in a serialized option row.

None of these failures surface in the default plugin UI because the UI is built around editing one thing at a time. SleekView's contribution is structural: every storage path becomes a column on one table. Once the audit table exists, drift becomes a filter and fixes become bulk edits.

For lifecycle teams running MailerLite Pro on production WordPress sites, the table is the difference between catching the archived-group misroute the same week it happens and finding out three months later when a quarterly report doesn't match.

Questions

Common questions about SleekView for MailerLite Pro for WordPress

No. Subscribers and campaign data stay in MailerLite. SleekView surfaces only the WP-side settings, form mappings, automation-trigger configs and sync state the plugin stores locally in wp_options and wp_postmeta.

 

In wp_options as a serialized array. The capture-script enable flag, API token, connected account ID, and sync timestamps are all there. SleekView pivots the array into named columns.

 

Per-form integrations write to wp_postmeta on the form's post record, with keys like _ml_group_id and _ml_consent_text. SleekView joins the form's title with its meta into one row per bridge.

 

Yes. SleekView writes through the plugin's options API where supported so existing hooks fire. Direct postmeta writes are available for bulk migrations after a group rename in MailerLite.

 

Yes. MailerLite Pro lets each trigger send a custom payload tied to an automation. SleekView reads the payload definition from wp_postmeta and renders it as a label, with the target automation ID as a sortable column.

 

Yes. Joins use indexed wp_postmeta queries and a single wp_options read, so even sites with hundreds of forms render in a single paginated query.

 

Yes. SleekView reads each subsite's wp_{blog_id}_options and wp_{blog_id}_postmeta and renders a network roll-up so agencies see every client's MailerLite Pro state in one screen.

 

Contacts live in MailerLite so subject-access requests run through MailerLite's tooling. The WP-side sync log is supporting evidence that shows when and from which form a contact was posted, which is useful for the export record.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView