> For the complete documentation index, see [llms.txt](https://docs.ingestlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ingestlabs.com/media-data-platform/dashboard/analytics-dashboard.md).

# Analytics Dashboard

The **Analytics Dashboard** provides predefined dashboards to help you monitor and analyze campaign performance and user activity across different channels.

Under the **Analytics Dashboard**, the following dashboards are available:

#### 1. Ad Insights

Provides an overall view of advertising performance across connected ad platforms, including key metrics such as traffic and conversions.

#### 2. Google Ad – Insights

Displays performance data specifically for Google advertising campaigns, such as campaign activity and conversions coming from Google ads.

#### 3. Facebook Ad – Insights

Displays performance data for Facebook advertising campaigns, including traffic and conversions generated from Facebook ads.

#### 4. Event Flow

Shows how users move through different events in the application, helping you understand the user journey and interaction flow.


---

# 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.ingestlabs.com/media-data-platform/dashboard/analytics-dashboard.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.
