> 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/domain-analytics-event.md).

# domainAnalyticsEvent

Get channel breakdown for a specific event. Given an event name (e.g., "PageView", "Purchase"), returns counts per channel over time for that event.

Use this after `domainAnalytics` with `type: "name"` to drill down into which channels are receiving a specific event.

### Parameters

| Parameter   | Type          | Required | Description                                                           |
| ----------- | ------------- | -------- | --------------------------------------------------------------------- |
| `domainId`  | string (UUID) | Yes      | The domain ID (tagId). Get this from the `domains` tool.              |
| `teamId`    | string (UUID) | Yes      | The team ID the domain belongs to.                                    |
| `event`     | string        | Yes      | The event name to analyze, e.g., `PageView`, `Purchase`, `AddToCart`. |
| `range`     | number        | Yes      | Number of time units to look back.                                    |
| `rangeType` | enum          | Yes      | Time unit: `MINUTE`, `HOUR`, or `DAY`.                                |
| `status`    | number        | Yes      | Filter by status: `1` for successful events, `0` for errors.          |
| `timezone`  | string        | Yes      | IANA timezone, e.g., `America/New_York`.                              |

### Output

Returns time-series data showing event counts broken down by channel/provider for the specified event.

### Example

> "Which channels are receiving Purchase events this week?"

The AI assistant will call `domainAnalyticsEvent` with `event: "Purchase"` and display counts per channel.


---

# 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://docs.edgetag.io/mcp/tools/domain-analytics-event.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.