SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Event Not Appearing in Amplitude Despite Successful Delivery from Segment

Issue

When sending events from Segment to Amplitude, users may observe that certain events do not appear in Amplitude’s reporting or data views, even though Segment’s Delivery Overview shows the event as successfully delivered. There are no error messages or blocks visible in either Segment or Amplitude, and the event may be visible in other destinations (such as data warehouses) but not in Amplitude.

 

Product

Segment Destinations

 

Environment

Segment Console

 

Cause

This issue can occur when Segment successfully sends the event to Amplitude and receives a 200 OK response, but Amplitude subsequently drops or filters the event internally. Common causes include:

  • Amplitude ingestion rules or drop filters (such as filters based on event name patterns) that silently block events after successful API receipt.
  • Property validation or length constraints in Amplitude that result in silent drops.
  • Configuration mismatches, such as incorrect API keys or project settings, though these typically affect all events, not just specific ones.

 

Resolution

To confirm that an event has been successfully sent from Segment to Amplitude and to identify where a drop may be occurring, follow these steps:

1. Check Segment Delivery Overview

  • In the Segment Console, navigate to your Amplitude destination’s Delivery Overview.
  • Locate the event in question under “Successful Delivery.”
  • Confirm that Segment shows a 200 OK response from Amplitude’s API for the event.

2. Use the Event Tester in Segment

  • Open the Event Tester for your Amplitude destination in the Segment Console.
  • Submit a sample payload matching your event.
  • Review the second response block (the Amplitude API call).
  • Confirm that "events_ingested": 1 and that there are no error arrays in the response body.

3. Verify Amplitude Configuration

  • Double-check that the Amplitude API key in Segment matches the intended Amplitude project.
  • Review Amplitude Data Management and Govern settings for any filters, hidden, or blocked events.
  • Ensure timestamp and timezone settings are correct.

4. Check for Drop Filters in Amplitude

  • If the event is not visible in Amplitude, contact Amplitude Support and provide the Segment Delivery Overview and Event Tester results.
  • Request a review of any drop filters or ingestion rules that may block events by name or pattern.

5. Share Evidence with Amplitude Support

  • Provide Amplitude with the exact payload, server upload time, and confirmation of successful ingestion from Segment.

 

Additional Information

  • Segment’s Delivery Overview and Event Tester are essential tools for confirming successful delivery to Amplitude.
  • Amplitude may silently drop events based on ingestion rules or filters, even if their API accepts the payload.
  • If Amplitude support cannot locate the event, request a review of historical drop filters or ingestion rules that may not be visible in the standard UI.
Have more questions? Submit a request
We can’t wait to see what you build.
Powered by Zendesk