Flexa Unsubscribe

Flexa Unsubscribe adds a complete unsubscribe workflow to every email WordPress sends, with a fully-branded admin UI for managing opt-outs, analytics, and the public unsubscribe page.

• Auto-appends a secure unsubscribe button to outgoing single-recipient emails. Tokens are HMAC-signed using the AUTH_KEY in wp-config.php, so no database lookup is needed to verify a link.
• Blocks outbound mail to unsubscribed addresses before it reaches the mail server. Blocked attempts are logged to a dedicated audit table.
• Honours an exclude-keywords list (default: Order, Password, Invoice) so transactional mail never gets an unsubscribe link and never gets blocked.
• Re-subscribe URL is supported as a first-class action — the plugin can tell opt-outs from opt-backs.
• Customisable public page — every color, font, and string on the unsubscribe/re-subscribe templates is editable from the admin with a live preview.

Admin UI

Starting with v3.0.0 the admin is a React single-page application with seven screens:

• Dashboard — stats cards + bar chart of unsubscribes over time + pie chart of top reasons.
• Unsubscribes / Blocked emails / Re-subscribed — paginated tables with sorting, per-row delete, and CSV export.
• Reasons — manage the dropdown options shown on the public unsubscribe form; click-to-edit, ↑/↓ reorder.
• Settings — enable/disable auto-append + blocking, tune the exclude-keywords list.
• Appearance — 19 tokens (colors, typography, copy) across three tabs with a live preview panel.

All screens are powered by a REST API under /wp-json/flexa-unsubscribe/v1/, so external integrations can plug in too.

Source code for compiled JavaScript and CSS

The plugin ships with minified/compiled JavaScript and CSS in assets/dist/. The human-readable source code for these assets is publicly available and maintained at:

https://github.com/flexatech/flexa-unsubscribe

Source lives in the apps/admin (admin UI) and apps/frontend (product page UI) directories. Build tools used: pnpm, Vite, React, TypeScript. To build from source: clone the repository, run pnpm install from the plugin root, then build the admin and frontend apps (see the repository README for exact commands). This allows the code to be reviewed, studied, and forked.