Skip to content
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.

Sign up for GitHub

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

Add recommendation to ID Syncs page about Segment prop > destination prop mappings #7460

Merged
merged 2 commits into from
Feb 27, 2025
Merged

Add recommendation to ID Syncs page about Segment prop > destination prop mappings #7460

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
21284ae
Update id-sync.md
forstisabella Feb 24, 2025
5cfa0e6
Update id-sync.md
forstisabella Feb 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions src/engage/trait-activation/id-sync.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,7 @@ With Customized setup, you can choose which identifiers you want to map downstre
- ID Sync used on existing audience destinations or destination functions won't resync the entire audience. Only new data flowing into Segment follows your ID Sync configuration.
- Segment doesn't maintain ID Sync history, which means that any changes are irreversible.
- You can only select a maximum of three identifiers with an `All` strategy.
- Segment recommends that you map Segment properties to destination properties using [Destination Actions](/docs/connections/destinations/actions/#components-of-a-destination-action) instead of ID Sync.


## FAQs
Expand Down