Skip to content

Commit 2b3da55

Browse files
authored
Rewording + added context on using destination with Eagle Eye Source
1 parent 9c68ba1 commit 2b3da55

File tree

1 file changed

+21
-11
lines changed
  • src/connections/destinations/catalog/eagleeye-actions

1 file changed

+21
-11
lines changed
Lines changed: 21 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,34 +1,44 @@
11
---
22
title: Eagle Eye (Actions) Destination
3+
id: 682db61f6c600fdb90251392
34
---
45

56
{% include content/plan-grid.md name="actions" %}
67

7-
[Eagle Eye](https://eagleeye.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} delivers real-time loyalty and promotions solutions for enterprise brands, enabling seamless integration with leading customer data platforms and marketing activation tools. Their platform connects digital and in-store experiences, accelerating personalization and campaign delivery through extensible APIs and pre-built connectors.
8+
[Eagle Eye](https://eagleeye.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} delivers real-time loyalty and promotions solutions for enterprise brands, enabling seamless integration with leading customer data platforms and marketing activation tools. The platform connects digital and in-store experiences, accelerating personalization and campaign delivery through extensible APIs and pre-built connectors.
9+
10+
This integration requires both an Eagle Eye Source and Destination. The source sends events into Segment, and the destination processes those events to trigger specific behaviorial actions in Eagle Eye.
11+
12+
> warning ""
13+
> This destination must be used in tandem with a corresponding Eagle Eye Source to trigger behaviorial actions in Eagle Eye.
814
915
This destination is maintained by Eagle Eye. For any issues with the destination, [contact their Support team](mailto:[email protected]).
1016

1117
## Getting started
1218

19+
To set up the Eagle Eye (Actions) destination in Segment:
20+
1321
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Eagle Eye".
1422
2. Select "Eagle Eye (Actions)" and click **Add Destination**.
1523
3. Select an existing Source to connect to Eagle Eye (Actions).
16-
4. Set up your EE Connector for Segment by following the [CDP and MAP Connectors](https://developer.eagleeye.com/eagleeye-developer/docs/eagle-eye-connect-cdp-map) guide, along with the [Segment](https://developer.eagleeye.com/docs/segment) specific page for information that needs to be provided.
17-
5. Enter the **Connector URL** and **Connector External Key** from the previous step in the "Eagle Eye (Actions)" destination settings in Segment.
24+
4. Set up your EE Connector for Segment by following the [CDP and MAP Connectors guide](https://developer.eagleeye.com/eagleeye-developer/docs/eagle-eye-connect-cdp-map){:target="_blank”}. You'll also need to refer to the [Segment-specific page](https://developer.eagleeye.com/docs/segment){:target="_blank”} for additional information required during setup.
25+
5. Go to the Eagle Eye (Actions) destination settings in Segment and enter the **Connector URL** and **Connector External Key** obtained in the previous step.
1826

1927
{% include components/actions-fields.html %}
2028

2129
### Define mappings to trigger Behavioral Actions
2230

23-
> This guide makes the assumption you're taking advantage of the Eagle Eye Connector for Segment as well to send events into Segment. Still, any event is valid as long as it contains properties to be used "User identity value" and (optionally, when needed) "Wallet transaction reference".
31+
This guide assumes you're using the Eagle Eye Connector for Segment to send events. Any event is considered valid as long as it includes the properties "User identity value" and (optionally) "Wallet transaction reference".
32+
33+
To set this up, you must first configure [Social Behavioral Action Triggers](https://developer.eagleeye.com/eagleeye-developer/docs/segment#set-up-social-behavioural-action-triggers){:target="_blank”} within the Eagle Eye AIR dashboard. You can find this under **Triggers > Search** / **Create Behavioral Action**.
2434

25-
> To set this up you must first [Set up Social Behavioral Action Triggers](https://developer.eagleeye.com/eagleeye-developer/docs/segment#set-up-social-behavioural-action-triggers) within the Eagle Eye AIR dashboard. You can find this under **Triggers** > **Search** / **Create Behavioral Action**.
35+
To map incoming event data and trigger behavioral actions in the Eagle Eye AIR dashboard, follow these steps:
2636

27-
1. Within your new Eagle Eye (Actions) destination, head to the Mappings tab and click **New Mapping**.
37+
1. In the Eagle Eye (Actions) destination, go to the Mappings tab and click **New Mapping**.
2838
2. From the action list, select **Trigger Behavioral Action**.
29-
3. Define your event trigger conditions. E.g.: if a behavioral action should only trigger for customers who just joined the program, you could set "Event Type is Track" and "Event Name is EE Loyalty Program Joined" (or any other event that contains the information you need).
30-
4. Under **Map fields**, ensure at least "User identity value" and "Behavioral Action trigger reference" are set. The trigger reference will be the same you set within the Eagle Eye AIR dashboard when creating your Behavioral Action.
31-
5. (Optional) If your Behavioral Action requires a "Wallet transaction reference", populate it from one of the event fields as well. E.g.: an event property that may contain the transaction reference, such as `properties.order_id`.
32-
6. Click on **Next**, type a name for your new mapping and hit **Save** or **Save and enable**.
39+
3. Define your event trigger conditions. For example, if you want to trigger an action only for customers who just joined the program, select "Event Type is Track" and "Event Name is EE Loyalty Program Joined" (or any other event that contains the information you need).
40+
4. Under **Map fields**, ensure that at least "User identity value" and "Behavioral Action trigger reference" are mapped. The trigger reference will be the same as the one set within the Eagle Eye AIR dashboard when creating the behavioral action.
41+
5. (Optional) If your behavioral action requires a "Wallet transaction reference", you can pull it from one of the event fields. For example, an event property that may contain the transaction reference, such as `properties.order_id`.
42+
6. Click **Next**, give the mapping a name and hit **Save** or **Save and enable**.
3343

34-
For more information on events sent through the Eagle Eye Connector for Segment and their properties, refer to the [Data Model](https://developer.eagleeye.com/eagleeye-developer/docs/segment#data-model) documentation.
44+
For more information on events sent through the Eagle Eye Connector for Segment and their properties, refer to the [Data Model](https://developer.eagleeye.com/eagleeye-developer/docs/segment#data-model){:target="_blank”} documentation.

0 commit comments

Comments
 (0)