> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/developer-guides/events-and-tracking.md).

# Events & Tracking

This article explains how to use Mimeeq events to make your own custom analytics

## How to track user events on the mimeeq configurator to track usage of various features?

This article explains how to use Mimeeq events to make your own custom analytics.

## Whats an event?

An event is something that Mimeeq fires when an action occurs on the configurator. these include such things as (these are just example)

* Enter Configurator
* Leave Configurator
* Add to cart
* Download PDF
* Generate Image
* Change Quality
* Change Option
* Generate AR (View in Room)

{% hint style="info" %}
For a full list check our [developer docs events list](https://docs.mimeeq.com/events)
{% endhint %}

## How to use these events?

Since each event is saying an action occurred you can use these events ot store this data to your own analytics system This can be any system you want to integrate with

For a practical example check this [developer docs example](https://docs.mimeeq.com/google-analytics)

## How to track events for specific users

{% hint style="warning" %}
Below presumes you are using the Mimeeq's login (Auth) system
{% endhint %}

then we will return the logged in users name (first and last name) and email as part of the user session Therefore once they have logged in you can see that info, check our developer docs to [learn how here](https://docs.mimeeq.com/events#authentication-events)

Now you know the user is logged in your can store the user details along with your events as described above If no user is logged in you can mark the user as visitor.

> The above gives you a brief outline how to use custom events to track user usage of your product configurators. We suggest passing this article to you developers.


---

# 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://help.mimeeq.com/developer-guides/events-and-tracking.md?ask=<question>&goal=<endgoal>
```

`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.