# Real time user tracking

Online tracking aims at giving the ability to track unique users across digital properties. We support the following integrations in real time:

* [Website tracking](/data-streams/data-ingestion/real-time-user-tracking/web-events.md)
* [Application tracking](/data-streams/data-ingestion/real-time-user-tracking/application-tracking.md)
* [API tracking](/data-streams/data-ingestion/real-time-user-tracking/api.md)
* [Conversion tracking](/data-streams/data-ingestion/real-time-user-tracking/conversions.md)
* [AMP tracking](/data-streams/data-ingestion/real-time-user-tracking/amp.md)
* [Email tracking](/data-streams/data-ingestion/real-time-user-tracking/email-views-and-clicks.md)
* [Display campaign tracking](/data-streams/data-ingestion/real-time-user-tracking/ads-exposure.md)

{% hint style="success" %}
Use this feature if you want to track in real time what your users are doing on your digital touch points.&#x20;
{% endhint %}

{% hint style="danger" %}
If your need is to mass import activities, users or CRM profiles, you should consider [Bulk Imports](/data-streams/data-ingestion/bulk-processing.md).
{% endhint %}

## User activities and events

With real-time user tracking, **you send user events** to mediarithmics that are **aggregated and encapsulated into** [**user activities**](/user-points/user-activities.md). Some user activities only have one user event, while others can have multiple events.&#x20;

{% content-ref url="/pages/-MNSuS1g6Npcklh14qQu" %}
[UserActivity & UserEvent](/user-points/user-activities.md)
{% endcontent-ref %}

For example, when you send hits from the JS Tag on a web site, mediarithmics aggregates all the events into sessions, creating one user activity per session.

![](/files/-MPDyxIKz1SJnxObE-dL)

## Session aggregation

If registering a visit as `IN_SESSION`, the visit will go through the **session aggregation** step. We aggregate visits in sessions based on the provided identifiers. We close sessions after 30 minutes of inactivity or if a new event is recorded with a referrer from a different domain than the previously recorded. Visits registered as `LIVE` don't create sessions.

## The processing pipeline

When using the real-time tracking capability of mediarithmics, you enter what is called the **User Activity Processing Pipeline**. It allows mediarithmics to do some processing on your behalf.

![](/files/-MPE4kxzJamGadf4sftT)

Here are the steps of processing, in order :

1. At session closing or every minute if events are `live`, creation of a user activity.
2. Execution of [**event rules**](/data-streams/data-ingestion/real-time-user-tracking/event-rules.md). They allow you to edit the events in the activity and add new ones based on their shapes.&#x20;
3. Application of the [**activity analyzer.**](/data-streams/data-ingestion/real-time-user-tracking/activity-analyzers.md) It is a plugin allowing you to execute code to transform each activity.
4. Detection of **query-based conversions**. Conversions relying on pixels skip this step.
5. Evaluation of **automations triggers "React to an event"**. If the ongoing activity matches the trigger, the UserPoint enters the scenario.
6. [**UserChoice**](/advanced-usages/data-privacy-compliance/user-choices.md) management ensures the data you ingest is compatible with GDPR and other regulations.

&#x20;The activity is finally stored.


---

# Agent Instructions: 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:

```
GET https://developer.mediarithmics.io/data-streams/data-ingestion/real-time-user-tracking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
