Zapier Source
Source Info
- The Zapier Source is an Event Cloud source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
- This source is in Beta
Zapier lets teams automate workflows across apps without code. The Zapier source lets you send Segment events directly from Zaps.
This source is maintained by Zapier. For any issues with the source, contact the Zapier support team.
To set up the Zapier source in your Segment workspace, follow these steps:
- From your workspace's Sources catalog page, click Add Source.
- Search for "Zapier" in the Sources Catalog, select Zapier, and click Add Source. Alternatively, you can create a source from a Zap using the Create Source action in Zapier.
- Give the Source a name and configure any other settings.
- Click Add Source to save your settings.
- You can now send events to the source from your Zaps. You'll need to use the Send Event action in Zapier.
- In Zapier, create or open a Zap that uses the Segment app, then select your Source. Zapier uses the Source Write Key to send events using the HTTP API.
Zapier sends events to Segment using the HTTP API. You can send Track, Identify, Page, Screen, Group, or Alias events. These events are available in downstream destinations that are configured with your source.
Zapier includes userId when provided. If a known user ID isn't available, Zapier can send anonymousId to support pre-login activity tracking.
The following table lists events that Zapier can send to Segment.
| Event name | Description |
|---|---|
| Track | Records a user action with properties. |
| Identify | Associates traits with a known user. |
| Page | Records a page view. |
| Screen | Records a screen view. |
| Group | Associates a user with a group. |
| Alias | Links two user identifiers. |
The following table lists common fields that can be included with Zapier events. You can also send a raw JSON object as the event payload by selecting the "Use raw JSON" option in the "Payload mode" dropdown.
| Property name | Description |
|---|---|
userId | Known identifier for the user. |
anonymousId | Identifier for an unknown user. |
event | Track event name. |
properties | Key-value properties for track, page, or screen. |
traits | Key-value traits for identify or group. |
name | Page or screen name. |
category | Page or screen category. |
groupId | Group identifier. |
previousId | Previous identifier for alias. |
context | Context object such as ip or locale. |
timestamp | ISO 8601 timestamp. |
messageId | Unique ID used for deduplication. |
After the source is set up, connect it to Destinations.
Log in to your downstream tools and confirm events appear as expected with the properties you use. If events and properties don't appear, check the Event Delivery tool and refer to the relevant destination documentation for troubleshooting.
If there are any issues with how the events arrive to Segment, contact the Zapier support team.