EnjoyHQ Destination

EnjoyHQ helps UX and product teams learn from customers faster by streamlining their customer research process. EnjoyHQ makes it easy to centralize, organize and share all their customer insights and user research data in one place.

This destination is maintained by EnjoyHQ. For any issues with the destination, contact the EnjoyHQ support team.

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “EnjoyHQ” in the Destinations Catalog, and select the EnjoyHQ destination.
3. Choose which Source should send data to the EnjoyHQ destination.
4. Go to the EnjoyHQ’s integrations page, find Segment and create a new API key.
5. Enter the API Key in the EnjoyHQ destination settings in the Segment web app.

Identify

If you aren’t familiar with the Segment Spec, take a look at the Identify method documentation to learn about what it does. An example call would look like:

analytics.identify('userId123', {
  email: 'john.doe@example.com',
  age: 37,
  role: "admin",
  "company.name" : "Umbrella Corp",
  "company.number of employees" : 120
  }
});

Segment sends Identify calls to EnjoyHQ as an identify event. These events can create or update an existing customer profile with a matching email address. Data imported using Segment Identify calls is merged with the data already stored in your EnjoyHQ account.

You can find profiles connected to at least one document in the People tab using the global search. You can also find any profile (connected or not) when you associate a customer with a piece of feedback.

Engage

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.

Settings

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