Skip to content

Commit bc37829

Browse files
authored
Merge pull request #1492 from segmentio/brennan/amplitude
Correct Amplitude/Alias description.
2 parents fe98f2f + 609e012 commit bc37829

File tree

1 file changed

+4
-1
lines changed
  • src/connections/destinations/catalog/amplitude

1 file changed

+4
-1
lines changed

src/connections/destinations/catalog/amplitude/index.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -448,7 +448,10 @@ Segment Alias call allows you to associate a Segment user's `previousId`
448448
with the user's `userId`, or what Amplitude refers to, respectively, as a
449449
`user_id` and a `global_user_id`.
450450

451-
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.
451+
By default, Segment does **NOT** send Alias events to Amplitude. To forward Alias events from Segment, go to your Amplitude destination settings in the
452+
Segment web app, and set the **Enable Alias** setting to "on". Once enabled, Segment forwards Alias events from Segment's servers only. This means
453+
that Alias events reach Amplitude only when you're sending events from the client and have set your Amplitude instance's connection mode to "Cloud Mode",
454+
or are sending Alias events from a Segment server-side library (such as Node).
452455

453456
> note ""
454457
> To use Alias, you must have the Amplitude Portfolio add-on enabled.

0 commit comments

Comments
 (0)