Skip to main content
When a company visits your website, Knock2 resolves the session’s IP address and browser signals to a real organization and creates an Account record. Accounts are the foundational company-level objects in Knock2 — every identified visit, contact, score, and CRM sync is anchored to one.

​
What is an account?

Knock2 uses IP-to-company resolution combined with browser-level signals to map live website sessions to organizations. When the resolution confidence meets the identification threshold, Knock2 creates or updates an Account record for that company. Each account is unique per organization — repeated visits by the same company accumulate activity on the same record rather than creating duplicates. Account records grow richer over time. As the company continues to visit, Knock2 appends visit history, refreshes enrichment data, calculates lead scores, and — if you have a CRM integration enabled — surfaces deal context directly on the account.

​
Account data fields

​
string
required
The unique Knock2 identifier for the account (e.g. acc_01HX...).
​
string
The company’s display name (e.g. "Acme Corporation").
​
string
The company’s primary website domain (e.g. "acme.com"). Used for CRM matching and deduplication.
​
string
The company’s industry classification (e.g. "Software", "Financial Services").
​
string
A broader sector grouping for the company (e.g. "Technology").
​
string
A banded headcount range (e.g. "51-200", "1001-5000").
​
string
A banded annual revenue range (e.g. "$10M-$50M").
​
string[]
An array of phone numbers associated with the company.
​
string[]
Firmographic tags applied to the account (e.g. ["B2B", "PLG"]).
​
string[]
Technology stack tags detected or enriched for the company (e.g. ["Salesforce", "HubSpot", "React"]).
​
string
City of the company’s primary address.
​
string
State or region of the company’s primary address.
​
string
Country of the company’s primary address (ISO 3166-1 alpha-2 code, e.g. "US").
​
string
A human-readable combined location string (e.g. "San Francisco, CA, US").
​
string
ISO 8601 date of the company’s most recent funding event (e.g. "2023-09-15").
​
string
The type of the most recent funding round (e.g. "Series B", "Seed").
​
string
The amount raised in the most recent funding round (e.g. "$20,000,000").
​
string
The deal source as synced from your connected CRM. Only populated when a CRM integration is active.
​
string
The current deal stage from your connected CRM (e.g. "Negotiation").
​
number
The deal value in USD as synced from your CRM.
​
string
The matching HubSpot Company record ID. Populated when the HubSpot integration is enabled.
​
string
The matching Salesforce Account record ID. Populated when the Salesforce integration is enabled.
​
string
ISO 8601 timestamp of the most recent session from this account (e.g. "2024-06-01T14:30:00Z").
​
string
The URL or path of the most recently visited page (e.g. "/pricing").
​
number
The cumulative time in seconds this account has spent on your website across all sessions.
​
string
The UTM source captured on the account’s first or most recent attributed session (e.g. "google").
​
string
The UTM medium for attribution (e.g. "cpc", "email").
​
string
The UTM campaign name for attribution (e.g. "q3-launch").
​
string
ISO 8601 timestamp of when Knock2 first identified this account.

​
Pagination

The GET /v1/accounts endpoint returns results as a paginated list. Knock2 uses cursor-based pagination — each response includes a next_cursor value you pass as the cursor query parameter on your next request to fetch the following page. This approach ensures stable, consistent results even when new accounts are identified between requests. See the Pagination guide for a full walkthrough of cursor handling, page size configuration, and iterating to the end of a result set.

​
Filtering

Accounts support a rich set of filter conditions covering firmographic data, visit behavior, UTM attribution, funding signals, and CRM deal context. You can pass inline filter JSON directly on the request, or save a reusable query as a Filter Set and reference it by ID.

​
Looking up a single account

Use GET /v1/accounts/{account_id} to fetch a single account by its Knock2 ID:
You can also look up an account by its company domain by passing the domain query parameter to GET /v1/accounts. This is useful when you have the domain from a CRM record or form fill but not the internal Knock2 ID: