Viewing & Exporting Your Signups

Every time a customer signs up on a MailerLite-powered coming soon product, the plugin saves a record in a custom database table called wp_sscs_signups. This is your local copy of the waitlist — independent of MailerLite — and it’s where the referral relationships are tracked.

Heads up: there is currently no admin screen for browsing signups inside WordPress. Until one is added, you read this data with WP-CLI, phpMyAdmin, or any database tool. This article shows the common queries.

What’s stored

The wp_sscs_signups table has one row per unique email address:

Column	Description
id	Auto-incrementing row id.
email	The subscriber’s email address (unique — one row per email).
mailerlite_id	The subscriber’s MailerLite ID (blank if MailerLite wasn’t configured).
referrer_id	The MailerLite ID of the person whose share link referred this signup, if any.
wp_user_id	The WordPress user ID, if the customer was logged in when they signed up.
created_at	Timestamp of the signup.

A few things to know:

• Table prefix. Your install may use a prefix other than wp_ (e.g. wp_abc123_). Adjust the table name in the queries below to match.
• MailerLite only. Products set to use Super Speedy Emails (SSE) do not write to this table — those signups live in SSE’s own storage. This table only reflects MailerLite-powered products.
• One row per email. A repeat signup with the same address does not create a duplicate; the existing row is kept.

Viewing signups with WP-CLI

If you have SSH/WP-CLI access, these are the quickest options.

List the most recent signups:

wp db query "SELECT email, created_at, referrer_id FROM wp_sscs_signups ORDER BY created_at DESC LIMIT 50"

Count total signups:

wp db query "SELECT COUNT(*) AS total FROM wp_sscs_signups"

See who referred the most signups (your top sharers):

wp db query "SELECT referrer_id, COUNT(*) AS referrals FROM wp_sscs_signups WHERE referrer_id IS NOT NULL AND referrer_id <> '' GROUP BY referrer_id ORDER BY referrals DESC LIMIT 20"

The referrer_id is a MailerLite subscriber ID. To turn it into a name/email, look it up in MailerLite, or match it against the mailerlite_id column of this same table (the referrer is usually also a signup):

wp db query "SELECT r.email AS referrer, COUNT(*) AS referrals
  FROM wp_sscs_signups s
  JOIN wp_sscs_signups r ON r.mailerlite_id = s.referrer_id
  WHERE s.referrer_id IS NOT NULL AND s.referrer_id <> ''
  GROUP BY r.email ORDER BY referrals DESC LIMIT 20"

Exporting to CSV

Export the whole table to a CSV file (WP-CLI):

wp db query "SELECT email, mailerlite_id, referrer_id, wp_user_id, created_at FROM wp_sscs_signups ORDER BY created_at" --skip-column-names > signups.csv

For a CSV with a header row, or to filter by date range, adjust the SELECT and add a WHERE created_at >= '2026-01-01' clause as needed.

Using phpMyAdmin: open your database, select the wp_sscs_signups table, click the Export tab, choose CSV, and download. This is the easiest route if you don’t have command-line access — your host’s control panel almost always includes phpMyAdmin.

Where the “real” list lives

Remember that wp_sscs_signups is a local ledger for your reference and for referral tracking. The marketing list you’ll actually email from is:

• MailerLite — for MailerLite-powered products. Send your launch campaign from the MailerLite group you configured on the product.
• Super Speedy Emails — for SSE-powered products. Manage and email those subscribers inside the SSE plugin.

The local table is most useful for auditing signups, spotting your best referrers, and reconciling numbers against your email provider.

Deleting a person’s data

If someone asks to be removed (see Privacy & Data Handling), delete their row here and remove them from your email provider:

wp db query "DELETE FROM wp_sscs_signups WHERE email = 'person@example.com'"

Then delete the subscriber in MailerLite (or SSE) as well — removing the local row does not touch your provider.

Related

• Referral & Sharing System — how referrer_id gets populated.
• Privacy & Data Handling — what’s stored, where it goes, and deletion requests.
• Email Providers — MailerLite vs SSE and where each one stores data.