-
Notifications
You must be signed in to change notification settings - Fork 380
Add Eagle Eye (Actions) destination docs #7691
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
sade-wusi
merged 3 commits into
segmentio:develop
from
andreshernandez-e2x:feature/eagleeye-actions-docs
Jun 24, 2025
Merged
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
34 changes: 34 additions & 0 deletions
34
src/connections/destinations/catalog/eagleeye-actions/index.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
--- | ||
title: Eagle Eye (Actions) Destination | ||
--- | ||
|
||
{% include content/plan-grid.md name="actions" %} | ||
|
||
[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. | ||
|
||
This destination is maintained by Eagle Eye. For any issues with the destination, [contact their Support team](mailto:[email protected]). | ||
|
||
## Getting started | ||
|
||
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Eagle Eye". | ||
2. Select "Eagle Eye (Actions)" and click **Add Destination**. | ||
3. Select an existing Source to connect to Eagle Eye (Actions). | ||
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. | ||
5. Enter the **Connector URL** and **Connector External Key** from the previous step in the "Eagle Eye (Actions)" destination settings in Segment. | ||
|
||
{% include components/actions-fields.html %} | ||
|
||
### Define mappings to trigger Behavioral Actions | ||
|
||
> 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". | ||
|
||
> 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**. | ||
|
||
1. Within your new Eagle Eye (Actions) destination, head to the Mappings tab and click **New Mapping**. | ||
2. From the action list, select **Trigger Behavioral Action**. | ||
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). | ||
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. | ||
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`. | ||
6. Click on **Next**, type a name for your new mapping and hit **Save** or **Save and enable**. | ||
|
||
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. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hi @andreshernandez-e2x can we reword slightly to improve the grammar in this sentence please?