> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.brevo.com/docs/tracker-rest-implementation/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.brevo.com/_mcp/server.
# REST implementation
> **Legacy Tracker Documentation**
>
> For the legacy tracker doc, check our guide [here](https://tracker-doc.brevo.com/docs/getting-started-1).
This page and the ones that follow describe how to use the REST API to implement the Brevo Tracker features. The [JS implementation](/docs/getting-started-with-js-implementation) is simpler and supports more capabilities. For example:
1. The JavaScript tracker tracks page views automatically. With the REST implementation, you must send the events yourself.
2. Brevo cannot track users who clicked on your emails through REST.
3. With REST, you must pass an email in each call to identify users.
> **Combining the REST and JS implementations**
>
> You can combine both tracking technologies. For example, use JS on the client side to identify and track user behaviour on your website, and use REST on the server side to track orders.
### Authentication
The REST implementation requires a key, shown as `client_key` below, to authenticate. Get it from your [Brevo account](https://app.brevo.com/automation/parameters).
```javascript
```
## Docs
- [Identify users](https://developers.brevo.com/docs/identify-users-rest.md)
- [Track link clicks](https://developers.brevo.com/docs/track-link-clicks-rest.md)
- [Track page views](https://developers.brevo.com/docs/track-page-views-rest.md)
- [Track custom events](https://developers.brevo.com/docs/track-custom-events-rest.md)