Comparing numbers between any two end-tools (or between Segment and an end tool) is rarely going to produce identical numbers. Each tool accepts and defines incoming data slightly differently, and they will not always match 100% depending on what types of data the tool accepts.
For example, consider these instances with some of our most popular destinations:
pageviews from one of Segment’s server-side libraries, a
urlproperty is required. Otherwise, Google Analytics will silently reject your
It is against Google’s terms of service to pass Personally Identifiable Information (PII) to your Google Anlaytics reporting interface. For that reason Segment will never pass anything from an
identifycall to Google unless you specifically tell us to.
If you want to pass the
identifycalls to Google Anlaytics - enable Send User-ID to GA in your Advanced Google Analytics settings on the Segment destinations catalog.
By default, Segment won’t send standard
screencalls to Amplitude. However, you can enable sending
screencalls with the following destination settings, which you can find under the “Advanced Options” tab.
If you’re using a server-side library or the Segment HTTP API to send events or traits about anonymous visitors, Amplitude won’t automatically be able to identify that anonymous user as being the same person when they log in. To have Amplitude connect the dots, when you call
.identify()on user log-in, you should include both the
anonymousIdyou were using before the user logged in, as well as their
For Amplitude to associate both client-side and server-side activity with the same user, you will need to pass the same
deviceIdto Amplitude. Otherwise, Amplitude will create two users - one associated with your
deviceIdand another user associated with your Segment
Please contact our support team for further inquiries about a specific tool you have questions about to ensure there isn’t an implementation error.
If you have any questions, or see anywhere we can improve our documentation, please let us know!