> For the complete documentation index, see [llms.txt](https://developer.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.mediarithmics.io/resources/your-first-integration/send-your-first-event/send-events-using-the-tag/standard-events.md).

# Standard events

As you've seen, you can give your events any name you would like. However you might want to considering mediarithmics standard event names (notice the "$" in front of the event name):

* **$page\_view**: the user has seen a page. This is the default event that you can send using the mics.pushDefault() method instead of mics.push(...). Please note that currently $page\_view events are discarded after a while.
* **$home\_view**: the user has seen the home page
* **$item\_list\_view**: the user has seen a list of products (category page, search page, etc)
* **$item\_view**: the user has seen a product page
* **$basket\_view**: the user has been on the basket page
* **$transaction\_confirmed**: the user has confirmed a transaction on one or several items
* **$conversion**: the user has completed a conversion

Using these events will make for a more user friendly experience in the mediarithmics UI.


---

# 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://developer.mediarithmics.io/resources/your-first-integration/send-your-first-event/send-events-using-the-tag/standard-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.