Unexpected "[Segment]" Prefix in Event Types

We would like to provide an end-of-week update on the Segment incident. At this time, we are continuing to working on data remediation to help impacted customers. Our next step is to scrub the [Segment] prefix from impacted events, and we expect this to be fully completed by June 11, 2025. No action will be required on your part to resolve the incorrect event names in your Amplitude Analytics charts and dashboards. We will keep you updated on our progress.

We’ve finalized our remediation plan and are actively executing it. Our team is working to address the remaining impact and will continue to provide updates as progress is made.

Thank you for your patience.

Segment has deployed a fix to resolve an issue that impacted the Segment → Amplitude Actions destination integration from June 5th, 2025 11:00 UTC to 16:36 UTC.

During this time, events sent from Segment via the Actions destination were incorrectly prefixed with [Segment] (e.g., an event like Played Song became [Segment] Played Song). This caused incorrect event names to appear in Amplitude and may have disrupted downstream workflows or charts relying on existing event names.

This change did not affect customers using the legacy Classic Segment destination.

We’ve confirmed that no new events are arriving with the [Segment] prefix.

Amplitude is working on a data remediation plan to help impacted customers. Additional updates will be posted here as we finalize the cleanup options.

We sincerely apologize for the disruption and thank you for your patience.

Status: Monitoring
Impact: Segment Actions destination only (Classic unaffected)

The fix has been deployed, and we are actively monitoring the situation.

We are currently evaluating options for data cleanup, which will take time to complete.

We’ve identified the root cause and are actively working with the Segment team to implement a resolution. We will keep you informed as we make progress.

We wanted to inform you that we've identified an unexpected issue where a "[Segment]" prefix has been added to some event types starting earlier this morning.

Our team is actively investigating this and working closely with the Segment team to resolve the issue as quickly as possible. We understand the importance of consistent event naming for your workflows and analytics, and we're treating this with high priority.

We'll keep you updated as we make progress, and will notify you as soon as the issue is resolved. If you have any questions or need assistance in the meantime, feel free to reach out.

Thank you for your patience and understanding.