Q: Why am I not seeing any data in Amplitude?
You have to send data to Amplitude by calling
track. Data will be visible after you track your first event.
Q: Why is the location information (city and/or country) from Segment's data different from the location information in Amplitude's data?
Amplitude attempts to determine the user's location from their IP address, if available. This may be different from the location information recorded by Segment.
Q: Why do I not see any user properties or only [Amplitude] user properties?
In order to send user properties via Segment, you would have to call
identify and include your user properties in the
traits field. You can read more about their
identify call in the Segment documentation.
Q: What is the difference between an event property and user property?
This article explains the difference between the two types of properties.
Q: What is the definition of a session?
A session is defined as a period of time that the user has the application open in the foreground. If session tracking is available, events logged within the same session will have the same session ID. A new session is started if the application enters the foreground after being in the background or closed for more than five minutes.
Q: Why do all of my events have a
sessionId of -1?
You have to use Segment's client-side bundled integration to have Amplitude's native SDKs track Session IDs for you.
Q: Why are there no session length calculations in Amplitude Dashboard?
See the previous answer.
Q: What if their SDK doesn’t support feature X? [device-mode]
Segment SDK might not have all the APIs provided by the Amplitude SDK; however you can still access features by directly calling Amplitude's SDKs.