Clearbit website visitor intent
Import reviewed Clearbit Visitors company activity as governed prioritization evidence without treating anonymous traffic as a person or outreach authorization.
Clearbit Visitors can reveal the company associated with website activity. GTM Brain stores that observation as company intent, separate from verified people, consent, and outreach eligibility. The first release uses Clearbit's supported CSV export; it does not automate private Clearbit browser endpoints or assume an API entitlement that has not been verified.
Import company intent
- Export Visitors data from Clearbit Visitors.
- Open Workspace → Intelligence → Visitor intent as an organization administrator.
- Select Import Clearbit CSV and choose the export.
- Review admitted and excluded row counts, geography, domains, timestamps, and exclusion reasons.
- Confirm the exact preview. If the file or suppression state changes, preview it again.
The import uses a strict allowlist of documented company-level columns. It explicitly refuses person identifiers such as email, IP address, user agent, cookie, first name, last name, and person fields, along with unsupported or duplicate headers, self-owned domains, non-U.S. observations, suppressed companies, invalid domains or timestamps, and unbounded files. Company LinkedIn and Twitter values may be present in a supported export, but they are discarded rather than copied into the operational record.
What is stored
The governed ingest records normalized company domain, company name, U.S. location, employee/revenue bands when present, observation count, and first/latest observation time. Raw paths, person fields, social values, campaign strings, and the source file are not copied into the operational record. Repeated imports are idempotent and preserve a bounded observation history.
Intent records expire under the documented retention policy and can be activated, dismissed, or suppressed through governed actions. Suppression is rechecked inside the ingest transaction, not only in the browser preview.
How intent enters the funnel
An active visitor-intent record raises company priority and provides explainable “visited our site” context. It is not a buying-contact record and cannot authorize outreach by itself. Before a campaign can draft, GTM Brain still requires:
- the active ICP and trusted firmographics;
- a qualifying, public evidence source when policy requires one;
- a verified eligible contact;
- an approved campaign, offer, proof, and content policy; and
- current suppression, consent, frequency, and delivery checks.
PostHog follows a different boundary: it sends a lead only after the visitor supplies contact details and marketing consent. Anonymous PostHog page views remain analytics. See Website leads and PostHog.
Next: Agent-led GTM lifecycle, Integrations, and Signals.
Integrations and credentials
Connect organization-scoped signal, CRM, delivery, webhook, and external-agent providers without exposing secrets to the browser or model context.
Website leads and PostHog
Route consented, high-intent Fabric website activity from PostHog into GTM Brain without turning anonymous traffic into CRM records.