Know which companies are on your site
Runner turns first-party visits into useful account context, keeps the history on the record and automatically applies the right identification level for each visitor's location.
Built into Runner
- One line of script, on every product you run
- Who is on the site now, by country or state
- A limit your team can tighten for each product, and nothing can raise
Worth knowing
In the US a visit can be claimed as a person — on evidence they volunteered, or through an identity provider you connect and switch on yourself, on your own key — and a teammate approves it before it becomes a contact. In Australia, Canada, the EU, Japan, Korea and the UK the same is possible only for a visitor who turned Recognition on in the site's notice themselves. Everywhere else you get the company, or just the count.
Runner checks every visit as it lands, so your team starts from the account
Nobody on your team presses a button. Each visit is checked as it arrives, Global Privacy Control before the rule for where the visitor is and your admins' limit last, then written to the record with what was attempted, what was permitted and why. Turned-down claims are kept too, so the record shows why someone wasn't identified.
A visit from a company's network lands on that company's account as history: which pages, when, how often. Mark the pages that matter, like pricing, and a company-identified visit to one becomes a review-queue entry on that account. Pages match on the path alone. The query string is dropped first, because that's where email addresses and reset tokens travel.
Two bits of housekeeping. Send your team a link to any page of your site ending in ?shmaplex_traffic=internal: each browser that opens it is still recorded but kept out of your human traffic numbers, and ?shmaplex_traffic=all puts it back. And a script tag left behind after its key is withdrawn loads a file that quietly does nothing, never an error.
Try it
The link shows nothing on the page, by design. Type runner.status() in the browser console afterwards: trafficContext reads internal, which is how you know it took.
A made-up week: four visits, and what each one became
A ten-person dev-tools startup has marked /pricing as "Pricing", and Northwind, a fictional freight firm, is already an account on its record.
Tuesday, a visit from an office network registered to Northwind opens /pricing. It lands on the account as history, and the review queue gets an entry reading A visitor from this company viewed a hot page: "Pricing". Nobody is emailed and no contact is created.
Wednesday, a visit comes from a home broadband line. The holder is an internet provider, so no company is written, the visit still counts, and the provider shows as its network line.
Thursday, someone in Seoul reads the docs: nothing is worked out from that traffic, and the visit is still counted. Friday, a visitor with Global Privacy Control on isn't matched to a named person, wherever they are, and company counting carries on.
Runner plugs into your sites, your code and your own data account
Your sites: one script tag, served from Runner's origin with the major version pinned in the address, and the same line on every product you run. Your own code can call track for an event and identify when a user signs in.
Your own IP-to-company data account, on your own key, adds the company behind a visit. An organization owner or admin connects it once for the whole organization. It's only asked about visits your own records don't already recognise, and each claim keeps the source that produced it, so a dataset's inference is never reported as something your records established.
The analytics you already run can stay alongside it. What Runner adds is the visit history on the account record, next to everything else your team keeps about that company.
Questions buyers ask
Can website visitor identification software tell me who a visitor is?
Sometimes, and where they are decides it: the bound under Worth knowing, above, says exactly where. Recognition, the switch it names outside the US, stays off until the visitor turns it on, and Accept doesn't turn it on.
Does it use cookies or fingerprinting?
No fingerprinting on any level, and no cookie on the cookieless level. A repeat-visit identifier is kept only where the site runs the persistent level, the visitor said yes, and no Global Privacy Control signal is present; otherwise it lasts one page load and is written nowhere. Three small markers that name nobody are kept on every level: the consent decision, whether the notice was seen, and the internal-traffic flag.
Can we identify less than a region allows?
Yes, and only less: no identification at all, or the company at most, for the organization or for one product, and the stricter setting wins. Nothing in the product can raise a limit above what the visitor's region permits, and it's enforced in the database from the tracking key, never trusted from the browser.
Does it work for visitors in Europe?
Up to the company. In the EU and the UK, identification from traffic goes as far as the company, and a named person is possible only for a visitor who turned Recognition on in the site's notice themselves.
Will it email the companies it finds, or add them to a sequence?
No. An identified visit triggers no outreach and creates no contact, at any confidence level. A claim becomes a contact only after a person reviews it and writes a reason, and it arrives with consent unknown, because identifying somebody isn't permission to contact them.
What match rate should I expect?
None is published, because none has been measured. How often a visit comes back with a company depends on where your visitors arrive from: a home broadband line belongs to an internet provider and writes no company, and in some regions nothing is worked out from traffic at all.
Use what already works
Connect your own enrichment account, on your own key, to add the company behind a visit. Keep GA4 or the reporting tools you already use alongside it while Runner becomes the first-party account record.
How teams often buy this job
Usually bought as Leadfeeder, RB2B or Dealfront.
LeadfeederRB2BDealfront
Trademarks of their owners. No affiliation or endorsement.