Skip to content

Commit 71cfd09

Browse files
authored
Merge pull request #5466 from segmentio/MStephen024-patch-2
Added FAQ Entry.md
2 parents 62a79dc + 5ca162f commit 71cfd09

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

src/engage/faqs.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -147,3 +147,7 @@ Multiple audience events can trigger for a user if any of the following conditio
147147
## Why am I not seeing standard source events on the Engage source, even though it has been connected through "Unify -> Unify Settings -> Profile Sources" page?
148148

149149
Based on Engage behavior, standard source events such as Page, Track and Identify calls aren't visible on the Engage source. The Engage source tracks and manages events related to audiences and computed traits within the Engage space. This includes events generated by changes in audience membership or computed trait calculations or when a user profile has been created in the Engage space. These are distinct from the typical Page calls, Track calls, or Identify calls (user interaction events) that you would observe in a standard Segment source.
150+
151+
## Why can't I connect the audience/computed trait to an existing destination in my workspace?
152+
153+
Engage will not allow you to connect an audience/computed trait to a destination that is already linked to a [Connections-based source](https://segment.com/docs/connections/sources/). Instead, create a new instance of the destination with the correct Engage space selected as the data source.

0 commit comments

Comments
 (0)