> 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/overview.md).
# Overview
You can use custom events to measure user behavior during experiments that are not covered by built-in metrics. Events can be managed in the [Events Manager](https://app.intelligems.io/events-manager).
There are two broad categories of custom events: those that measure page visits, and those that measure other user interactions on the site.
## Page visits
These events measure or filter to visitors who visited specific pages. Because they use Intelligems’ built-in page view tracking, they’re available retroactively, and can be added to experiments even after they’ve been started.
## User Interaction
These events measure user interactions on your site — for example, clicks or scrolls on a page. Targeted elements (for example for a click or "Element Visible" event) do not necessarily need to be available when the page initially loads, they can be created dynamically afterwards (for example, by an app).
{% hint style="success" %}
Custom Metrics can be added to Tests and Personalizations via the Configure Analytics tab
{% endhint %}
---
# 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/overview.md?ask=&goal=
```
`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.