Choose Dashboard if you want Snitcher to identify visiting companies and give you the tools to work with them. Choose the OEM products, Radar and IP2C, if you want to build visitor identification into a product of your own.
Want Snitcher data in your own dashboard or CRM? Dashboard already includes a REST API and Webhooks for that. You do not need the OEM products just because you want an integration.
1. Dashboard: use Snitcher for your business or clients
Install the Snitcher tracker and you get company identification, segments, alerts, and CRM integrations. Use it for lead follow-up, target-account campaigns, lost-deal reactivation, or reporting on who visits your website.
Dashboard includes the REST API, Webhooks, MCP, and Spotter. These let you use your Snitcher workspace and its data in different ways. They are part of the Dashboard product.
To start using Dashboard, install the Snitcher tracker. For an example workflow, see the lost-deal reactivation recipe.
Agencies: manage Snitcher for your clients
With the Partner / Agency program, each client has a Snitcher workspace and subscription. You manage these from the partner portal and earn commission.
You can also pull each client’s Snitcher data into your own reporting dashboard or CMS using the REST API. Snitcher still handles the tracking, identification, workspace features, and subscription usage. Building that connection does not mean you need to build a whole visitor-identification product.
REST API and Webhooks: connect your other tools
The Dashboard REST API reads and manages data in your Snitcher workspaces. For example, you can pull identified companies and visits into your own reporting tool, create client workspaces, or update custom fields.
Dashboard Webhooks send configured events and data to your system as they happen. Use them to trigger a workflow or connect a custom CRM. Your integration needs to handle duplicate records; a webhook is not a ready-made two-way CRM sync.
Generate a REST API token under Settings → Account → API. It can access the workspaces your user has access to. See the REST API docs and Webhooks docs.
MCP: work with Snitcher through an AI assistant
Connect an MCP-compatible AI assistant to your Snitcher workspace to ask questions about your visitors or make changes, such as adjusting your ICP scorecard. The assistant is instructed to ask for confirmation before applying changes.
Reading and analysing data through MCP uses no Snitcher AI or reveal credits. Revealing a contact’s email uses reveal credits, just as it does in the app. Connect your AI assistant to Snitcher.
Spotter: personalise your website
Spotter makes an identified company available to code running on your website. You could show the company’s logo or add its details to a form submission.
It needs the Snitcher tracker and authorised domains, but no API key. Your website should still work when identification takes time or no company is found. Get started with Spotter.
2. OEM: build your own product with Radar and IP2C
These are separate products for developers building visitor identification into their own software, such as a lead-generation platform. You get the tracking and identification services to build on. You build the interface, logins, customer workspaces, workflows, billing, and integrations you need.
OEM does not include Dashboard, the Dashboard REST API, Dashboard Webhooks, MCP, or Spotter. Radar and IP2C have their own APIs, and Radar delivers tracking data through webhooks. They do not come with a ready-made Snitcher dashboard to rebrand.
IP2C identifies companies
IP2C, short for IP-to-Company, returns company details for an IP address or a Radar session ID when a match is found. If you already collect visitor IP addresses and only need company identification, you can use IP2C on its own.
Radar collects website activity
Radar collects events and sessions from websites and delivers them to your webhook. Radar does not identify companies. To identify a company, make a separate IP2C lookup for the session.
Use Radar plus IP2C when you need both tracking and identification. Session-based identification can also give you a higher match rate than looking up IP addresses alone.
Before choosing OEM
You need someone to build and maintain the software around these services. If you mainly want to manage client websites and show their results in your own tools, start with Dashboard and the Partner / Agency program above.
IP2C agreements normally start at $10,000 per year. Radar has its own standalone pricing when used for raw tracking without the identification contract.
Pricing depends on volume and whether Snitcher attribution is displayed, so the exact commercials come from a conversation with sales.
Talk to sales for access. Technical details: IP2C docs and Radar docs.
What neither product does
Name anonymous visitors. Company identification does not tell you which person visited. Known people can be linked through a form, login, or tracked link using the Identity Layer. Suggested contacts are not proof that those people visited.
Identify consumers or households. Snitcher is built for B2B company identification.
Provide off-site keyword intent. Snitcher works from visits to your websites and connected data, not people’s searches elsewhere.
