Office hours: Build your self-driving GTM engine·Oct 29, 9:00am PT, onlineRegister→
Cargo
  • PrimitivesData ModelsYour companies, contacts and deals, merged from every sourceContextWhat your team knows, as files every agent readsTerritoriesWho sells where, defined onceMailboxesMailboxes in your reps' names, warmed up and kept under limitsToolsThe actions your agents, plays and reps callAgentsAI that researches, decides and writes, reading your contextPlaysWorkflows that run on a trigger or a schedule, with retriesAppsInternal apps for your reps, hosted on Cargo
    Add-onsChrome ExtensionSell faster, right in your browserButtonTrigger AI agents inside your CRMFormTurn any tool into an embeddable formSlackTag Cargo in Slack. It does the GTM workGitHubPlan on every pull request, deploy on merge
    MoreProjectsDefine your entire GTM in codeCLIUse Cargo from your terminalMCPUse Cargo from Claude and ChatGPTDeveloper resourcesCargo API docs, OpenAPI spec, auth docs, webhooks, MCP serverAPI ReferenceExplore the Cargo APIDocumentationLearn how to use CargoIntegrationsConnected to your entire GTM stack
  • VeriffHow Veriff replaced MuleSoft with Cargo under NetSuite, Stripe and SalesforceAugmentHow Augment Code routes developer sign-ups to reps in under an hourWeights & BiasesHow Weights & Biases ships a new purchase signal in 2 days on CargoSee all
  • Pricing
  • Cookbooks
  • Blog
Sign in
Cookbooks
VISignals

Visitor identification

Identify which companies visit your website and what they read: Snitcher identifies the organisation behind each visit, two Cargo models keep the visiting companies and their sessions current, and the site loads the tracker only after a visitor accepts it.

Installation
Set up the visitor-identification cookbook in this project. 1. If the Cargo CLI is not installed yet, follow every step in https://api.getcargo.io/INSTALL.md 2. From the Cargo project, run: cargo-ai project add cookbook/visitor-identification 3. Then follow .claude/skills/visitor-identification/SKILL.md. Stop for my approval before any paid call, and stop at "cargo-ai project plan" before deploying anything.
Paste it into Claude Code, Cursor, Codex, Gemini CLI, Devin or Replicas.
$cargo-ai project add cookbook/visitor-identification
Run it in your Cargo project. Copies the example in, and deploys nothing.

Say this to your agent

Show us which companies visit www.fabrikam.example, and only track visitors who accept.

Illustrative output #

Fictional records, to show the shape of what comes back.

text
model:website_visiting_companies     deployed   12 companies after the first day
  northwind.example     Software     first seen 09:14   last seen 16:02
  contoso.example       Logistics    first seen 11:40   last seen 11:52
model:website_visitor_sessions       deployed   31 sessions
  northwind.example     /pricing/ /about/      referrer: linkedin.com
app:website                          updated    consent gate on, tracker after accept only

Rows land on Cargo’s own sync interval. A day with no identified company is an honest zero: not every IP resolves to an organisation.

Done when #

  • node --import tsx evals/contract.mjs passes: the companies model is fetchOrganisations on the Snitcher connector with an HTTPS url, the sessions model is fetchSessions reading config._workspaceUuid from it, both are filed in visitor_identification_models
  • the plan’s first deploy shows the two models and the app update, and the operator approved the spend against the live price
  • in a browser on the canonical origin: no request to snitcher.com before a choice, after “Reject tracking”, or after withdrawing and reloading; one “Accept tracking” makes a request to cdn.snitcher.com and radar.snitcher.com
  • the Cargo URL and a draft preview make no request to snitcher.com and show no banner
  • after the sync interval the models hold rows, or a zero reported as a zero
  • the banner links to the reviewed privacy disclosure

What it costs #

Each company Snitcher identifies is billed once, when it first lands in the companies model; sessions add nothing. Read the live price from the integration (cargo-ai connection integration get snitcher) and the workspace’s credit balance before the first deploy, and quote both. Spend follows the site’s traffic and there is no built-in cap, so say that too. Removing the companies model stops the billing.

To see which companies visit your website and what they read, identify the organisation behind each visit with Snitcher and keep the results in two Cargo models, website_visiting_companies and website_visitor_sessions. The site loads the tracker only after a visitor accepts it, and it identifies companies, never named people.

