For cybersecurity vendors

Enterprise security teams evaluate you for months — from behind a corporate firewall.You never see them. Backstory does.

Backstory identifies the enterprise accounts already on your site, scores how close each is to buying, and turns the traffic you already have into a warm, account-level pipeline.

first-party · company-level · no PII to identify · opt-in Lead identification

The problem

GA4 shows you sessions. It never shows you the enterprise security team that read your docs, compared you, and priced you—then left without a word.

Your best-fit buyers research anonymously, from corporate networks. When inbound dips, you have no second source of warm enterprise pipeline. That’s the gap Backstory closes.

vs third-party intent

Not another intent database

Third-party tools infer intent from across the web and sell you person-level data. Backstory reads what accounts did on your own site.

DimensionBackstoryThird-party intent tools
Signal sourceFirst-party — what accounts did on your own siteThird-party intent from across the web
ResolutionCompany-level identification (no PII), plus opt-in Lead identificationPerson-level tracking across the web
The scoreExplainable — the signals sum to the numberBlack-box propensity
PrivacyCookieless; no PII to identify the accountCookies + personal data
Priced forA self-serve startup, from $99/moAn enterprise contract
How it works

From anonymous traffic to a warm account list

Website visitor identification for a cybersecurity vendor runs in four steps: identify the enterprise account behind the visit, score how close it is to buying, act while it’s still warm, and—when you’re ready—reach the buying committee. Identification is first-party and company-level; Lead identification is opt-in.

01

Identify the account, never the person

Backstory resolves anonymous traffic to the organization from first-party signals, then strips ISPs, home broadband, VPNs, and cloud hosting — so your list is real enterprise accounts, each enriched with up to 60+ firmographic fields. The IP is enriched to a company domain, then discarded.

02

Score how close they are to buying

A transparent 0–100 buying-intent score, tiered hot / warm / cold, built from what each account did on your site — pricing visits, return trips, activity from several stakeholders. The breakdown adds up to the number.

Sample data
Backstory buying-intent breakdown: visits to pricing, return trips, and multi-stakeholder traffic add up to a score of 92
03

Act while they’re still warm

Every account comes with an AI playbook — where they are in the buyer journey and exactly how to reach out — routed to Slack (beta) or any tool via webhook (Zapier, Make, n8n).

Sample data
Backstory sales playbook for an account: three specific, journey-based outreach next steps
04

Reach the buying committee, on demand

When an account is worth a conversation, identify the people to reach: Backstory matches your target job titles and locations to the decision-makers at that identified account and returns each one’s name, title, LinkedIn, and verified work email. First-party behavior tells you which account is in-market; the Leads come from a business-contact provider — never from de-anonymizing the individual who visited. Opt-in and credit-metered, so your security team stays in control.

Privacy by design

Identify the account without the personal data

Most website visitor identification tools de-anonymize people. Backstory identifies the account, never the individual who visited. Reaching the decision-makers is a separate, opt-in identification—DPA-governed and credit-metered, so a security team stays in control.

  • First-party only — your own site traffic, nothing bought.
  • Account-level identification — the organization, never the individual who visited.
  • No PII to identify the account — IPs are enriched to a company domain, then discarded.
  • Cookieless — nothing for visitors to accept, nothing for you to manage.
  • Lead identification is opt-in — decision-makers’ business-contact details only under a data-processing agreement you accept, credit-metered, with opt-out honored.
  • Private by architecture — company-level and cookieless from the ground up.

Built for cybersecurity vendors selling to the enterprise—where buyers browse from identifiable corporate networks. It’s honestly weak for home-broadband and mobile traffic, so it’s not for you if you sell to small businesses or consumers.

FAQ

Questions security teams ask

How do you identify companies visiting our website?
Backstory reads the first-party network signal from each visit and resolves it to the organization behind it — a reverse-IP-to-company match — then strips ISPs, VPNs, home broadband, and cloud hosting, leaving real enterprise accounts. It’s company-level identification: the account, never a named person.
Is this website visitor de-anonymization?
At the company level, yes — Backstory de-anonymizes anonymous traffic into the enterprise accounts behind it. It never de-anonymizes the individual who visited: no tracking of the person, cookieless. Reaching the decision-makers at that account is a separate, opt-in step — Lead identification provides their business-contact details (name, title, LinkedIn, verified work email) under a data-processing agreement you accept and credit-metered, never the identity of the person who browsed.
Do you store personal data?
To identify the account, no — Backstory resolves the visit to the organization, never a named individual; visitor IPs are enriched to a company domain and then discarded, cookieless. Lead identification is deliberate and different: when you opt in, it provides the decision-makers’ business-contact details for an identified account, DPA-governed and credit-metered. So there’s no PII to identify the account, and personal business-contact data only under a data-processing agreement you accept.
How is this different from third-party intent tools?
Third-party tools infer intent from what an account researched across the web and hand you person-level data. Backstory scores what accounts actually did on your own site — first-party, company-level, with a breakdown you can read.
Will it identify our traffic?
If your buyers visit from corporate networks — which enterprise security teams do — yes. It’s deliberately thin for home broadband and mobile visitors, and we’re upfront about that.
What’s shipped, and what’s coming?
Everything here works today: account identification, buying-intent scoring, interests, per-account playbooks, Slack (beta) and webhook alerts, CSV export — and Lead identification, the decision-makers to reach at each identified account (name, title, LinkedIn, verified work email), opt-in and credit-metered.

See who’s evaluating you.

Add a snippet and start seeing the enterprise accounts on your site—and how close each one is to buying.