Segment-Amplitude integration

Before you consider an event missing from Amplitude, remember that if the event is not in Segment then it will not be in Amplitude. Also, make sure that your requests from Segment received a successful response before considering an event missing.

Once you make sure that the event is in Segment and got a successful response, here are the first 3 things you should confirm:

1. Has Amplitude been enabled as a destination?

   Amplitude must be explicitly added as an integration for each source in your Segment instance:

2. Has the correct API Key been inputted?

   Double-check the Amplitude API Key value in project settings in your Amplitude UI to make sure the correct one is used in Segment.

3. Is the syntax correct?

   Sometimes it is not obvious that there are instrumentation errors, so always double-check the code for syntax errors (Browser’s ‘Console’ tab can be helpful):

   After going through the above steps and confirming those requirements are correct, send data to Amplitude by calling track. Data will be visible after you track your first event.

If you went over the limit, any data sent after that will not be ingested. If you want to ingest more event types you have to delete events to get back under the limit.

Check your deleted/blocked events. Deleting event types also blocks all future instances of events with the same name. If you send any data to a deleted or blocked event name in Amplitude it won't come through.

Check your Debugger tab to see if there are any errors. If there are no instances of the missing event in the Debugger, try to send a test event of that event type. If the event never comes through to Segment in the first place, then it won't show up in Amplitude.  

For track calls, you can choose to only send certain events to certain integrations. So double-check if the event is sending and that Amplitude is enabled.

You can also enable/disable specific integrations directly in the instrumentation code, so check that Amplitude isn't disabled in the actual code. 

For page/screen calls, there's no way to see all the individual names of the pages but you can see from the activity if page calls are being received by Segment.

You can also check the raw JSON of the requests to verify if the Amplitude integration has been turned off:

1"integrations": {
2    "Amplitude": false
3}

This article explains the difference between the two types of 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 an identify call in the Segment documentation.

If you went over the limit, then that may be why you are missing properties in Amplitude. Any data sent after you are over the limit will not be ingested. You will need to delete the properties to get back under the limit to ingest new properties.

Check your deleted/blocked properties. Deleting properties also blocks all future instances of properties with the same name. If you attempt to send any data to Amplitude with the deleted or block property name, it won't come through. 

If you don't see it in Segment, you won't see it in Amplitude. Check your Segment's debugger to make sure that the property appeared in Segment first.

Check your tracked properties and make sure they exist in Segment.

Sometimes it is not obvious that there are instrumentation errors, so always double-check the code for syntax errors (Browser’s ‘Console’ tab can be helpful):

See Segment's specs here on the best way to format your data. 

Amplitude also has a limit of 1024 characters, so if the property value is too long, this might be the reason why it is not showing up in Amplitude. 

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.

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.

If you are using the Amplitude Classic integration in Cloud mode, Segment does not provide session tracking by default, so you will see Session ID = -1 in Amplitude. Segment doesn’t have a concept for a session. You will have to pass in the sessionId for your server-side calls from Segment to Amplitude see details here.

If you use Segment's client-side bundled integration it will use Amplitude's native SDKs. They will track Session IDs for you here are the options from Segment:

• Use the integration in device mode and utilize Amplitude's native SDKs' default session-tracking details here.
• If you use the Amplitude Actions integration from Segment there is session tracking is available in Segment's new libraries Analytics.js 2.0, Swift or Kotlin details here.

See the previous answer.

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.

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 the correct API Key has been used for the Amplitude destination.

Lastly, share the raw data for an event that should've been in Amplitude, but is missing. We need a full payload of the event, including the endpoint used, header, body, etc.