Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 0 additions & 2 deletions src/_data/sidenav/main.yml
Original file line number Diff line number Diff line change
Expand Up @@ -81,8 +81,6 @@ sections:
title: 'Spec: Screen'
- path: /connections/spec/track
title: 'Spec: Track'
- path: /connections/spec/alias
title: 'Spec: Alias'
- path: /connections/spec/group
title: 'Spec: Group'
- path: /connections/spec/identify
Expand Down
2 changes: 2 additions & 0 deletions src/connections/spec/alias.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@
title: 'Spec: Alias'
---

> note "Alias is an advanced method"
> The Alias method allows you to explicitly change the ID of a tracked user, however this should only be done when it's required for downstream destination compatibility. See our [Best Practices for Identifying Users](/docs/guides/how-to-guides/best-practices-identify/) for more information.

The `alias` method is used to merge two user identities, effectively connecting two sets of user data as one. This is an advanced method, but it is required to manage user identities successfully in some of our destinations.

Expand Down