Visitor intelligence product concept

See the accounts behind your traffic.

A compliant visitor identification layer for B2B sites: first-party tracking, account resolution, lawful person enrichment, intent scoring, and CRM routing.

View feature set

visitor-intel.live

Live match

Unknown visitor

Government relations at BGR Group

Company onlyAU

Source

Direct

Intent

Returned after 3 days

blocked by region

CRM

No duplicate

LinkedIn enrichment

company-level only

workflow.match

{

confidence: 71,

route: "crm + slack + sequence",

dedupe: "No duplicate",

personLevelAllowed: false

}

Feature set

What we can build now.

The core product is feasible today. Person-level results depend on geography, consent, and licensed identity data, so the architecture keeps that provider layer replaceable.

Global B2B

Account-level visitor ID

Identify visiting companies globally using reverse-IP and firmographic enrichment, then show the exact pages and sessions that created intent.

US-first

Person-level matches

Resolve named people only where an approved identity partner, geography, consent policy, and suppression check allow it.

Intent

Hot-page scoring

Tag pages like pricing, case studies, integration docs, and comparison pages so sales sees real buying intent instead of raw traffic.

Activation

CRM and Slack workflows

Send clean payloads to reps, owners, lists, ad audiences, or sequences with enough context to act without opening another dashboard.

Governance

Consent and region guardrails

Honor GPC, opt-out, CMP state, retention windows, DPA requirements, and person-level blocking outside approved markets.

Buildable

Snippet and API kit

Drop in one script, collect compliant first-party behavior, and swap mock enrichment for Firecrawl, Clearbit, Demandbase, or CRM data.

Pilot dashboard

Prove match rate before scaling.

Bullseye is right about one thing: published match rates are marketing until you run your own traffic through the pipeline. This dashboard makes the pilot measurable.

14-day pilot

1,248 unique visitors

Person match

31%

US B2B traffic

Company match

64%

Global account-level

Verified email

88%

deliverable contacts

CRM duplicates

12%

merged, not created

Identity graph adapter

Keep the identity provider replaceable. Bullseye, RB2B, Warmly-style vendors all become adapters that return the same normalized contract.

Adapter contract

type IdentityGraphAdapter = {
  name: string;
  resolve(input: {
    visitorId: string;
    ip: string;
    browserSignals: Record<string, unknown>;
    consent: boolean;
    region: "US" | "EU" | "AU" | "OTHER";
    suppressionHash?: string;
  }): Promise<{
    level: "none" | "company" | "person";
    person?: {
      name: string;
      email: string;
      emailStatus: "verified" | "risky" | "unknown";
      title: string;
      linkedinUrl?: string;
    };
    source: string;
    confidence: number;
    expiresAt: string;
  }>;
};

CRM sync rules

The routing engine should update existing contacts first, create only when dedupe passes, and push visitor activity back into account history.

Hot person match

Verified email + score above 80

Create or update contact, alert owner, start sequence

Known account returns

Company match + open opportunity

Slack account owner with viewed pages

EU or AU visitor

Region blocks person-level enrichment

Company-level dashboard only

Suppressed profile

Opt-out or GPC signal present

Drop enrichment and store suppression audit

Resolution waterfall

From page view to sales action.

Competitors converge on the same pattern: collect first-party behavior, resolve company identity, enrich when allowed, score the intent, then route the insight.

Script install and first-party visitor timeline

Reverse-IP company identification

US-only person-level enrichment through consented identity vendors

High-intent page tagging and lead scoring

Slack, CRM, sequence, and ad-audience activation

Consent, opt-out, retention, and region controls

Developer kit

One script, clean payloads.

The snippet only reads your site's first-party context. It cannot and should not read LinkedIn, Facebook, or Instagram cookies.

No social-cookie access

Region-aware resolution

Suppression and opt-out checks

Configurable routing rules

Install snippet

<script>
  window.entialVisitorID = {
    accountId: "acct_live_xxxxx",
    endpoint: "https://ential.com/api/visitor-intel/collect",
    consent: window.Cookiebot?.consent?.marketing === true
  };
</script>
<script async src="https://ential.com/visitor-intel.js"></script>

Collector payload

{
  "visitorId": "ev_7c4a91",
  "consent": true,
  "page": "/pricing",
  "referrer": "https://linkedin.com/",
  "utm": { "source": "linkedin", "campaign": "demo" },
  "traits": { "email": "known-form-submit@company.com" },
  "privacy": { "gpc": false, "suppressed": false }
}

Privacy policy module:
- We use first-party cookies and similar technologies to understand B2B website activity.
- We may work with approved data partners to associate business visitors with company or contact records.
- We do not read LinkedIn, Facebook, or Instagram cookies.
- You can opt out, request deletion, or suppress future matching at any time.

MVP build plan

Ship the useful layer first.

The first version should make sales teams faster without overclaiming identity. Add person-level partners only after the consent and legal model is locked.

Tracking and sessions

Public JS snippet, collector API, visitor ID, consent flag, page/event capture, bot filtering, and retention settings.

Company matching

Reverse-IP provider adapter, firmographic profile, ICP score, excluded domains, VPN/ISP handling, and confidence labels.

Identity enrichment

Vendor adapter contract for work email, title, LinkedIn URL, geography, confidence, source, expiry, and opt-out state.

Activation workflows

Slack alerts, HubSpot or GHL lead creation, owner routing, sequence triggers, webhook delivery, and audit logs.