Send audiences to Eagle Eye Audiences

Eagle Eye is a loyalty and promotions platform. Its AIR platform manages loyalty wallets that track each customer’s earning and spending activity in a loyalty program.

Note

This destination uses the Eagle Eye AIR Audiences API, which is part of the Eagle Eye Resource API , and looks up wallets with the Eagle Eye AIR Wallet API .

Beta

The Eagle Eye Audiences connector is in beta, and Eagle Eye labels the AIR Audiences API as beta. Contact your Amperity representative to learn more.

The steps required to configure campaigns to send audiences to Eagle Eye.

Note

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

Caution

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

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

Eagle Eye supports the following attributes: audiences.

Important

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

	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 Eagle Eye 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 Eagle Eye.
	Click Edit attributes to review the attributes that Amperity sends to Eagle Eye. identity values Amperity pre-selects the list of attributes sent to Eagle Eye. The Edit attributes page for Eagle Eye is similar to: Note The Merged Customers table is the default table for sending data to Eagle Eye, 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 Eagle Eye 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.

Eagle Eye Audiences requires the identity_value attribute, and Amperity sends only that attribute.

Source attribute	Required?	Destination attribute
identity_value	Yes	A loyalty identity that is attached to the person’s wallet in Eagle Eye, such as a loyalty card number, an email address, or whatever identity type your company unit is configured for. Amperity uses it to find the person’s wallet. The destination attribute must be named identity_value, in lower case. Map an attribute that holds values exactly as Eagle Eye stores them, without hashing them.

Each campaign send adds the people who recently joined the audience to the audience in Eagle Eye, and removes the people who left. A change is sent again on later sends for a few days, which has no effect in Eagle Eye. Every person must already have an Eagle Eye wallet that holds their identity value. A person without a wallet is reported as a failed row.

Caution

Each send to this destination also has an Audience action setting. delete permanently deletes the audience in Eagle Eye AIR, even while an active AIR campaign uses it. Leave it set to upsert unless you mean to delete the audience, and see Audience actions for the other settings, such as Audience name, that you choose for each send.