Add Eagle Eye (Actions) destination docs #7691
Conversation
|
|
||
| ### 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". |
There was a problem hiding this comment.
hi @andreshernandez-e2x can we reword slightly to improve the grammar in this sentence please?
|
note for @forstisabella or whoever reviews this from the Docs team. The Destination itself is pretty simple and allows customers to trigger a behavioral action in Eagle Eye. I feel like this doc could benefit from a better explanation of how the Eagle Eye Source and Eagle Eye Destination work together, and what use-case they can be used for. |
|
Thanks for checking @joe-ayoub-segment. Also thanks @sade-wusi, I'm okay with those changes you proposed. |
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Proposed changes
This is the initial documentation for the Eagle Eye (Actions) destination, requested as part of the approval process to go into public beta.
Merge timing
Related issues (optional)
No open related issues at this time, action was merged and currently in private beta.