Send audiences to Airship Attributes

Airship is a customer engagement platform that helps marketers connect with their customers across every stage of the customer lifecycle. The Airship Attributes destination sends customer attributes from Amperity to matching profiles in an Airship project using the Airship Attribute Lists API, where they can be used for segmentation and personalization.

Note

This destination uses the Airship Attribute Lists API .

Beta

The Airship Attributes connector is currently in beta. Contact your Amperity representative to learn more.

The steps required to configure campaigns to send attributes to Airship Attributes.

Note

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

Caution

This destination is available for sending campaign audiences to Airship Attributes 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 Airship Attributes.

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 Airship Attributes as part of a campaign you must choose specific attributes to send.

Airship Attributes supports the following attributes: attributes.

Important

Validate the audience with Airship Attributes by using a sample audience with a very small membership. For example: 10 or 100 members or the minimum audience size recommended by Airship Attributes. Send the sample audience to Airship Attributes and verify the sample audience is correct in Airship Attributes. 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 Airship Attributes. Add a segment, define exclusions and sub-audiences, and then define each audience sent to Airship Attributes.

	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 Airship Attributes 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 Airship Attributes.
	Click Edit attributes to review the attributes that Amperity sends to Airship Attributes. The attributes sent are the airship_identifier column and every additional column in the audience, which Airship applies as an attribute. Each additional column must match an existing attribute in your Airship project. Amperity pre-selects the list of attributes sent to Airship Attributes. The Edit attributes page for Airship Attributes is similar to: Note The Merged Customers table is the default table for sending data to Airship Attributes, 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 Airship Attributes 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.

Airship Attributes requires the airship_identifier field. Every other field is sent as an Airship attribute and must exactly match the ID of an attribute that already exists in your Airship project.

Source attribute	Required?	Destination attribute
airship_identifier	Yes	The identifier Airship matches the row against. Its contents must match the Identifier type configured on the destination: a named user ID, a channel ID, or an email address. Rows with a blank value are dropped and counted as failed.
Additional attributes	No	Each additional field is sent as an Airship attribute, matched to the attribute in your Airship project whose ID is exactly the field name. Values are sent as they appear in Amperity.