# Custom events

> For AI agents: a documentation index is available at [/docs/llms.txt](/docs/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

A custom event is a saved, reusable event that combines two or more existing events with an `OR` clause, so any of those events counts as the same step in an analysis. For example, a custom event can show users who, after receiving a push notification, either played a song or searched for one as their next step.

You can also [combine multiple events in-line](https://amplitude.com/docs/analytics/charts/event-segmentation/event-segmentation-in-line-events) through the Events Module, but an in-line event applies only to the chart where you create it. Save it as a custom event when you want to reuse the same combination across other charts.

You create a custom event in the _Events_ panel from one or more pre-existing events. Doing so tells Amplitude to combine those pre-existing events and count any user activity for them as activity for the new custom event. This approach helps when you want an easy way to track activity on related or similar events, like whether a visitor has fired either the `view_landing_page_1` or `view_landing_page_2` events.

For example, `Play or Search Song` is a custom event consisting of the `Play Song` event, the `Search Song` event, and an `OR` clause to connect the two. Any user who triggers either the `Play Song` event or the `Search Song` event has converted that second step.

Another method is conditioning an added event with an [event property or user property](https://amplitude.com/docs/data/user-properties-and-events). This is the primary method for analyzing whether a user performed one of many events.

## Before you begin

- Only admins, managers, and members can create custom events.
- You can use custom events in Event Segmentation, Funnel Analysis, Retention Analysis, Lifecycle, Stickiness, Impact Analysis, Journeys, Pathfinder, Conversion Driver, Experiment Results, and Compass charts.
- You can't query on custom events in Redshift.
- All custom events have the prefix `[Custom]` before the event name in your charts.
- Editing or renaming custom events used in other charts breaks those charts. Amplitude continues to query the named value until you manually change it on any charts that use it. Amplitude displays a warning when you make any edits to custom events.
- Querying event properties on custom events is possible only if the property applies to all events. If you try to create a custom event with five different events and want to see the location values from all those events, you need to instrument the location event property to all the individual events making up the custom event.

## Group two existing events into a single custom event

To group two events, follow these steps:

1. In Amplitude Data's left-hand rail, select **Events**. Then select **Create Custom Event**.
2. In the modal that appears, select the events you want to analyze as a single event. You can set different filters on these events, in case the analysis requires a more granular view of the selected events.

At this point, you can use this event for further analyses in Amplitude. Select the new event in the _Custom_ category in the appropriate chart drop-down menus.

## Custom events and transformed events

| Topic | Custom Events | Transformed Events and Properties |
| --- | --- | --- |
| Analysis of individual components | Can perform analysis on the individual events used in the custom event. | Can only perform analysis on the transformed event. |
| Use case | Augment and group existing events into new events which you can analyze. | Clean up events and fix instrumentation issues. |
| Drop and block filters | Not available to block and drop filters. | Transformed entities aren't available to block and drop filters. |
| Chart UI limitations | Limited availability in Funnels, but can't group by event name. | Available to most charts. |
| User lookup | Shows raw event data only. | Shows raw event data only. |
| Event type limit | Don't count toward the event limit. | Don't count toward the event limit. |