One plugin. Records and consent, on your own site.
Installs one line of code to activate on your WordPress site, beside the menu embed you already run. Every consented visitor arrives as one record, with its receipt.
The scan shows whether your site already runs WordPress plugin.

How it works
Inside WordPress plugin, where you already work.
A GreenLeadSource plugin on your WordPress site stores each Verified Customer Record and its consent state in your site's own database, on the domain you already own. No third-party dashboard.
Native WordPress plugin, installed on your site.
- 1A visitor says yes on your site.
- 2GreenLeadSource verifies the record and writes the receipt.
- 3The record lands in the plugin's own table in your WordPress database, on your domain.
What we send, and how.
Consent receipts travel as a tag, property, or field. No destination has a receipt object of its own, and every field is one the visitor agreed to.
- What it does
- Installs one line of code to activate on your WordPress site, beside the menu embed you already run.
- Website
- wordpress.org
- How it connects
- Plugin · The plugin's own table in your WordPress database, on your domain
- What we send
- Enriched Customer Contact, with its consent receipt

Late bulletin
Every day you wait, visitors leave as strangers. Scan your site today.
Ten seconds. Your Customer Reach Score, what fires before anyone says yes, whether your age gate is the only question you ask, and what your privacy policy leaves out. Nothing installed, nobody contacted.
- A real browser load of your homepage, screenshot included
- Every tag that fires before a visitor can answer
- Your privacy policy, lined up against what the site does
- Modeled traffic and what an ask-first step would return