# Clay Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Clay** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.

Use website visitor tracking in [Clay](https://clay.com/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) to identify and understand companies visiting your website, track their engagement patterns, and turn anonymous traffic into actionable leads.

This destination is maintained by Clay. For any issues with the destination, [contact the Clay Support team](mailto:support@clay.com).

## Getting started

1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog) search for "Clay".
2. Select Clay and click **Add Destination**.
3. Select an existing Source to connect to Clay (Actions).
4. Open your [Clay dashboard](https://app.clay.com), and select **Settings**.
5. Navigate to **Website tracking** and select your website connection.
6. Select **Segment**, and then copy your **Connection key** and **Secret key**.
7. Return to the Segment app and enter these keys in your Clay destination settings page.

## Destination Settings

| Field          | Description              | Required | Type     |
| -------------- | ------------------------ | -------- | -------- |
| Connection Key | Your Clay connection key | Yes      | string   |
| Secret Key     | Your Clay secret key     | Yes      | password |

## Available Presets

Clay has the following presets

| Preset Name | Trigger              | Default Action |
| ----------- | -------------------- | -------------- |
| Track Calls | Event type = "track" | Track          |
| Page Visit  | Event type = "page"  | Page Visit     |

## Available Actions

Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Clay-supported actions:

> \[!NOTE]
>
> Individual destination instances have support a maximum of 50 mappings.

* [Page Visit](#page-visit-1)
* [Track](#track-9)

### Page Visit

Send a page event to Clay

Page Visit is a **Cloud** action. The default Trigger is `type = "page"`

| Field        | Description                               | Required | Type   |
| ------------ | ----------------------------------------- | -------- | ------ |
| Event Name   | The name of the page                      | No       | STRING |
| Timestamp    | The timestamp of the page event           | No       | STRING |
| Page         | Information about the current page        | No       | OBJECT |
| IP Address   | IP address of the user                    | Yes      | STRING |
| User Agent   | User-Agent of the user                    | No       | STRING |
| Anonymous ID | The anonymous ID associated with the user | No       | STRING |
| User ID      | The ID associated with the user           | No       | STRING |
| MessageId    | The Segment messageId                     | Yes      | STRING |
| Properties   | Properties to associate with the event    | No       | OBJECT |

### Track

Send a track event to Clay

Track is a **Cloud** action. The default Trigger is `type = "track"`

| Field        | Description                               | Required | Type   |
| ------------ | ----------------------------------------- | -------- | ------ |
| Event Name   | The name of the event                     | Yes      | STRING |
| Timestamp    | The timestamp of the track event          | No       | STRING |
| Page         | Information about the current page        | No       | OBJECT |
| IP Address   | IP address of the user                    | Yes      | STRING |
| User Agent   | User-Agent of the user                    | No       | STRING |
| Anonymous ID | The anonymous ID associated with the user | No       | STRING |
| User ID      | The ID associated with the user           | No       | STRING |
| MessageId    | The Segment messageId                     | Yes      | STRING |
| Properties   | Properties to associate with the event    | No       | OBJECT |

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

> \[!NOTE]
>
> Real-time audience syncs to Clay  may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field          | Description              | Required | Type     |
| -------------- | ------------------------ | -------- | -------- |
| Connection Key | Your Clay connection key | Yes      | string   |
| Secret Key     | Your Clay secret key     | Yes      | password |