Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Update actual steps to Add Source to Engage Space #4130

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 3 commits into from
Feb 21, 2024
Merged

Conversation

lizkane222
Copy link
Contributor

A CSM created a ticket today (https://segment.zendesk.com/agent/tickets/496875) because they and the customer followed the above doc and were confused on how to actually add a source to their Engage Space as the information was inaccurate.

I've edited the steps for Step 3 so that it's accurate to what actually exists within the UI.

Previously :

  1. From your Engage space, go to your space Settings and click Sources.

Changes :

  1. On the left sidebar click Profiles, click Profiles Settings, click the tab Sources tab, and the blue Add Source button.
  2. (only the info below was added to don't checkin apple files #2)
    The flag Replay data is enabled by default, Replay data : Enable this option to replay last month of data into Profiles for every selected source below. When left enabled, 30 days of historical data will be replayed from the source.

A CSM created a ticket today because they and the customer followed the above doc and were confused on how to actually add a source to their Engage Space.

I've edited the steps for Step 3 so that it's accurate to what actually exists within the UI.

Merge timing

  • ASAP once approved

A CSM created a ticket today (https://segment.zendesk.com/agent/tickets/496875) because they and the customer followed the above doc and were confused on how to actually add a source to their Engage Space as the information was inaccurate.

I've edited the steps for Step 3 so that it's accurate to what actually exists within the UI.
@cmastr
Copy link
Contributor

cmastr commented Jan 24, 2024

@lizkane222 does this works till need to be done? This PR is quite old and still in draft state, with merge conflicts. We plan to close this PR on Friday January 26, 2024. If the work still needs to be done, please let us know.

@cmastr cmastr marked this pull request as ready for review January 25, 2024 15:11
@cmastr cmastr requested review from pwseg and rchinn1 as code owners January 25, 2024 15:11
@cmastr cmastr removed the Outdated label Jan 25, 2024
updates to grammar
@cmastr cmastr merged commit f9a5d12 into develop Feb 21, 2024
@cmastr cmastr deleted the lizkane222-patch-5 branch February 21, 2024 15:13
Copy link
Contributor

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants