> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/analytics/custom-events/using-custom-events-in-experiment-analytics.md).

# Using custom events in experiment analytics

Custom events can be used in two ways in experiments analytics:

1. To measure the % and number of visitors who triggered the event during the experiment
2. To filter to visitors and sessions who triggered the event during the experiment

In either case, to use a custom event in an experiment, you need to add that event as a "Custom Metric" in experiment setup, during the "Configure Analytics" step. As long as the event was created before the experiment started, you can also do this even after an experiment started. "Page visit" type events can be added at any time, they can even be created after an experiment has started (see more on this distinction [here](/analytics/custom-events/overview.md)).

To add an event to an experiment as a custom metric, go to the "Configure Analytics" step, and click "Add Custom Metric":

<figure><img src="/files/D9ZfrB9x6KT2QJhHcrSV" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.intelligems.io/analytics/custom-events/using-custom-events-in-experiment-analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.