Skip to content

Correct Amplitude/Alias description. #1492

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.

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

Merged
merged 5 commits into from
Mar 31, 2021
Merged

Correct Amplitude/Alias description. #1492

merged 5 commits into from
Mar 31, 2021

Conversation

brennan
Copy link
Contributor

@brennan brennan commented Mar 30, 2021

Proposed changes

  • Segment has not sent client-side Alias requests to Amplitude since September 2019. This change removes the incorrect information related to how Segment sends Alias to Amplitude and replaces it with a description of what we actually do.

Merge timing

  • Discovered this issue while looking into STRAT-641.

@netlify
Copy link

netlify bot commented Mar 30, 2021

Deploy preview for segment-docs ready!

Built with commit 609e012

https://deploy-preview-1492--segment-docs.netlify.app

By default, Segment does **NOT** send Alias events to Amplitude. To forward Alias events from Segment, go to your Amplitude destination settings in the Segment web app, and set the **Enable Alias** setting to "on". Once enabled, Segment forwards both client-based and server-based Alias calls. Segment processes _all_ Alias calls before sending them to Amplitude, so you won't see a `usermap` request to Amplitude if you check your browser's Network activity after making a Segment Alias call.
By default, Segment does **NOT** send Alias events to Amplitude. To forward Alias events from Segment, go to your Amplitude destination settings in the
Segment web app, and set the **Enable Alias** setting to "on". Once enabled, Segment forwards Alias events from Segment's servers only. This means
that Alias events reach Amplitude only when you're sending events from the client and have set your Amplitude instance's connection mode to "unbundled",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be instance's connection mode to "Cloud Mode" to be consistent with the App UI settings?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, good catch!

Copy link
Contributor

@briemcnally briemcnally left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM left one comment re wording

@markzegarelli markzegarelli self-requested a review March 30, 2021 23:50
@brennan brennan force-pushed the brennan/amplitude branch from 2693c6e to f90fc86 Compare March 31, 2021 00:50
@brennan brennan merged commit bc37829 into master Mar 31, 2021
@brennan brennan deleted the brennan/amplitude branch March 31, 2021 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants