Uses a Site Key
An administrator enters the Site Key for an already configured Lean site. The connector does not create or link accounts.
The Lean Cookie Consent plugin is a focused WordPress connector. You configure one Site Key, while banner copy, categories, preferences and consent evidence are managed in Lean Cookie Consent.
An administrator enters the Site Key for an already configured Lean site. The connector does not create or link accounts.
The plugin enqueues its bundled runtime on the frontend. It retrieves public, site-specific configuration data from Lean.
Banner layout, copy, categories, services and policy links are configured from the Lean dashboard rather than in multiple WordPress options.
The official plugin describes a bundled local runtime and public configuration API. It does not offer arbitrary JavaScript, HTML or CSS injection fields. A valid Site Key is required for live Lean configuration and consent recording.
Consent tooling is only one part of a compliant implementation. Theme code, plugins and tag managers must also be configured so that non-essential services respect the chosen consent flow.
Read the setup, policy, scanner and reporting workflow.
Open the usage guideReview the benchmark methodology and configuration caveats before making performance claims.
Open the benchmarkSee how a site-based dashboard supports repeated client handoffs.
For agenciesNo. Create an account and site in Lean first, then enter its Site Key in WordPress.
No. It uses a bundled local runtime and public configuration data; it has no arbitrary JavaScript, HTML or CSS injection fields.
Each Lean site has its own Site Key and configuration. Agencies can manage several configured sites from the Lean workflow.