M2Labs Leads

By Martin Micevski

0+ active installationsVersion 1.2.6

Store contact form submissions in a local WordPress inbox with lead statuses, internal notes and source details.

Description

M2Labs Leads stores submissions from connected contact forms in your WordPress database. Administrators can review enquiries, update lead statuses and add internal notes from the Leads menu.

Capture runs through the connected form plugin’s submission hooks. A saved lead does not confirm email delivery, and the plugin does not repair SMTP settings or replace your form builder.

Features

  • Local database storage for captured submissions.
  • Lead statuses: New, In Progress, Contacted, Won and Lost.
  • Internal notes and individual lead deletion.
  • Submission date, source, form details and submitted fields.
  • Automatic identification of common name, email, phone and message fields.
  • Page/referrer URLs and UTM source, medium and campaign values when available.
  • Dashboard status counts and a new-lead menu badge.
  • Status filtering; the inbox displays up to the latest 500 matching leads.
  • Generic PHP capture API for custom integrations.

Included form adapters

Adapters are included for Contact Form 7, Elementor Pro Forms, WPForms, Gravity Forms and Ninja Forms. Only the form plugins installed and active on your site are used. These plugins are separate products and are not bundled with M2Labs Leads.

Test a submission from each form after activation. Field mappings, compound fields, arrays and file-upload fields can vary between builders and versions. This plugin does not copy uploaded files into its own attachment storage. Installation detection is not an end-to-end compatibility test.

Privacy and data storage

Captured information is stored in the current site’s WordPress database table using the suffix mxyz_leads. Depending on your forms, records may include names, email addresses, telephone numbers, messages, submitted field values, URLs, campaign values and administrator notes.

M2Labs Leads does not send captured leads to M2Labs or an external service and does not load remote assets. The branded website link opens https://ranklens.si/ only when clicked. Your form builder and other plugins may use external services separately.

Access to the inbox requires the manage_options capability. Configure forms to avoid collecting passwords, payment details or unnecessary sensitive information, and describe submission storage in your site’s privacy notice.

There is no automatic retention schedule and no integration with WordPress personal-data export or erasure tools in this release. Administrators can delete individual leads in the inbox. Deactivation or deletion of the plugin does not automatically remove the leads table; site owners must manage retained database records and backups separately.

Multisite

This release uses a site-specific table and dashboard. It does not provide a network-wide inbox or automatic table creation across all sites during network activation. Activate individually on each site that will capture leads. New sites require individual activation as well.

Developer API

Call the following after plugins have loaded, for example from a validated custom form handler:

if ( class_exists( 'MXYZ_Leads' ) ) {
    MXYZ_Leads::capture( array(
        'source'    => 'custom-form',
        'form_id'   => 'contact',
        'form_name' => 'Contact form',
        'name'      => 'Example Visitor',
        'email'     => 'visitor@example.com',
        'message'   => 'Example enquiry',
        'fields'    => array( 'subject' => 'Product question' ),
    ) );
}

The calling integration is responsible for validating its submission, authorization or nonce checks where applicable, consent requirements and spam prevention. The mxyz_leads_created action receives the inserted record ID and row data after the insertion attempt; integrations should verify the result before relying on it.

Developed by M2Labs: https://ranklens.si/
M2Labs Leads is an independent plugin and is not affiliated with the form-builder vendors listed above.

Installation

  1. Upload the plugin ZIP using Plugins > Add New > Upload Plugin, or upload its folder to wp-content/plugins/.
  2. Activate M2Labs Leads on the site where it will be used.
  3. Install and activate a supported form builder, or connect your own validated handler using the PHP API.
  4. Open Leads > Integrations to inspect installed form-plugin detection.
  5. Submit a test enquiry through your public form.
  6. Open Leads to confirm the record, field mapping and available source details.
  7. Configure your form notifications separately and verify email delivery independently.

When upgrading an earlier privately distributed release, replace the existing plugin rather than running parallel copies. Keep a database backup before upgrading.

FAQ

Does this plugin create contact forms?

No. Use a supported form builder or a custom integration.

Will a lead be saved if email fails?

Capture is separate from the email transport and uses the form builder’s submission hooks. Whether a record is created depends on the submission reaching that hook. Rejected or interrupted submissions may not be captured. A saved record does not prove email delivery.

Does the plugin track email delivery?

No. Stored mail-status values are adapter metadata such as pending or unknown, not a verified delivery receipt.

Why are some contact details blank?

Automatic mapping recognizes common field names. Custom labels and compound fields may not map to the summary columns. Check All submitted fields in the lead detail and test your form’s mapping.

Does it work without a supported form plugin?

The inbox is available, but new records require a connected form adapter or the PHP capture API.

Are my leads sent to M2Labs?

No. The plugin stores captured records locally in your WordPress database.

Is a paid M2Labs account required?

No account, subscription or license key is required by this release. Separate form builders may have their own licensing requirements.

What happens to data when I remove the plugin?

The database table is retained. Delete individual leads through the inbox or arrange database cleanup separately if permanent removal is required. Backups may retain copies.

Can all sites in a multisite network share one inbox?

No. This release provides a separate inbox per site and requires individual site activation.

Screenshots

Changelog

1.2.6

  • Added Tested up to 7.1 from the site owner’s latest-stable test environment confirmation.
  • Aligned Text Domain with the M2Labs directory slug.

1.2.5

  • Escape lead IDs, option values and labels, and sanitize rendered header HTML.
  • Align Text Domain with the requested m2labs-leads directory slug.

1.2.4

  • Added a complete directory-format readme with installation, feature, integration, privacy, multisite and developer documentation.
  • Added GPL license and minimum platform requirement metadata.
  • Removed the private Update URI header for directory distribution.
  • Retained existing data identifiers and the transparent versioned logo.

1.2.3

  • Added a uniquely named transparent logo with a versioned URL and explicit transparent image background.

1.2.2

  • Replaced the opaque brand image with a transparent M2Labs logo.

1.2.1

  • Updated branding, plugin name, author and website links to M2Labs.

1.2.0

  • Existing private release used as the basis for the M2Labs rebranding.