> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/mcp/tools/edge-lake-traffic-analysis.md).

# edgeLakeTrafficAnalysis

Analyze HTTP traffic for a domain using Cloudflare analytics. Returns traffic over time with breakdowns by browser, operating system, device type, and country.

### Parameters

| Parameter       | Type          | Required | Description                                                                                                  |
| --------------- | ------------- | -------- | ------------------------------------------------------------------------------------------------------------ |
| `channelId`     | string (UUID) | Yes      | The Edge Lake channel ID. Must be a channel with `providerId: "edgeLake"`. Get this from the `domains` tool. |
| `teamId`        | string (UUID) | Yes      | The team ID the domain belongs to.                                                                           |
| `startDateTime` | string        | Yes      | Start date/time in ISO 8601 format, e.g., `2024-01-01T00:00:00.000Z`.                                        |
| `endDateTime`   | string        | Yes      | End date/time in ISO 8601 format, e.g., `2024-01-31T23:59:59.999Z`.                                          |
| `granularity`   | enum          | No       | Time granularity for chart data: `DAY`, `HOUR`, or `MINUTE`. Defaults to `DAY`.                              |
| `timezone`      | string        | No       | IANA timezone, e.g., `America/New_York`.                                                                     |

### Output

Returns:

* **chart** - Time-series of request counts
* **topBrowsers** - Most common browsers with request counts
* **topOS** - Most common operating systems
* **topDeviceTypes** - Device type breakdown (desktop, mobile, tablet)
* **topCountries** - Top countries by request count

### Example

> "What browsers are our visitors using this month?"

The AI assistant will call `edgeLakeTrafficAnalysis` and display the browser breakdown along with other traffic dimensions.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.edgetag.io/mcp/tools/edge-lake-traffic-analysis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
