Custify Destination

1. From the Segment web app, click Catalog.
2. Search for "Custify" in the Catalog, select it, and choose which of your sources to connect the destination to.
3. Enter the "API Key" into your Segment Settings UI which you can find from your Custify Developer area.

If you're not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:

1
analytics.identify('userId123', {
2
  email: 'john.doe@example.com'
3
});

Identify calls will be sent to Custify as customers, with the userId being stored as Custify's user_id. You can view the Customers by going to Customers > People in your Custify app interface.

If you're not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like:

analytics.track('Clicked Login Button')

Track calls will appear in Custify as events with the same name, associated with the correct Company and Customer based on the Identify call.

Track calls require the identify call to be made in advance to be able to link the event to a customer.

To view the events, go to their linked Customer and they are displayed in the activity stream (when filtering the view by System > Events).

If you're not familiar with the Segment Specs, take a look to understand what the Group method does. An example call would look like:

1
analytics.group("0e8c78ea9d97a7b8185e8632", {
2
  name: "Initech",
3
  industry: "Technology",
4
  employees: 329,
5
  plan: "enterprise",
6
  "total billed": 830
7
});

Group calls will be sent to Custify as companies and the identified customer will be linked to the company. You can view Companies by going to Customers > Companies in your Custify app interface

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.

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