add updates to fullstory cloud mode destination docs #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ndonze-fs
reviewed
Dec 7, 2022
src/connections/destinations/catalog/actions-fullstory-cloud/index.md
Outdated
Show resolved
Hide resolved
src/connections/destinations/catalog/actions-fullstory-cloud/index.md
Outdated
Show resolved
Hide resolved
c80ea20 to
196da66
Compare
ndonze-fs
approved these changes
Dec 7, 2022
src/connections/destinations/catalog/actions-fullstory-cloud/index.md
Outdated
Show resolved
Hide resolved
196da66 to
b9b648d
Compare
GGonryun
pushed a commit
that referenced
this pull request
Dec 12, 2022
* add updates to fullstory cloud mode destination docs (#2) * apply suggested code fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
We've received feedback that customers expect Cloud Mode to "just work" by flipping it on, yet they miss the requirement that users need to be previously-identified using FS.identify. We already made an update to our KB article to call out this requirement more prominently. Here we are doing the same for our Segment Docs
Merge timing
as soon as possible or as soon as its approved