Relevant source files

The following files were used as context for generating this wiki page: - [src/app/api/send/route.ts](https://github.com/andyrvcom/test-umami/blob/main/src/app/api/send/route.ts) - [src/tracker/index.js](https://github.com/andyrvcom/test-umami/blob/main/src/tracker/index.js) - [src/lib/constants.ts](https://github.com/andyrvcom/test-umami/blob/main/src/lib/constants.ts) - [src/app/(main)/console/[websiteId]/TestConsolePage.tsx](https://github.com/andyrvcom/test-umami/blob/main/src/app/%28main)/console/[websiteId]/TestConsolePage.tsx) - [cypress/e2e/api-website.cy.ts](https://github.com/andyrvcom/test-umami/blob/main/cypress/e2e/api-website.cy.ts)

# Data Collection API The Data Collection API is the core mechanism for capturing website analytics data within the Umami application. It consists of a client-side JavaScript tracker and a server-side ingestion endpoint. The tracker, when embedded on a website, collects information about page views, user interactions, and custom events, then sends this data to the API endpoint for processing and storage. This system is designed to be lightweight and privacy-focused. It handles tasks such as bot detection, IP blocking, session management, and parsing of event data, including UTM parameters and various click IDs. The primary endpoint for data collection is `POST /api/send`. ## Client-Side Tracker The client-side component is a JavaScript file (`script.js`) that is included on the tracked website. It exposes a global `window.umami` object for manual tracking and automatically captures page views and specific user interactions. *Sources: [src/tracker/index.js](), [src/app/(main)/console/[websiteId]/TestConsolePage.tsx]()* ### Configuration The tracker is configured via `data-*` attributes on the `