Zapier empowers businesses to create processes and systems that let computers do what they do best - automating information transfer, allowing humans to be more productive.
Before you start, make sure Zapier supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.
- Navigate to your Zapier dashboard and select “Make A Zap” - you’ll need at least one Zap so you can tell Segment where to route data later on.
Search “Webhooks”, then select “Catch Raw Hook” (Segment POSTs raw data to Zapier using our destination).
- Complete the remaining Webhook set up steps, and Zapier will present you with a custom Webhook URL.
- Repeat step 3 to create as many Webhook URLs as you like.
Remember that each Zapier “trigger” should be connected to an “Action” - i.e. posting the Webhook data to another downstream tool, such as Slack.
- From your Segment UI’s Destinations page click on “Add Destination”.
- Search for “Zapier” in the Catalog, select it, and choose which of your sources to connect the destination to.
- Add your custom Webhook URLs to your destination settings as desired.
- Starting sending data!
Page / Screen
Segment doesn’t perform any transformations or mappings on data you send to Zapier - we send raw payloads. When you specify a “Zap” URL, Segment will send all your
screen events to that Zapier URL. If you also specify any “Page/Screen Zaps” under “Optional Settings” in your Segment settings UI, Segment will send these named
screen events to the specific Webhook URL instead of to the “Zap” URL.
When you specify a “Zap” URL, Segment will send all your track events to that Zapier URL. Leave this setting blank if you do not wish to send all track events to Zapier. As with page/screen events, Segment does not perform any transformations or mappings. If you also specify any “Event Zaps”, Segment will send these events to the specific Webhook URL instead of to the “Zap” URL.
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, Personas 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), Personas sets that value to
When you first create an audience, Personas 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.
Segment lets you change these destination settings from the Segment app without having to touch any code.
Enter the Zaps you want track events to go to. Enter an event name on the left, and a Zap URL on the right.
Enter the Zaps you want page/screen events to go to. Enter an page/screen name on the left, and a Zap URL on the right.
The default Zap URL events and page/screen should be sent to.
This page was last modified: 20 Oct 2020
Questions? Problems? Need more info? Contact us, and we can help!