WordPress plugin intelligence profile

Keyset Cart Lead Capture

Capture guest emails at Add to Cart, before checkout. Consent-first, unlimited and free, under 8 KB. Leads stay in your own database.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version0.1.3
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 6.3 · PHP 7.4
Directory statusactive
Last directory update9 Oct 202624d ago
Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Keyset Cart Lead Capture version 0.1.3 as active, updated 24d ago and tested up to WordPress 7.1.

Overview

About this plugin

Shoppers add to cart and vanish before checkout. Keyset catches their email at the moment of intent — consent-first and under 8 KB. Free, with no lead cap, no forced branding, and nothing locked.

Most abandoned cart plugins don’t capture abandoned carts. They capture abandoned checkouts — they only fire once a shopper has already reached the checkout page and started filling it in. By then most guests are long gone.

Keyset meets the shopper earlier, at Add to Cart, where intent is highest and nothing else is listening.

Many capture plugins grab emails through silent keystroke logging. Keyset refuses to. Nothing is captured without a clear, unchecked-by-default yes — and every lead carries a consent record you can stand behind.

Abandoned cart vs. abandoned checkout — why it matters

Roughly 70% of carts never become orders. The plugins that promise to “recover abandoned carts” almost all wait for the checkout page to load before they capture anything — so they only ever see the shoppers who were already going to check out. Keyset fires the moment a guest clicks Add to Cart: peak purchase intent, and the point where hesitation, distraction, and second-guessing quietly cost you the sale.

It shows a calm prompt, fires only on an explicit opt-in, stores every lead in your own store’s database, and hands it to the email tool you already use. Behavioral research on cart abandonment and digital nudging points the same way: meet the shopper who has signalled intent earlier, and you keep more of it — with consent, never a dark pattern.

What it does

  • Consent-first, always. An explicit, unchecked-by-default opt-in — no silent capture, no pre-ticked boxes. Every lead comes with a consent record: the exact text shown, a timestamp, and the page.
  • Unlimited, forever. No lead cap and no trial. Capture, consent records, CSV export and deletion are free and uncapped, forever.
  • Your leads, your database. Leads are stored locally in your own WooCommerce install. We host nothing. Export to CSV anytime.
  • Unbranded by default. The prompt carries no logo and no “powered by” line. If you want to help other store owners find Keyset, you can switch on a small glyph. It’s off unless you turn it on, and it never links anywhere.
  • Faster checkout. Captured name and email prefill the checkout contact fields — a genuine benefit for the shopper, not just for you. They can still edit before they buy.
  • Lightweight by design. Loads only on product and shop pages, under 8 KB, no jQuery, no bloat. It answers the one complaint every merchant has about capture plugins: they slow the whole site down.
  • Block-checkout compatible. Works with the modern WooCommerce block checkout and the classic one, from day one — no console errors, no layout breakage.
  • No lock-in. Hands leads to the email tool you already use — Keyset never sends on your behalf. Delete a lead, or all of them, whenever you like.

How it works

  • You finish the one-minute setup. Review the consent sentence and your privacy-policy link, then click “Turn on capture.” Shoppers see nothing until you do.
  • A guest adds to cart. A shopper browses, clicks Add to Cart, and a calm prompt offers to save their cart — inline, dismissible, never blocking the buy.
  • They opt in, with consent. They leave an email (name optional) and tick a clear consent box. The lead is saved to your own database with a full consent record.
  • Checkout gets faster. Their details prefill at checkout, so buying is quicker — and if they leave, you hold a consented lead you actually own.

Honest by default

” We provide consent-first capture — a clear opt-in, a real consent trail, and full control over deletion — and we say exactly that. Trust is a feature, not a footnote.

Free, with no catch

Most free plugins come with a catch. This one doesn’t: unlimited captures, no watermark, nothing held back. Everything in the free plugin works for everyone, and capture, consent records, CSV export and deletion stay free forever.

Missing something? Tell us from the plugin’s Help shape Keyset Pro form. We read every request, reply personally, and let you know when the thing you asked for ships.

What we build next comes from what you ask for.

External services

This plugin connects to one external service, and only when the site admin chooses to use it.

Feature-request form (“Help shape Keyset Pro”). build. Nothing is sent automatically, and no shopper or lead data is ever sent.

  • Service provider: Keyset — https://kinto.build
  • Privacy policy: https://kinto.build/privacy

Source Code

The JavaScript and CSS in the build/ folder are compiled. Their full, human-readable source ships with the plugin in the src/ folder:

  • src/storefront/ — the “save your cart?” prompt shown to shoppers (TypeScript, compiled to build/storefront.js and build/storefront.css ).
  • src/admin/ — the plugin admin screens (TypeScript + React, compiled to build/admin.js and build/admin.css ).

The build uses the standard WordPress toolchain, @wordpress/scripts (webpack). json ) is included in the plugin. To rebuild the assets:

  • Install Node.js 22 or later.
  • In the plugin folder, run npm ci to install the exact build dependencies.
  • Run npm run build. The compiled files are written to build/.

Use npm run start to rebuild automatically while you edit files in src/.

The two bundled font files (Hanken Grotesk and JetBrains Mono, both under the SIL Open Font License) are emitted unchanged by webpack from src/ into build/fonts/.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • abandoned cart
  • email capture
  • guest checkout
  • consent
  • woocommerce
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 6.3 · PHP 7.4
Update activity9 Oct 202624d ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.