Planhat is an Amplitude Event Streaming Destination. This means you can send a continuous, real-time stream of Amplitude events to Planhat as user activities on the End User, Asset or Project Level with minimal setup.
This guide walks through the key requirements of the connection with Amplitude, and how to configure it.
Contents
How the Connection Works
Remember!
You will need to perform the following steps separately for each Amplitude project you want to push data into Planhat
Amplitude sends all user, event, and group properties along with the event
The maximum size of event data is 1 MB
Matching IDs
The Amplitude user_id matches to the End User externalId within Planhat for associated events. If a user with that externalId doesn't exist within Planhat, a user with that externalId is created
Please ensure that your Planhat End User, Company and/or Asset/Project externalIds match the corresponding ids in Amplitude. In particular, to avoid user duplication, ensure that the Amplitude user_id/email field matches the related Planhat user externalId/email field
Start Pushing Events
Preparing Planhat
Get Tenant Token
To connect Amplitude to Planhat, you'll need to obtain your tenant token
. To do so:
ensure you have Admin permissions in Planhat, or contact an Admin to complete these steps for you
head into Integrations, from the menu in the bottom left
scroll until you see the Amplitude integration and select it
turn the integration on using the toggle at the top
select "Copy to clipboard" to copy your Tenant Token and use it to complete the setup from Amplitude
Preparing Amplitude
In Amplitude, navigate to
Connections
>Destinations
Click
Add Destination
in the top rightSearch to find
Event Stream
>Planhat
and select itEnter a sync name, such as "Planhat Connection", then click
Create Sync
Toggle Status from
Disabled
toEnabled
and paste in your Planhat Tenant TokenEnable the Send Events filter toggle if you wish to send only specific events. You can send all events (leave this toggle
Disabled
), but it is strongly recommended that you filter only to the events you intend to use to drive action in PlanhatWhen you have finished filtering, click Save
Click on the
Mappings
tab >Edit
At minimum, map the externalId or email
Destination Property
to the User ID or EmailAmplitude Property
. Additionally, specifying "companyExternalId" is advisable for example in the event that you have an End User associated with multiple companies, or if End User email domains do not always match Company Related Domains, necessitating creation of End Users from eventsπ Note: if you wish to map your user activities to an object other than the Company, you'll also need to map the Asset or Project externalId
Once you have completed the mapping, click Save
And just like that, your Amplitude Event Stream is up and running! From now on, all the events you specified in your filter on the connection's Settings
tab will now be streamed in real time as user activities to Planhat.
To confirm your Event Stream is up and running, you can head into the Connection at any time, and see what's been pushed from the Delivery
tab.
If events delivered from Amplitude don't match what you've received in Planhat, reach out to Planhat Support.
π Note: remember, just because the event status is Success in Amplitude, doesn't mean that the payload was correctly specified and received successfully by Planhat. That's because Planhat's Analytics Endpoint behaves like a "data sink", issuing 200 (OK) Response Codes regardless of whether data was received successfully.