Amplitude
Use GrowthLoop audiences for Amplitude user-property membership.
Connect this destination to export audience membership onto an Amplitude user property, for use in Amplitude analysis.
This destination writes to your Amplitude account and is a good fit when you want to:
- Match your warehouse identifier to the Amplitude
user_id - Store audience names on an array-type user property
This maps to GrowthLoop Audiences:
| Use it for | Audiences |
|---|---|
| Writing audience membership onto Amplitude user profiles | ✓ |
This destination matches User ID only. It does not resolve email or device IDs to Amplitude users.
Prerequisites
Make sure you have:
- An Amplitude project with an API key and secret key. Find them in Amplitude Settings → Projects.
- A warehouse identifier that matches the
user_idyour Amplitude project uses.
NoteAmplitude creates the
gl_audiencesuser property on the first write. You do not need to create it in Amplitude first.
Set up Amplitude as a destination
- In GrowthLoop, click the Destinations tab on the left sidebar.
- Click New Destination in the upper right corner.
- Search for Amplitude and click Add Amplitude.
- Enter the required information, then click Create.
| Field | Description |
|---|---|
| Destination Name | Name this destination in GrowthLoop. Use a name so your team recognizes its purpose, like "Amplitude Audiences". |
| Sync Frequency | Set the default export frequency (for example, daily or weekly). You can override this setting for individual exports. |
| API Key | Your Amplitude project API key. |
| Secret Key | Your Amplitude project secret key. GrowthLoop uses it only for a read-only credential check. |
| Region | us or eu, matching your Amplitude data residency. Defaults to us. |
| Audience Property (optional) | Array-type user property that stores audience membership. Defaults to gl_audiences. |
GrowthLoop validates the connection with a read-only call to the Amplitude Export API. Amplitude then appears in your list of connected destinations.
Export to Amplitude
From within GrowthLoop, export from an audience. See Export an audience if you need more information on these steps.
After building or selecting an audience, click Export, then search for Amplitude.
Map identifiers
Map User ID to the warehouse column that matches Amplitude user_id.
Configure the export
- Export Name: GrowthLoop populates this with your audience name. Amplitude stores that name on the user property.
- Campaign Type: Choose a one-time export or an ongoing export.
- Export Schedule: Set the frequency, start date, and end date.
Export behavior
This is what GrowthLoop writes when you export an audience.
| Behavior | What happens |
|---|---|
| What GrowthLoop writes | Audience names on an Amplitude array-type user property. Direction is GrowthLoop → Amplitude. |
| When it runs | GrowthLoop sends the export as a batch on the next successful run. An export that starts Now runs within about 15 minutes. |
| Identify API | GrowthLoop sends one Identify call per contact. |
| Adds | GrowthLoop appends the audience name to the audience property array. |
| Removals | GrowthLoop removes that audience name from the array. Other audience names on the same user stay in place. |
| User ID only | GrowthLoop does not resolve email or device IDs. |
| Audience property | Amplitude creates gl_audiences (or your custom property) automatically on the first write. |
| One-time exports | GrowthLoop appends the audience name once and does not remove anyone later. |
| Ongoing adds and removals | Ongoing exports append contacts who enter and remove that audience name when they leave. GrowthLoop does not delete the Amplitude user. |
Confirm the export was successful
When the run finishes, confirm you can use the data in Amplitude.
- Audience export: Open User Look-Up and search for a
user_idfrom the export. Confirm the audience name appears on thegl_audiencesuser property, or on the custom property you configured.
In GrowthLoop, review counts on the audience Exports tab. See Export an audience for more information.
Congrats on successfully exporting to Amplitude!
Troubleshooting
These are the issues we see most often. You can always email us at [email protected] for help.
| Problem | Cause | Resolution |
|---|---|---|
| Connection fails to validate | API Key and Secret Key are from different projects | Confirm both keys belong to the same Amplitude project |
| Users do not update | Region does not match data residency, or User ID does not match Amplitude user_id | Set Region to us or eu to match the project, and map User ID to Amplitude user_id |
Updated 17 days ago