Script speed, cookies and data collected
What the IntentBid script collects, what it never collects, and its effect on page speed.
What the script sends
- The page URL (we store only the path, never the query string, plus the campaign parameters we need for attribution)
- The referrer (where the visit came from)
- A random session ID kept in the tab's sessionStorage, which disappears when the tab closes
- A short "engaged" signal after 15 seconds with the page visible
Our server also sees the visitor's IP address, as every web server does, to look up the company.
What it never does
- Set cookies or use localStorage
- Run for visitors whose browser sends Global Privacy Control
- Read form fields, keystrokes or page content
- Fingerprint the browser
- Store the plain IP address (it is encrypted and deleted within 24 hours)
Page speed
The script is small, loads with async and sends data with the browser's beacon API, so it never blocks rendering or delays your page.
Bots
Known crawlers and AI bots (including GPTBot and PerplexityBot) are filtered out before anything is stored.
Related articles
How company identification worksWhat happens between a page view and a named company: filters, lookups, caching, credits and privacy.Allowed domains and subdomainsWhich domains the script accepts visits from, how subdomains work and how to add extra domains such as docs or regional sites.Check the script is installedHow to confirm the IntentBid script is running, and what to do when Get started still says it is waiting for the first visit.Exclude your own office trafficAdd your office IP addresses so your own team's visits are ignored in reports and never use credits.