Clay Destination
Use website visitor tracking in Clay 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.
- From your workspace's Destination catalog page search for "Clay".
- Select Clay and click Add Destination.
- Select an existing Source to connect to Clay (Actions).
- Open your Clay dashboard, and select Settings.
- Navigate to Website tracking and select your website connection.
- Select Segment, and then copy your Connection key and Secret key.
- Return to the Segment app and enter these keys in your Clay destination settings page.
Your Clay connection key
Your Clay secret key
Clay has the following presets
| Preset Name | Trigger | Default Action |
|---|---|---|
| Track Calls | Event type = "track" | Track |
| Page Visit | Event type = "page" | Page Visit |
Build your own Mappings. Combine supported triggers with the following Clay-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Send a page event to Clay
Page Visit is a Cloud action. The default Trigger is type = "page"
Optional
The name of the page
Optional
The timestamp of the page event
Optional
Information about the current page
IP address of the user
Optional
User-Agent of the user
Optional
The anonymous ID associated with the user
Optional
The ID associated with the user
The Segment messageId
Optional
Properties to associate with the event
Send a track event to Clay
Track is a Cloud action. The default Trigger is type = "track"
The name of the event
Optional
The timestamp of the track event
Optional
Information about the current page
IP address of the user
Optional
User-Agent of the user
Optional
The anonymous ID associated with the user
Optional
The ID associated with the user
The Segment messageId
Optional
Properties to associate with the event
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an 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.
Real-time to batch destination sync frequency
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.
Segment lets you change these destination settings from the Segment app without having to touch any code.
Your Clay connection key
Your Clay secret key