> 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/scoping-to-specific-pages.md).

# Scoping to specific pages

By default, custom events fire on every page of your site. If you want to track events only on specific pages, you can specify them in the event setup:

<figure><img src="https://2052204893-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2SvefuMLsJyJPAcVXeWc%2Fuploads%2Fgit-blob-fb0d71dc5dc209b36bcf7fea31ab52af128f6cc8%2FScreenshot%202025-03-24%20at%2011.43.10%E2%80%AFAM.png?alt=media" alt=""><figcaption></figcaption></figure>

This URL matching operates on the page path name, which is the part of the URL after the initial slash and before any query parameters or anchor. For example, in the URL:

<https://www.mysite.com/**pages/my-page**?utm\\_source=google#anchor>

The page path that Intelligems matches against is **pages/my-page**.\\

Because the initial slash is ignored, you should generally not have an initial slash in the pattern. URL matching for page visit events work the same way.


---

# 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/scoping-to-specific-pages.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.