Not every website signal should become an email
A page visit is not sales consent and does not justify contacting a named person. A useful system must respect cookie choices, evaluate the company and only then decide whether a legitimate, relevant B2B next step exists.
Leeeds separates visit measurement, company identification, business contact sourcing and sequence execution. Each layer can be inspected, paused or disconnected.
Website intent is valuable only when it avoids shortcuts
Some products imply that an anonymous visit instantly reveals a person. Website Signals do not work that way. The tracker handles company-level signals and does not determine a visitor's name or email.
The second risk is blind automation: one pageview starts a generic message. Leeeds combines returning visits and important paths, requires sufficient identity confidence and uses the safety rules of an existing sequence.
From consent to a prepared sales action
The flow makes it clear what happened on the website, what remains a technical signal and where an actual sales decision begins.
The website waits for marketing consent
The WordPress loader supports WP Consent API, Cookiebot, Complianz, CookieYes and a custom consent event. If it cannot verify consent, it fails closed and sends nothing.
Leeeds accepts the configured domain
The endpoint checks origin, pixel domain and measurement status, applies rate limits and stores a clean path without query parameters. Raw events default to 90-day retention.
Leeeds creates a first-party company link
After a verified human click on a Leeeds email, the system stores a client-scoped HMAC of the network signal. A later visit is matched locally, without any external IP-to-Company API.
Intent scoring chooses the moment
A return visit, pricing page or demo path carry different weight. Only a sufficiently strong signal can prepare a lead and route it into the selected acquisition sequence.
Contacts and email keep Leeeds safeguards
A business contact comes from allowed company sources, passes safety and deduplication, and enters the existing sequence. Website intent does not bypass approval or mailbox limits.
A WordPress connection an administrator can finish
The client portal first enables consent-first measurement for the exact domain. The administrator downloads the Leeeds Website Signals ZIP and uploads it through the standard WordPress plugin screen.
Leeeds creates a single-use code valid for 15 minutes and bound to that domain. The plugin exchanges it for a revocable token. The token never reaches the visitor's browser and Leeeds stores only its hash.
The plugin checks connection health daily, reports its consent adapter and suggests privacy-policy wording through WordPress. Revoking the installation in Leeeds immediately invalidates future authenticated checks.
Non-WordPress sites can use the short installation script. It remains subject to the configured consent mode and allowed domain.
Leeeds Website Signals
Install the ZIP in WordPress, activate the plugin and connect it with the one-time code from Leeeds.
What the system does—and deliberately does not do
A company returns to pricing and demo pages: intent increases and can prepare the next sequence step after the threshold is met.
A visitor rejects marketing cookies: the WordPress loader never loads the tracker.
A request arrives from another domain or without an origin: the event is rejected.
An anonymous visit has no previous verified relationship: Leeeds can measure the permitted signal, but it does not guess the company or run a company trigger.
A company is identified: the system still does not guess who visited. Outreach uses a relevant business role sourced separately.
What the customer gains
Installation
01ZIP + one code
A WordPress administrator does not edit the theme or paste JavaScript into a header.
Control
02Three separate layers
Measurement, company identification and sequence routing each have their own state and diagnostics.
Safety
03Fail closed
Without consent, an allowed domain or a valid connection, the signal is not used.
Website analytics becomes a sales system only with context and brakes
Website Signals are not a replacement for analytics or a trick for exposing a person. They are a B2B input that distinguishes a weak visit from repeated company interest.
The pixel is the smallest part. The value comes from connecting consent, company identity, qualification, business contacts and a sequence into one explainable next step.
Keep reading
These related pages connect the strategy, compliance and real workflow behind Leeeds.
CRM and personalization
How Leeeds uses CRM data in outreach
A concrete illustrative example of how Leeeds connects CRM orders to a company profile, safely uses verified context in the first email and hands the reply to sales.
Read next
Sequences
Why sequences are core to Leeeds
How Leeeds uses sequences as a sales journey: email steps, activity-based branching, CRM import, replies and safe follow-ups.
Read next
GDPR guide
GDPR lead generation guide
A practical guide to GDPR-safe B2B lead generation: lawful sources, legitimate interest, opt-out, AI review, audit trail and CRM handoff.
Read next
Model case study
Manufacturer entering a new market
A detailed model case for a manufacturer that needs to separate buyers, integrators and distributors before outreach begins.
Read nextWant to connect your website to an acquisition sequence?
We can configure the domain, consent layer, company identity and a safe intent threshold. WordPress then connects through the ZIP and a one-time code.
Discuss Website SignalsThis article describes Leeeds Website Signals' first-party architecture. Identity is learned from verified human clicks, matched locally and never identifies a named visitor.