Website visitor reveal (company-level)
A ~330-word demand-gen help article explaining how to install Tipoff's company-level website reveal tag, its privacy posture (company-only, no cookies/fingerprinting, honors GPC/DNT/consent), and how to view visiting accounts.
Most of the people researching you never fill out a form. Website visitor reveal closes that gap by identifying the companies browsing your site, so you can spot in-market accounts and follow up while intent is fresh. It works at the company level only, never resolving individual people, and it runs without cookies or fingerprinting.
How it works
Tipoff matches the network signals of a visit to a company using IP-to-company intelligence. It answers "which account is on the page," not "who is the person." No personal profiles are built, no cross-site tracking is used, and no device fingerprinting takes place.
Privacy posture
Privacy is the default, not a setting you bolt on:
- Company-level only. Reveal returns an organization, never a named individual.
- No cookies or fingerprinting. Nothing is stored on the visitor's device to make the match.
- Honors GPC, DNT, and consent. When a visitor sends Global Privacy Control or Do Not Track, or declines through your consent banner, that visit is excluded from reveal.
- Your control. You decide which pages carry the tag and can remove it at any time.
Install the tag
- Open Settings → Website reveal in Tipoff and copy your tag snippet.
- Paste it before the closing
</body>on the pages you want to track, or add it through your tag manager. - If you use a consent platform, gate the tag behind your analytics/marketing category so it fires only after consent.
- Save and publish. Visit a page yourself to confirm the tag loads.
See who visited
- Go to Reveal → Companies.
- Review the list of visiting accounts with pages viewed, visit recency, and frequency.
- Filter to accounts that match your ICP corpus, or sort by tier to surface your best-fit visitors first.
- Push a company to your CRM, Slack, or a sequence to act on the signal.
Allow a short window after install for traffic to accumulate before expecting a full list.
Related: See ICP tiering to prioritize revealed accounts, and Integrations to route them into HubSpot, Pipedrive, Slack, or your sequencer.