Update Using Engage Data doc #4666
Merged
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
Updated the terminology in the last paragraph of the "New external identifiers added to a profile" section of the "Using Engage Data" docs.
Currently:
"If this behavior, re-syncing a computed trait or audience when the underlying trait or audience value hasn’t changed, isn’t desired in your system, contact Segment."
Update:
"If you encounter an undesired behavior, such as the re-syncing of a computed trait or audience when the underlying trait or audience value hasn't changed in your system, contact Segment."
Merge timing
Related issues (optional)