> For the complete documentation index, see [llms.txt](https://documentation.crossengage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.crossengage.io/data-and-engagement-platform/web-tracking/web-tracking-v2/tracking-user-behavior.md).

# Tracking User Behavior

CrossEngage's web tracking SDK uses an event-based system to track user behaviour. To send these events to CrossEngage, you may use one of the following three methods, depending on the behaviour you would like to track or even set up custom functions & triggers.

To trigger a predefined or a custom event, you can use the **Trigger Command** functionality which is used by providing the trigger name as string and additional arguments based on the trigger:

```
// Interface: 
ce([triggerCommandName], <...[commandParameters]>);

// Example:
ce('identify', {email: 'me@emailprovider.com'});
```

{% hint style="warning" %}
Please note that that **no user tracking will occur** until the configuration `ce({trackingOptIn: true});` has been set.
{% 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 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://documentation.crossengage.io/data-and-engagement-platform/web-tracking/web-tracking-v2/tracking-user-behavior.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.