Skip to content

Commit f76dac8

Browse files
authored
Merge pull request #7744 from andreshernandez-e2x/fix/EESD-16_2
Fix typos for Eagle Eye (Actions) documentation
2 parents 31b6092 + e582116 commit f76dac8

File tree

1 file changed

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

1 file changed

+10
-10
lines changed

src/connections/destinations/catalog/eagleeye-actions/index.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -5,23 +5,23 @@ id: 682db61f6c600fdb90251392
55

66
{% include content/plan-grid.md name="actions" %}
77

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.
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.
99

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.
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 behavioral actions in Eagle Eye.
1111

12-
> warning ""
13-
> This destination must be used in tandem with a corresponding Eagle Eye Source to trigger behaviorial actions in Eagle Eye.
12+
> warning "Required Source Integration"
13+
> This destination must be used in tandem with a corresponding Eagle Eye Source to trigger behavioral actions in Eagle Eye.
1414
15-
This destination is maintained by Eagle Eye. For any issues with the destination, [contact their Support team](mailto:support@eagleeye.com).
15+
This destination is maintained by Eagle Eye. For any issues with the destination, [contact their Support team](mailto:support@eagleeye.com){:target="_blank"}.
1616

1717
## Getting started
1818

1919
To set up the Eagle Eye (Actions) destination in Segment:
2020

21-
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank} search for "Eagle Eye".
21+
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank"} search for "Eagle Eye".
2222
2. Select "Eagle Eye (Actions)" and click **Add Destination**.
2323
3. Select an existing Source to connect to Eagle Eye (Actions).
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.
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.
2525
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.
2626

2727
{% include components/actions-fields.html %}
@@ -30,15 +30,15 @@ To set up the Eagle Eye (Actions) destination in Segment:
3030

3131
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".
3232

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**.
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**.
3434

3535
To map incoming event data and trigger behavioral actions in the Eagle Eye AIR dashboard, follow these steps:
3636

3737
1. In the Eagle Eye (Actions) destination, go to the Mappings tab and click **New Mapping**.
3838
2. From the action list, select **Trigger Behavioral Action**.
3939
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.
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.
4141
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`.
4242
6. Click **Next**, give the mapping a name and hit **Save** or **Save and enable**.
4343

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.
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)