Send audiences to Amplitude

Amplitude is a self-service digital analytics platform to understand your users, drive conversions, and increase engagement, growth and revenue.

Beta

The Amplitude connector is in beta. Contact your Amperity representative to learn more.

A campaign sends an audience to Amplitude as a behavioral cohort, so product teams can run funnel, retention, and feature-adoption analyses against an Amperity-resolved audience inside Amplitude.

Note

This destination uses several of Amplitude’s REST APIs : the HTTP V2 and Batch Event Upload APIs for events, the Identify and Group Identify APIs for user and group properties, the Behavioral Cohorts API for audiences, and the User Privacy API for deletion requests.

In cohort-push mode, one orchestration or campaign maintains one Amplitude behavioral cohort, named by the Cohort name setting. Amperity creates the cohort on the first run and updates the same cohort on later runs of that name.

Every cohort’s first run sends the full audience, in either Cohort sync mode, because Amplitude assigns the cohort’s identifier only on that first full send. From the second run onward, replace keeps re-sending the full audience and append sends only the members added and removed since the last run.

Important

Amplitude only recognizes identities it has already seen. An identity that has never been sent through user-properties or events mode is not matched into a cohort — Amplitude reports it as invalid, and Amperity reports those rows as failed. Send an audience’s identities as user properties or events before, or alongside, pushing them into a cohort.

If the cohort is deleted in Amplitude between runs, the next run creates a replacement cohort under the same name and continues from there. The replacement is a new cohort, so anything in Amplitude that referenced the deleted one — a chart, a saved analysis — needs to be pointed at the new cohort.

An audience that is empty on a given run is not sent: Amplitude rejects an empty membership, so the cohort keeps the membership it already had. This is reported as a warning in the run details rather than as a failure.

The steps required to configure campaigns to send audiences to Amplitude.

Note

Ask your DataGrid Operator or your Amperity representative for help configuring Amplitude as a destination to which you can send campaigns for customer activation.

Caution

This destination is available for sending campaign audiences to Amplitude after it is configured by a Datagrid Operator or your Amperity representative.

If this destination cannot be selected from the campaigns editor or activations canvas ask your Datagrid Operator or Amperity representative to configure a destination for sending campaign audiences to Amplitude.

Build a segment

Use the Segment Editor to build any audience using a series of drop-downs and picklists.

As you define the attribute profile for an audience be sure to refresh segment insights to view audience size and to see the value it brings to your business.

When the segment is ready, activate it, and then use it use it in a campaign to send to your preferred destinations for customer activation.

About segments that use the sub-audience editor

You can use any attribute that is in your customer 360 database to define your audience.

When sending the list of customers who belong to this audience to Amplitude as part of a campaign you must choose specific attributes to send.

Amplitude supports the following attributes: audiences.

Important

Validate the audience with Amplitude by using a sample audience with a very small membership. For example: 10 or 100 members or the minimum audience size recommended by Amplitude. Send the sample audience to Amplitude and verify the sample audience is correct in Amplitude. Make adjustments if necessary. Only send full audiences after validation is complete.

Add to a campaign

Use the campaign editor to configure Amperity to send data to Amplitude. Add a segment, define exclusions and sub-audiences, and then define each audience sent to Amplitude.

	Open the Campaign Editor. This is available from the Campaigns page. Click the Create campaign button in the top right corner of the page.
	Assign Amplitude as a destination for at least one treatment group. Note You may need to edit the attributes for the sub-audience to ensure Amperity is sending the right data to Amplitude.
	Click Edit attributes to review the attributes that Amperity sends to Amplitude. Amplitude accepts a single identifier per member and no other attributes, so the only attribute sent for this campaign is the one mapped to identity_value. Amperity pre-selects the list of attributes sent to Amplitude. The Edit attributes page for Amplitude is similar to: Note The Merged Customers table is the default table for sending data to Amplitude, even though segments are often built against the Customer 360 table. This is by design. The Merged Customers table is the underlying table for customer profile data and is the source for all customer profile data that exists within the Customer 360 table.

Configure default attributes

Each unique destination configured to send treatment group audiences to Amplitude has a set of default attributes.

Configure default attributes by clicking the Default attributes link next to the Create campaign button on the Campaigns page.

The source table defaults to the Merged Customers table for most attributes. This is configurable.

Amplitude sends a single identifier per member and no other attributes, because cohort membership in Amplitude carries no properties. Map the default attribute for the campaign to the column that holds the identifier, and name it identity_value.

Source attribute	Required?	Destination attribute
identity_value	Yes	The identifier for each member of the audience. It must match the identifier type chosen in the Cohort identifier type setting when this destination was configured — either Amplitude’s own assigned identifier or the one your own systems assign. A member whose value is empty is dropped and reported as a failed row.

Important

Amplitude only matches identifiers it already knows. An identifier that has never reached Amplitude through a user-properties or events orchestration is reported as invalid and is not added to the cohort.