> 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/custom-javascript-events.md).

# Custom JavaScript Events

If you want to track events that are not covered by Intelligems’ built-in custom event types, you can write any custom event using JavaScript. There are two ways to do this:

1. JavaScript custom event managed in Intelligems: this can be set up from the Events Manager. Make sure you leave the event name as-is in the generated code (`javascripteventGVYMQ` in this example):

   <figure><img src="https://2052204893-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2SvefuMLsJyJPAcVXeWc%2Fuploads%2Fgit-blob-5c3f01e24f69fff0f62a37ea34ce8bcd3f229946%2Fimage.png?alt=media" alt="" width="332"><figcaption></figcaption></figure>
2. Events sent directly from your theme code: you can send events using JavaScript directly from your own site code, like this:

```html
<script>
   window.igEvents = window.igEvents || [];
   window.igEvents.push({"event": "myCustomEvent"});
</script>
```

This event will then appear in the Events Manager, where you must register it (acknowledging the event and giving it a name) before you can start using it in experiments.

{% hint style="info" %}
Custom event identifiers can be a maximum of 100 characters long
{% 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 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/custom-javascript-events.md?ask=<question>&goal=<user_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.