Go to the Destinations overview page and click the Add destination button. Select Planhat and click Continue. You can then authenticate Hightouch to Planhat by entering the following required fields into Hightouch:
API Access Token: You can generate an API token under the Settings > Service Accounts section in Planhat.
Tenant UUID: You only need to provide a Tenant UUID if you plan to sync to Metrics or User Activities. You can get your Tenant UUID under in the Developer section in Planhat.
Region: You only need to provide a region if your Planhat app subdomain isn't app. For example, if your app URL is app-us1.planhat.com, then enter us1. If your app URL is app.planhat.com, leave the region blank.
Once you've set up your Planhat destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Planhat destination you want to sync to.
Companies or accounts are your customers.
Depending on your business these might be agencies, schools, other businesses or something else.
Companies can also be your previous customers and or prospects.
To match rows from your model to company in Planhat, you need to select a model column and corresponding Planhat field. You can match on any of the following Planhat fields:
ID
Source ID
External ID
In Insert mode, Planhat automatically generates an identifier for every
new record synced, so there is no need to match an existing record.
Hightouch lets you sync company fields via field mapping.
You can map data from any of your model columns to default and custom company fields.
Ensure your model columns data types match the data types of the fields you want to sync to.
To match rows from your model to enduser in Planhat, you need to select a model column and corresponding Planhat field. You can match on any of the following Planhat fields:
ID
Source ID
External ID
In Insert mode, Planhat automatically generates an identifier for every
new record synced, so there is no need to match an existing record.
Hightouch lets you sync enduser fields via field mapping.
You can map data from any of your model columns to default and custom enduser fields.
Ensure your model columns data types match the data types of the fields you want to sync to.
To match rows from your model to sale in Planhat, you need to select a model column and corresponding Planhat field. You can match on any of the following Planhat fields:
ID
Source ID
External ID
In Insert mode, Planhat automatically generates an identifier for every
new record synced, so there is no need to match an existing record.
Hightouch lets you sync sale fields via field mapping.
You can map data from any of your model columns to default and custom sale fields.
Ensure your model columns data types match the data types of the fields you want to sync to.
To match rows from your model to invoice in Planhat, you need to select a model column and corresponding Planhat field. You can match on any of the following Planhat fields:
ID
Source ID
External ID
In Insert mode, Planhat automatically generates an identifier for every
new record synced, so there is no need to match an existing record.
Hightouch lets you sync invoice fields via field mapping.
You can map data from any of your model columns to default and custom invoice fields.
Ensure your model columns data types match the data types of the fields you want to sync to.
To match rows from your model to license in Planhat, you need to select a model column and corresponding Planhat field. You can match on any of the following Planhat fields:
ID
Source ID
External ID
In Insert mode, Planhat automatically generates an identifier for every
new record synced, so there is no need to match an existing record.
Hightouch lets you sync license fields via field mapping.
You can map data from any of your model columns to default and custom license fields.
Ensure your model columns data types match the data types of the fields you want to sync to.
Syncing metrics lets you track dimensional data in Planhat.
While user activity says a lot about user engagement, it doesn't always reflect the value created.
Dimension data is a set of model level metrics (Company by default) to understand how well your customers are doing, and the value they get out of your service.
To ensure syncs send each event, your event model must use a truly unique primary key. See the events syncs documentation for more information.
Syncing user activites lets you track endusers's actions in Planhat.
Keeping track of your endusers activity is an important part of the Customer Success effort.
To ensure syncs send each event, your event model must use a truly unique primary key. See the events syncs documentation for more information.
When receiving user activities, Planhat's API always returns an OK successful response even if the user activity payload contains invalid data.
You can find these failed user events in Planhat in Customer Intelligence > Trends & Analytics > User Activities by clicking the Show failed activities icon.
To date, our customers haven't experienced any errors while using this destination. If you run into any issues, please don't hesitate to . We're here to help.
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.