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.
…even though it has been connected through "Unify -> Unify Settings -> Profile Sources" page?
Why am I not seeing the standard source events on the Engage source, even though it has been connected through "Unify -> Unify Settings -> Profile Sources" page?
Based on Engage behavior, standard source events such as page,track and identify calls are not directly visible on the Engage source. The Engage source is specifically designed to track and manage 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.
Merge timing
Related issues (optional)