> 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/overview/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/overview/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":
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.intelligems.io/analytics/overview/custom-events/using-custom-events-in-experiment-analytics.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
