Segment integration troubleshooting
이 페이지는 아직 귀하의 언어로 번역되지 않았습니다. 현재 작업 중이므로 곧 다시 확인해 주십시오.
When you send data to Amplitude through Segment, data can go missing or arrive in an unexpected shape at several points in the pipeline. Work through the checks below in order: confirm the event or property exists in Segment first, then confirm Amplitude accepted it.
For troubleshooting that isn't Segment-specific, refer to Missing or unexpected data.
Missing events
Why don't I see any data in Amplitude?
If the event isn't in Segment, then it isn't in Amplitude. Confirm that your requests from Segment received a successful response before considering an event missing.
After you confirm that the event is in Segment and got a successful response, confirm these three things:
Is Amplitude enabled as a destination?
Is the correct API Key entered?
Verify the Amplitude API Key value in project settings in your Amplitude UI matches the one in Segment.
Is the syntax correct?
Instrumentation errors aren't always obvious. Check the code for syntax errors (the browser Console tab can help).
After you confirm these requirements, send data to Amplitude by calling
track. Data appears after you track your first event.
Are you over the event-type instrumentation limit?
If you went over the limit, Amplitude doesn't ingest any data sent after that. To ingest more event types, delete events to get back under the limit.
Is the event deleted or blocked from Amplitude?
Check your deleted and blocked events. Deleting event types also blocks all future instances of events with the same name. If you send data to a deleted or blocked event name in Amplitude, the data doesn't come through.
Are there any errors in Segment's debugger?
Check your Debugger tab for errors. If the missing event doesn't appear in the Debugger, send a test event of that event type. If the event doesn't reach Segment, it doesn't appear in Amplitude.
Does the event exist in Segment?
For track calls, you can choose to send only certain events to certain integrations. Verify that the event is sending and that Amplitude is enabled.
You can also enable or disable specific integrations directly in the instrumentation code. Check that Amplitude isn't disabled in the code.
For page and screen calls, you can't see all the individual page names, but the activity shows whether Segment is receiving page calls.
You can also check the raw JSON of the requests to verify whether the Amplitude integration is turned off:
"integrations": {
"Amplitude": false
}
Missing properties
What is the difference between an event property and a user property?
The article on user properties and events explains the difference between the two types of properties.
Why don't I see any user properties or only [Amplitude] user properties?
To send user properties through Segment, call identify and include your user properties in the traits field. Refer to the Segment documentation for more on the identify call.
Are you over the event property type instrumentation limit?
If you went over the limit, properties may be missing in Amplitude. Amplitude doesn't ingest any data sent after you exceed the limit. Delete properties to get back under the limit and ingest new properties.
Is the property deleted or blocked from Amplitude?
Check your deleted and blocked properties. Deleting properties also blocks all future instances of properties with the same name. If you send data to Amplitude with a deleted or blocked property name, the data doesn't come through.
Did the property come through in the raw payload to Segment?
If the property isn't in Segment, it isn't in Amplitude. Check Segment's debugger to confirm that the property appeared in Segment first.
Does the property exist in Segment's schema?
Check your tracked properties and confirm they exist in Segment.
Spot any syntax code errors or other instrumentation errors?
Instrumentation errors aren't always obvious. Check the code for syntax errors (the browser Console tab can help).
Refer to Segment's specs for how to format your data.
Amplitude has a limit of 1024 characters. If the property value is too long, the property doesn't appear in Amplitude.
Why does the location information (city or country) from Segment's data differ from the location information in Amplitude's data?
Amplitude tries to determine the user's location from the user's IP address, if available. This location may differ from the location information Segment recorded.
Incorrectly-tracked sessions
What is the definition of a session?
A session is a period of time when the user has the application open in the foreground. If session tracking is available, events logged within the same session share the same session ID. A new session starts when the application enters the foreground after being in the background or closed for more than five minutes.
Why do all of my events have a sessionId of -1?
If you use the Amplitude Classic integration in Cloud mode, Segment doesn't provide session tracking by default, so Session ID appears as -1 in Amplitude. Segment doesn't have a concept for a session. You must pass in the sessionId for your server-side calls from Segment to Amplitude. For more details, refer to Segment's Amplitude integration docs.
If you use Segment's client-side bundled integration, the integration uses Amplitude's native SDKs, which track Session IDs for you. Segment provides these options:
- Use the integration in device mode and use Amplitude's native SDKs' default session tracking. For details, refer to the Segment source catalog.
- If you use the Amplitude Actions integration from Segment, session tracking is available in Segment's new libraries Analytics.js 2.0, Swift, or Kotlin. For details, refer to Segment's Amplitude Actions docs.
Why are there no session length calculations in Amplitude Dashboard?
When Session ID is -1 (refer to the previous answer), Amplitude can't calculate session length.
What if Segment's SDK doesn't support a feature in device mode?
The Segment SDK might not have all the APIs the Amplitude SDK provides. You can still access features by directly calling Amplitude's SDKs.
Still have questions?
Submit a Support ticket with the following details:
- What type of connection are you using? (cloud-mode or device-mode).
- Do you have any destination filters enabled?
- Do you see any errors in the Event Delivery tab?
- Confirm that you're using the correct API Key for the Amplitude destination.
Also share the raw data for an event that should have been in Amplitude but is missing. Amplitude needs a full payload of the event, including the endpoint used, header, and body.
이 내용이 도움이 되었나요?
For AI agents: a documentation index is available at /docs/llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.