Zendesk Destination

Segment makes it easy to send your data to Zendesk (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Zendesk in the format they understand. Learn more about how to use Zendesk with Segment.

Credentials for our Zendesk Destination

There two ways to authenticate your Zendesk account with Segment so that we can send you data, there is the standard email and password vs. Zendesk Oauth.

For the former, you can enter your email and password in the Zendesk destination panel on your dashboard and for the latter, you should pass the email as ‘email/token’ and the password as ‘token’.

Identify

When you call identify we will insert or update a user record in Zendesk. We’ll use the user email in traits.email to match user records in Zendesk. If there are multiple users matching the email, then no updates are submitted. Note that you must provide a trait for name or first_name and last_name in order for the identify call to send to Zendesk.

Here’s an example:

Note: To limit identified users from receiving a verification email from Zendesk, simply enable the “verified” option in the Zendesk destination settings.

Group

Important: To make group calls, you must be an Administrator in Zendesk.

When you call group we will insert or update an organization in Zendesk. We’ll use the groupId you include in the call to match organization records in Zendesk. If there are multiple organizations matching the name, then no updates are submitted.

Here’s an example:

Every time you call group, we will also link the organization to the user making the request.


Supported Sources and Connection Modes

WebMobileServer
📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.

Settings

Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

Email

Your Zendesk account email. If you’re using oAuth to login, fill in your email/token - e.g. john@gmail.com/token Use the actual word token in your email address if using this method of authentication and then set your password as the actual oAuth token.

Password

Your Zendesk account password or oAuth token.

Subdomain

Your Zendesk subdomain, not including .zendesk.com.

Create Users as Verified

Passes the verify flag set to true on each user upsertion, which will mean customers needn’t confirm their email upon account creation. See here for more information.


If you have any questions or see anywhere we can improve our documentation, please let us know or kick off a conversation in the Segment Community!