Skip to content

Add Engage Source FAQ #6318

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
merged 2 commits into from
Apr 9, 2024
Merged

Add Engage Source FAQ #6318

merged 2 commits into from
Apr 9, 2024

Conversation

Panandhan22
Copy link
Contributor

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

…even though it has been connected through "Unify -> Unify Settings -> Profile Sources" page?
@Panandhan22 Panandhan22 marked this pull request as ready for review April 2, 2024 00:27
@Panandhan22 Panandhan22 requested a review from pwseg as a code owner April 2, 2024 00:27

## 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
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.

@pwseg pwseg added the content-update updates to content that are not new features, includes grammar fixes, added notes label Apr 9, 2024
@pwseg pwseg changed the title Why am I not seeing the standard source events on the Engage source, … Add Engage Source FAQ Apr 9, 2024
@pwseg pwseg merged commit 4c3f7fe into develop Apr 9, 2024
@pwseg pwseg deleted the Panandhan22-patch-10 branch April 9, 2024 17:44
Copy link
Contributor

github-actions bot commented Apr 9, 2024

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content-update updates to content that are not new features, includes grammar fixes, added notes KCS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants