=== Leeeds Website Signals ===
Contributors: leeeds
Tags: b2b, intent, analytics, consent, crm
Requires at least: 6.0
Tested up to: 6.8
Requires PHP: 7.4
Stable tag: 1.0.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Consent-first company website signals connected to Leeeds sequences.

== Description ==

Leeeds Website Signals connects a WordPress website to a Leeeds client account with a short-lived, single-use pairing code.

The plugin:

* waits for marketing consent before loading the Leeeds tracker;
* supports WP Consent API, Cookiebot, Complianz, CookieYes and a custom `leeeds:consent` event;
* fails closed when it cannot recognize a consent signal;
* sends page path, title, referrer and UTM parameters for company-level intent aggregation;
* never exposes the private WordPress connection token to site visitors;
* reports connection health back to Leeeds once per day.

Leeeds can recognize a company after a verified human click on a Leeeds email creates a first-party relationship. Matching happens inside Leeeds without an external IP-to-Company service. Unrelated anonymous visits stay anonymous, and the tracker does not identify a named person.

== Installation ==

1. In Leeeds, open Website signals and enable measurement for the website domain.
2. Download the plugin ZIP and upload it in WordPress under Plugins > Add New > Upload Plugin.
3. Activate the plugin.
4. In Leeeds, create a WordPress pairing code for the exact website domain.
5. In WordPress, open Settings > Leeeds Signals and enter the code within 15 minutes.
6. Verify the connection and your consent banner before enabling a sequence.

== Privacy ==

After marketing consent, the plugin can send the visited path, page title, referrer, UTM parameters, a privacy-preserving network hash and browser user agent to the connected Leeeds service. Leeeds uses those signals to aggregate company-level interest and may start a configured B2B follow-up workflow.

The plugin does not load the Leeeds tracker before marketing consent. It does not set a Leeeds visitor cookie in version 1.0.0 and does not identify a named visitor by itself.

The WordPress administrator should review the suggested text in Settings > Privacy, document the lawful basis and recipients, and configure a compatible consent platform. Raw website events are retained according to the connected Leeeds workspace policy (90 days by default).

== Frequently Asked Questions ==

= What happens if there is no supported consent manager? =

Nothing is sent. The loader fails closed. A developer can integrate another consent manager by dispatching `leeeds:consent` with `{ detail: { granted: true } }` after a valid marketing consent.

= Does this reveal the visitor's email address? =

No. Website Signals works at company level. A separate, lawfully sourced company contact is required before Leeeds can prepare or send outreach.

= Can the connection be revoked? =

Yes. Revoke the WordPress installation in Leeeds. The stored access token immediately stops working.

== Changelog ==

= 1.0.0 =

* Initial consent-first WordPress connection.
