Planhat Destination

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

Getting Started

Getting data from Segment to Planhat’s Customer Success Tool is easy.

Once the Segment library is integrated with your product, toggle Planhat on in your Segment destinations, and add your Planhat API Key which you can generate in Planhat under App Settings > API Access.

The Segment Planhat destination is 100% handled through our servers, so you don’t need to bundle their iOS or Android SDKs. Your Segment SDK will be enough.

Planhat supports the identify, page, and track methods at the moment.


Identify

When you identify a user, we’ll pass that user’s information to Planhat with userId as Planhat’s External User ID. Segment’s special traits recognized as Planhat’s standard contact profile fields (in parentheses) are:

  • name (name)
  • title (title)
  • email (email)
  • user_id (externalId)

In addition, all calls will get Segment as ‘source’.

If the userId or traits.email matches an existing Contact in Planhat the Identify-call will automatically be associated with that Contact. Otherwise a new Contact will be created in Planhat. New Contacts received from Segment can either be discarded or manually assigned to a Customer profile in Planhat.


Personas

You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.

Settings

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

Tenant Token

Add your Planhat Tenant Token, which you can find in Planhat under App Settings > API Access

subdomain

Your Planhat API subdomain.


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!