Supported syncing
For more information about sync modes, refer to the sync modes docs.
Connect to Amplitude
Go to the Destinations overview page and click the Add destination button. Select Amplitude and click Continue. You can then authenticate Hightouch to Amplitude by entering these fields into Hightouch:- API Key: You can find your API key by following these instructions in Amplitude’s docs.
- Region: This is either a Standard server or EU residency server.
Sync configuration
Once you’ve set up your Amplitude 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 Amplitude destination you want to sync to.Objects
Hightouch can sync data to either User and Group objects. A dropdown is available to select between Users and Groups when configuring an Amplitude sync. This integration only supports the Upsert mode. In this mode, Hightouch inserts new users or groups into Amplitude and keeps all user attributes up-to-date.Record matching
For user objects, map at least one of Amplitude User ID and Amplitude Device ID. Map both when your model mixes known and anonymous users: rows that carry either identifier are sent, rather than only the rows that carry the one identifier you picked. See Amplitude’s docs for more on identifying users. Hightouch sends one identifier per row. When a row has values for both, the first identifier in the order you mapped them wins, and the other isn’t sent for that row. Order the mappings so your preferred identifier comes first, usually Amplitude User ID, so a known user isn’t identified by their device. Rows with no value for any mapped identifier are rejected. Hightouch matches rows from your model to Amplitude groups by Group Value. Select the model column that contains these values if you are syncing groups.Field mapping
You can sync columns from your source to Amplitude’s default and custom fields. User properties only apply on the next event after the property has been changed, and don’t apply retrospectively. For more information, check out Amplitude’s FAQ.Delete behavior
The delete behavior you select dictates what to do when a row no longer appears in your model’s query results. You have the following options for Amplitude objects:Events
Hightouch supports sending events of a given name, for example,Signed Up. Enter this name and choose the model column containing either the user ID or device ID. You can also select the model column containing the event timestamp. If the timestamp field is empty, Hightouch uses the time the event arrives at the server.
Field mapping
Hightouch allows you to pass data to the default properties and the custom event properties of an Amplitude event.Cohorts
Hightouch can sync data to Behavioral Cohorts in Amplitude.Record matching
Hightouch matches rows from your model to Amplitude users by User ID or Amplitude ID. Select the model column that contains these values if you are syncing to cohorts. See Amplitude’s docs for more on behavioral cohorts.Creating new Cohorts
Hightouch can Create a new cohort when syncing to Amplitude cohorts. Hightouch will create a single placeholder user when creating a new cohort, and then sync the mapped identifiers to your newly created cohort.Tips and troubleshooting
To see the exact API requests and responses from each sync run, use the live debugger. To get notified by Slack, PagerDuty, SMS, or email when a sync fails, set up sync alerts. If you run into an issue this page doesn’t cover, .For Hightouch platform error codes related to Amplitude, see Error codes:
Other destinations.