OXYGENOXYGEN

Anonymous traffic

See which companies are on your site right now

Most of the people evaluating you never fill in a form. Visitor identification turns that anonymous traffic into named companies arriving as events you can route while the visit is still warm.

try

Your pricing page gets more qualified attention than any list you could buy, and almost none of it identifies itself. The visit happens, the tab closes, and the only surviving evidence is a number on an analytics dashboard that nobody can act on.

Deanonymized visits post to a workspace webhook in real-time and land as typed events. A visit attaches to a company record when one exists and survives unresolved when it does not, so a first look from an account nobody has heard of is still on file when they come back in March.

Example searches

Ask for it the way you'd say it

Every search below runs on the same hosted Tables, with the cost previewed before anything is spent.

  • Pricing page in the last week

    which companies looked at our pricing page in the last seven days

    Each visit lands as an event with the page and the timestamp, so the intent and its date stay together.

  • Repeat visits, not one glance

    show me accounts that came back to the site three or more times this month

    One visit is noise. A pattern of returns across several pages is the part worth a message from a person.

  • Visitors already in the pipeline

    did anyone from an open deal read the docs or the pricing page recently

    Matching visits to existing records pays off first, because the conversation with that account already exists.

Plays

Three motions you can run this week

Each one is a chain of Oxygen primitives — the same hosted objects your workspace already has, composed.

  • Pricing-page visit to a same-day touch

    A company that read the pricing page hears from you while they still remember doing it.

    1. 1Point RB2B at the workspace's own reveal webhook and arm the website-visit automation, then fire one test event to prove the route.
    2. 2Resolve a contact at the matching account and enroll only visits that clear your page and fit filters, never every hit on the blog.
    oxygen signals record
  • Match the visit to an open deal

    A quiet opportunity shows renewed activity and its owner can reply in the thread that exists.

    1. 1Attach the visit event to the company record the open deal already sits against.
    2. 2Let the owner answer inside the existing conversation rather than opening a cold one.
    oxygen signals list
  • Work the ranked queue, not the feed

    The people whose latest signal is a visit arrive as one ordered list instead of a stream nobody reads.

    1. 1Read the ranked reach-out list: it orders people by the weight and recency of their last signal, and a site visit carries the heaviest weight.
    2. 2Work down it in order, and check suppression yourself on email-only reveals, where the do-not-contact match is best effort.
    oxygen signals leads-today

Capabilities

What you get

  • Traffic that has a name

    Deanonymized visits arrive as company-level events, with person-level detail where the source can supply it, rather than as an aggregate count on a chart.

  • Unmatched visits survive

    A visit from a company you hold no record for is kept unresolved. When that account appears later, the earlier visits are already attached to it.

  • Page and frequency as filters

    A pricing page read twice is not the same thing as one bounce off a blog post. Both are stored, and where you draw the line is yours to set.

  • Delivered by webhook

    Visits post into the workspace as they happen, so routing becomes a workflow decision rather than a nightly export somebody has to remember to run.

Boundaries

What Signals does not own

Signals holds the visit. Contacting the visitor is Sequences when it is net-new outreach, or Messages when a thread already exists, and the company the visit attaches to lives in Records.

Data sources

What the data actually comes from

Every value lands with its provider and cost recorded on the cell.

  • RB

    RB2B

    Posts deanonymized visitors into a workspace webhook as they browse, which is what makes same-day routing possible.

  • People Data Labs

    Turns an identified company into a firmographic row, so a visit can be filtered on size and industry.

  • Blitz API

    Runs a people search at an identified company, so an account-level reveal gets a contact row; the seniority filters on it are yours to set.

  • LeadMagic

    Adds company and contact detail on visits the primary source manages to identify only partially.

Run these on Oxygen's managed credits, or connect your own provider keys and pay the vendor directly — the same columns, the same runs, the same provenance either way. See every integration.

Limits

Where this stops

  • Identification is partial by nature and coverage is best for United States desktop traffic. Treat the identified slice as an extra channel on top of your forms, never as a picture of everyone who visited.

FAQ

Questions people ask first

Does this identify people or companies?
Company level is the dependable part. Person-level detail arrives where the source can supply it, and the honest posture is to design the motion around named accounts instead of named individuals.
How fast does a visit reach the workspace?
It is posted by webhook as the visit happens, so routing can run the same day. Whether you act that quickly is a workflow decision rather than a limitation of the feed itself.
What about visitors I hold no record for?
They are stored as unresolved events. Identity resolution attaches them later if that company becomes a record, so early anonymous interest is never quietly thrown away.
Is every visit worth an email?
No, and treating it that way is how this channel earns a bad name. Filter on page, repeat frequency, and fit, then write only where a colleague would agree the interest looks real.
Can I use this on an existing deal?
That is the strongest use of it. A visit from an account with an open opportunity belongs in the thread its owner already has, not in a cold sequence that ignores the relationship.
What does it cost to run?
Receiving the events is part of the workspace. Credits are drawn when you enrich or resolve the companies behind them, which is exactly why filtering before enrichment matters here.

Run see which companies are on your site right now on your own workspace

Sign up, get a working workspace with a one-time credit grant, and run the first play from the web app, the CLI, or your AI assistant over MCP.