Listrak/update documentation #5082
Merged
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
stayseesong
requested changes
Jul 31, 2023
|
|
||
| ## Stream | ||
|
|
||
| Listrak uses our stream Source component to send Segment event data. It uses the server-side `identify` and `track` methods to send data to Segment. These events are then available in any destination that accepts server-side events, and available in a schema in your data warehouse, so you can query using SQL. |
|
|
||
| Listrak always sets the `anonymousId` and the `email` trait to the email address of the contact. | ||
|
|
||
| If a profile field was entered when the email list was added to the integration and the email address has a value for that profile field, the `userId` will be set to that value when sending `identify` events. Otherwise, Listrak will not set the `userId`. The `userId` will not be set for any `track` events. |
There was a problem hiding this comment.
Suggested change
| If a profile field was entered when the email list was added to the integration and the email address has a value for that profile field, the `userId` will be set to that value when sending `identify` events. Otherwise, Listrak will not set the `userId`. The `userId` will not be set for any `track` events. | |
| If you entered a profile field when the email list was added to the integration and the email address has a value for that profile field, the `userId` sets to that value when you send identify events. Otherwise, Listrak won't send the `userId`. The `userId` won't be set for any `track` events. |
Co-authored-by: stayseesong <[email protected]>
Co-authored-by: stayseesong <[email protected]>
Co-authored-by: stayseesong <[email protected]>
stayseesong
requested changes
Aug 1, 2023
|
@colevohs can you please incorporate my suggested changes, and then I can merge the PR. The template is outdated and needs to be updated |
Co-authored-by: stayseesong <[email protected]>
Co-authored-by: stayseesong <[email protected]>
Co-authored-by: stayseesong <[email protected]>
stayseesong
approved these changes
Aug 1, 2023
stayseesong
added
the
content-update
|
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
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
Merge timing