Web intent

Collect visitor information including pages visited, time spent, and traffic sources.

Overview

Clay’s web intent signal collects visitor information from your website — including pages visited, time spent, and traffic sources.

This tracking provides insights into how visitors engage with your content and helps you identify high-intent accounts at the optimal moment.

Using web intent in Clay

Creating the connection

  1. Click on your account name → Settings → Web intent.
  2. Click Add connection and give the connection a unique name in the Website name field – you'll need this later.
  3. In the Web intent setup section, copy the code from the JavaScript Snippet tab and install it with one of the methods below.
    • Directly installing a tracking snippet (Recommended):
      • We recommend installing the tracking snippet before the closing </body> tag on all pages of your website to collect comprehensive data. This snippet loads tracking scripts asynchronously, ensuring it won't affect your page loading time.
    • Installing via Google Tag Manager:
      • Note: While this method works, we recommend installing directly as ad blockers often disable Tag Manager.
      1. Navigate to the Tags section in your GTM account.
      2. Click New in the top-left to create a new tag.
      3. Add a name like Clay Visitor Tracking.
      4. Edit your Tag Configuration, and select Custom HTML as the tag type.
      5. Paste the JavaScript snippet from Clay into the text box.
      6. Below, add a new trigger, and select All Pages.
      7. Finally, click Save for this new tag, and publish your changes.
    • Installing via Twilio Segment:
      1. Visit this link to add the Clay integration as a new destination in Segment.
      2. Select the website data source in Segment you want to connect to Clay.
      3. From your Clay website connection page, copy both your Connection key and Secret key to the Segment settings page.
      4. Enable your Clay destination to begin sending events.
  4. Configure which de-anonymization providers you'd like to use. Clay provides a recommended selection or you can manually choose your own provider settings.
    • Note: Pricing is based on unique IP addresses that successfully retrieve data. You'll be charged at most once per 30-day period for each visitor with the same IP address who visits your website.
  5. In the Tracking filters section, choose which visitors and pages to track.
    • Filter by country to limit tracking to specific regions.
    • URL paths to include — by default, all pages are included. Enter paths starting with /, and use * to match multiple pages at once (e.g., /blog*).
    • URL paths to exclude — keep pages out of tracking entirely, such as /careers or the logged-in parts of your app.
  6. Select Enable connection rather than Disable connection, then click Save changes.
  7. Open Signals and choose Web intent from the quick links. You can also start from a workbook under Create.
  8. In Select website connection, pick your connection and choose a Table configuration.
    • One row per company (the default) keeps one row per company and updates it with the latest visit data each time they return.
    • New row per visit adds a new row every time someone visits.
  9. In Configure intent filters, adjust your filters.
    • Configure your table filters to show only relevant visitor data. The available fields are Company Domain, Referrer domain, Referrer path, the UTM fields, and visit counts.
    • To filter on page paths or session duration, use the connection's own filters in settings instead. Adjust visit frequency parameters to refine results further.

Since we only display completed visitor sessions, data may be delayed up to 30 minutes after user activity.

Best practices

Snippet placement

Install the tracking snippet before the closing </body> tag, not in the <head>. We recommend placing it in a global site template so it appears on all pages of your website.

URL path formatting