shellscript
cargo-ai project add cookbook/visitor-identification
text
visitor accepts on the site
  -> the site's own Snitcher loader (profile ID only)
  -> Snitcher identifies the company from the visit
  -> website_visiting_companies + website_visitor_sessions   (Cargo, on its sync interval)

Why it is built this way #

One deploy, no capture step. Snitcher’s tracker and workspace only exist once the companies model is created. visitingCompanies.config._trackingScript and ._workspaceUuid are project tokens, so the sessions model and the site’s env read them in the same deploy that creates them.

The site owns its loader. The provider’s snippet is a script; the site takes only its public profile ID from it, rejects any other shape at build time, and loads Snitcher with settings this repository reviews: consent required, form, click, download, error and recording capture off.

Nothing before consent. Snitcher’s own waitForConsent still records pageviews and sessions before consent, so the gate does not request the tracker at all until the visitor accepts.

Company-level by design. An IP address resolved to an organisation. No identify call, no person, no outreach in this skill.

Placeholders (edit before deploy) #

  1. Site URL: infra/models/companies.ts url, the site’s canonicalUrl.
  2. Privacy disclosure: site/visitors.json privacyPolicyUrl, once copied into the app.

Files #

PathWhat it is
infra/connectors/snitcher.tsSnitcher on Cargo’s credits
infra/models/companies.tsfetchOrganisations: the companies, and the tracker
infra/models/sessions.tsfetchSessions, on the provisioned workspace
site/lib/snitcher.tsSnippet to reviewed settings; anything else fails
site/lib/visitors.tsBuild-time switch: settings, or no gate at all
site/components/visitor-consent.tsxThe consent gate and the loader
references/consent.mdWiring the site, and checking the gate in a browser
references/data.mdWhat the rows mean, querying, stopping
evals/contract.mjsGraph and parser contract

Verify #

shellscript
node --import tsx visitor-identification/evals/contract.mjs
Version0.1.2
LicenseMIT
Source
Deploys
  • connectors
  • models
For
  • Marketing
  • Sales development
  • GTM engineering
Integrations
  • Snitcher
Content
  • Say this to your agent
  • Illustrative output
  • Done when
  • What it costs
  • Why it is built this way
  • Placeholders (edit before deploy)
  • Files
  • Verify
More in Signals
  • New hire detection
  • Social listening
  • Readiness scoring
Next: Engagement
  • Inbound qualification
  • Agentic engagement

Build the self-driving GTM engine

Your coding agents build it on Cargo.Or our team builds, operates and improves it with you.

Start building
Cargo
Backed byY CombinatorSOC 2 Type IICertified
LinkedinX

Product

Data ModelsContextTerritoriesMailboxesToolsAI AgentsPlaysAppsIntegrationsPricing

Add-ons

Chrome extensionButtonFormSlackGitHub

Build

DocsDeveloper resourcesCargo API docsCargo OpenAPI specCargo auth docsCargo webhooksCargo MCP serverProjectsClaude CodeCodexCursorAll coding agents

Resources

ReportsBlogCustomer storiesCookbooksEnrichmentRoutingSignalsScoringCRM hygieneAd audiencesGTM skillsGTM EngineeringGlossaryCompareCargo x ClayCargo x WorkatoCargo x n8nCargo x DeeplineCargo x DefaultCargo x LeanDataCargo x UnifyCargo x ValleyCargo x GojiberryCargo x PhantomBusterCargo x ZapierCargo x ApolloCargo x Chili PiperCargo x Common RoomCargo x MakeCargo x Tray.io

Company

ManifestoCommunityEventsJobsPartners DirectoryPartner Program

Legal

SecurityTerms of servicePrivacy PolicyRefundsDPASupport
© 2026 Cargo
 ////////    ///////    ////////     ////////    ///////
///         ///   ///   ///   ///   ///         ///   ///
///         ///   ///   ///   ///   ///         ///   ///
///         /////////   ////////    ///  ////   ///   ///
///         ///   ///   /// ///     ///   ///   ///   ///
///         ///   ///   ///  ///    ///   ///   ///   ///
 ////////   ///   ///   ///   ///    ///////     ///////

$ npm install -g @cargo-ai/cli