> ## Documentation Index
> Fetch the complete documentation index at: https://docs.squid-id.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Send visitors to Clay

> Send identified Squid ID visitors into a Clay table through a Clay webhook source, with control over which fields are sent, which visitors qualify, and how often.

When a visitor is identified, Squid ID sends their enriched profile to a Clay table through a Clay inbound webhook ("Monitor webhook") source. Each identified visitor becomes one row, and Clay builds columns from the JSON keys automatically. You choose which field groups to send, which visitors qualify, and whether to send once per person or on every visit.

## If you're coming from RB2B

RB2B also sends to Clay through a webhook, but the control stops there: a fixed payload, no targeting, and a single "send repeat visitor data" toggle. Squid ID gives you the same one-click webhook plus routing, requirements, deeper enrichment, and premium contact data.

<div className="compare">
  <table>
    <thead>
      <tr><th /><th>RB2B</th><th>Squid ID</th></tr>
    </thead>

    <tbody>
      <tr><td>Connection</td><td>Clay webhook URL</td><td>Clay webhook URL</td></tr>
      <tr><td>Webhook auth</td><td>URL only</td><td>Optional <code>x-clay-webhook-auth</code> token</td></tr>
      <tr><td>How often</td><td>Net-new, or every visit</td><td>Net-new, or every visit (repeats tagged <code>is\_repeat\_visit</code>)</td></tr>
      <tr><td>Who to send</td><td>All visitors</td><td>All, by ICP, or by high-intent page</td></tr>
      <tr><td>Requirements</td><td>Not available</td><td>Require a company, a LinkedIn, or a work/personal email</td></tr>
      <tr><td>Field control</td><td>Fixed payload</td><td>Per-group toggles with a live JSON preview</td></tr>
      <tr><td>Enrichment depth</td><td>Core contact fields</td><td>Traits, social, company, job, location, experience, skills, interests</td></tr>
      <tr><td>Premium contact data</td><td>Not provided</td><td>Mobile, personal email, home address and more with <a href="/add-ons/squid-id-plus">Squid ID+</a></td></tr>
      <tr><td>Test before saving</td><td>Not available</td><td>Send a test event to confirm delivery</td></tr>
      <tr><td>Pause without disconnecting</td><td>Not available</td><td>Enable/disable toggle keeps the setup</td></tr>
    </tbody>
  </table>
</div>

<p className="why"><strong>Why this matters.</strong> RB2B fills your Clay table with every visitor and leaves the filtering to you. Squid ID lets each Clay table receive exactly the segment it cares about, once per person by default, with the depth of data Clay needs to take action.</p>

## Before you start

<Info>You'll move faster if these are already in place.</Info>

* You're an **Owner** or **Admin** on the website. Viewers can see the connector but can't change it.
* The [snippet is installed and verified](/getting-started/install-snippet), so there are visitors to send.
* A Clay table with a webhook source, so you have a URL to paste. In Clay, add a source, search **Webhook**, choose **Monitor webhook**, and copy the URL (and, optionally, the auth token).

## Connect Clay

<Steps>
  <Step title="Open the Clay connector">
    Go to **Settings → Integrations** and click **Connect** on the Clay card.
  </Step>

  <Step title="Paste the Clay webhook URL">
    Paste the URL from your Clay webhook source into the **POST** field.
  </Step>

  <Step title="Add an auth token (optional)">
    If you set an authentication token on the Clay source, paste it into the auth token field. Squid ID sends it on every request as the <code>x-clay-webhook-auth</code> header so Clay only accepts data from you.
  </Step>

  <Step title="Choose which field groups to send">
    Each group (Traits, Social, Company, Job, Location, Experience) has its own toggle. Turn off any group you don't need. The JSON preview on the right updates to match.
  </Step>

  <Step title="Set who and how often">
    Pick the send frequency, routing, and any requirements (see below).
  </Step>

  <Step title="Send a test event">
    Click **Send test event** to push a sample payload to Clay and confirm the source is reachable.
  </Step>

  <Step title="Save">
    Click **Save**. Qualifying visitors now flow to Clay.
  </Step>
</Steps>

## Choose who and how often

The **Delivery** controls decide which identified visitors reach Clay and how often.

* **Send.** *Once per visitor* (the default) sends one row the first time we identify a person, so your Clay table stays one row per contact. *Every identified visit* re-sends on return visits and tags those rows with `is_repeat_visit: true`, so a Clay table can branch net-new versus returning.
* **Who.** Route *all identified visitors*, *any [ICP](/finding-visitors/icp-filtering) match*, *only specific ICPs*, *any high-intent page*, or *only specific high-intent pages*. A table that only wants enterprise accounts can receive just those.
* **Only send when.** Require a company, a LinkedIn profile, or a work or personal email before a visitor is sent. Thin records never reach Clay.

These combine. For example: *once per visitor*, *only specific ICPs*, *must have a work email* sends each new enterprise contact a single time.

## Fields and Squid ID+

Each group lists **Default fields** that come with every identified visitor and **Squid ID+ fields** (the locked rows) that are part of [Squid ID+](/add-ons/squid-id-plus): mobile phone, personal email, home address, demographics, income and net worth, skills and interests, full work history, and extra social profiles.

The Squid ID+ fields are sent automatically for records that are **ID+ unlocked**, either because the website is on [Squid ID+ Automatic](/add-ons/squid-id-plus#turning-on-automatic) or the record was revealed. There is nothing extra to switch on. To drop a whole group from the payload, turn its card off.

<Info>This is the same egress rule as everywhere else in Squid ID: premium contact data is sent only for records you've unlocked, so Clay never receives ID+ data you haven't paid for. For a record that isn't unlocked, only the default fields are sent.</Info>

## Pause or disconnect

* **Pause:** Use the toggle on the Clay card to stop delivery without losing the webhook URL or field setup.
* **Disconnect:** Open the connector and click **Delete**. This removes the webhook URL, auth token, and field config from Squid ID.

## Multiple websites

The connection applies to the website you have selected. If your account owns more than one website, switch the active site and connect each one. Routing, requirements, and field choices are set per website.