Use relative URL paths starting from the root domain:

  • ✅ /pricing or /blog/*
  • ❌ https://www.example.com/pricing

For wildcards, use * to match all child pages (e.g., /resources/*). Note that URL paths are exact-match, so /blog and /blog/ are treated as different paths.

Reducing credit usage

To minimize credit usage while maintaining quality results, adjust the connection's Advanced filters to focus on higher-intent traffic.

Recommended settings:

  • Minimum session duration (seconds): 20–30
  • Minimum unique pages visited: 2

These filters help narrow your results to visitors who spend more time on site and engage with multiple pages, indicating genuine interest.

You can also list specific addresses under Excluded IP addresses so they are never de-anonymized. Your own office or VPN ranges are the usual candidates, since they otherwise show up as repeat visits from your own company.

Use Waterfall instead of Best match: Waterfall runs your selected providers in sequence and stops at the first match, while Best match runs them all together and selects the highest-confidence result. Because Best match queries every provider, it costs more per visitor. Remember that IPs are cached for 30 days to avoid repeat costs.

Troubleshooting

Verification says "Tracking script not found"

This usually means:

  • The snippet isn't installed on all pages.
  • It's placed in the <head> instead of before </body>.
  • A Content Security Policy is blocking it.

Check your browser console for errors. Note that verification only checks if the script exists — a failed verification can still coexist with working data flow. Your Clay table is the ultimate proof of success.

Tracking filters not working as expected

URL paths are exact-match, so /blog and /blog/ are different. Also, filter changes only apply to new data — existing rows aren't affected. Make sure you haven't accidentally excluded important pages.

Content Security Policy blocking the script

Update your site's Content Security Policy to allow Clay domains:

Content-Security-Policy:   default-src 'self';   script-src 'self' https://static.claydar.com https://cdn.claydar.com;   connect-src 'self' https://api.claydar.com;

Not seeing new rows in my table

Common causes:

  • The connection is disabled or was just enabled (allow 30 minutes for data to appear).
  • The snippet isn't installed on the relevant pages.
  • Connection-level or table-level filters are too restrictive.
  • Your site hasn't had enough live traffic yet.

Web intent connection stopped or shows as disabled

This happens when:

  • The signal hit its monthly credit spend limit.
  • Your workspace ran out of credits.
  • The table reached the 50,000 row limit (enable passthrough tables to avoid this).

If the signal hit its monthly credit spend limit, new visit sessions resume on their own at the start of the next month. For the other two causes, re-enable the connection yourself once you've addressed them.

Unexpected companies showing up in results

Traffic from bots, VPNs, cloud infrastructure, or ISP-owned IPs can appear as companies. Filter results by company size, industry, or minimum visit count to screen out unwanted records.

If the same addresses keep appearing, add them to Excluded IP addresses in the connection's Advanced filters so they are skipped before any credits are spent.

Wrong domain showing for a company

IP de-anonymization can sometimes return a secondary or infrastructure domain instead of the primary marketing domain. If needed, use Clay enrichments by company name instead of domain to improve data quality.

Credit spend higher than expected

The most common cause is using Best match instead of Waterfall for de-anonymization. Waterfall stops at the first provider match, while Best match queries every selected provider, so it costs more per visitor. Remember that IPs are cached for 30 days to avoid repeat costs.

Other common causes: adding new pages to tracking, removing exclusions, loosening filters, or surges in site traffic.

Can the tracking snippet cause my site to crash?

No. The script runs in the visitor's browser and loads asynchronously, so it won't affect page performance. Website issues after installation are usually due to other simultaneous changes.

FAQ

Is visitor tracking data shown in real-time?

No, visitor event data can be delayed up to 30 minutes. This allows the full visitor session to be completed first.

When will I start getting charged?

Charges begin after you install the tracking snippet and Clay starts receiving events. To stop tracking, disable the website connection under your workspace settings. Clay will stop processing new visitor sessions and stop charging Clay credits.

How does pricing work?

Cost: Each successful IP enrichment consumes 1 action plus the applicable data credits (based on the de-anonymization provider). Results are cached for 30 days to avoid repeat costs.

You can view your credit spend for signals underneath the Signals tab of the credit usage dashboard. To access, click on your account name → Settings → Credit usage.

How do I cap what web intent spends?

Set a monthly ceiling on the connection itself. Click your account name → Settings → Web intent, open your connection, and find the Credit spend section.

Turn on Cap monthly credit spend, then enter a figure under Enter monthly credit limit. Once the signal reaches that number you'll stop seeing new visit sessions, and the allowance resets at the start of the next month.

How is web intent different from topic intent?

Web intent tracks visitors on your own website, so it tells you which accounts are already engaging with your content.

Topic intent is a separate signal that finds people and companies researching your topics across a provider's intent network, which surfaces net-new accounts that have not visited your site yet. The two signals are configured independently, and you can run both.

Can I track person-level information?

Clay's visitor tracking identifies unique accounts visiting your website, not individuals. Once an account is identified, you can use enrichments to find specific profiles of relevant people you may want to target at those companies.

How many site visitors can Clay support?

Clay can support hundreds of thousands of daily visitors for even the largest enterprise customers.

Is the visitor data consistent across different providers?

Yes, de-anonymized website data is in a consistent format across various providers.

Explore other docs

Gen AI

Clay MCP in ChatGPT

Connect the Clay MCP to ChatGPT, sign in to your workspace, and see what you can build and run from a chat on your plan.

View article
Settings & admin

Best practices before a member leaves your workspace

Audit admin access, billing, connections, automated work, and sequencer senders before you remove a member from your workspace.

View article
Getting started

Enhanced matching

Enhanced matching is Clay's hashed email enrichment: it finds the personal email identifiers ad platforms recognize, so more of your audience matches when you sync it.

View article
Signals & triggers

Ad lead form triggers

Send LinkedIn and Meta lead generation submissions into a Clay workflow, so each new lead is qualified, routed, or written to Audiences automatically.

View article
Export

Credit refunds

Learn when Clay refunds Actions and Data Credits, and which actions refund when a provider returns no data.

View article
Enrich

Definitive Healthcare integration

Find US hospitals in Clay and enrich them with executives, physicians, networks, payor mix, technology, and financial metrics.

View article
Enrich

Reusing saved enrichment data

Keep the data your enrichments return so later runs can reuse it instead of paying for the same answer twice.

View article

Other popular resources

Experts

Find a Clay Expert

Explore our network of Clay experts and agencies.

View experts
Community

Join our slack community

Find help in our slack community, and support channels.

Go to slack
Cohorts

Join a cohort, learn Clay fast!

The faster way to master Clay. Sign in if you're enrolled in a cohort (current or past) or apply!

Learn more about cohorts
Talents

Hire GTME Talent

Find and connect with GTM talent who've demonstrated expertise in building advanced workflows

Explore GTME talents