Source: https://docs.amadalis.ai/reference/copilot/analytics-and-events/

# Copilot: Analytics and events

Open **Copilot** in the site admin and describe the result you want. Use the tables below to check the requests in this area, their approval steps and their available Undo.

Checked against the product’s code on 7 November 2026.

Reports read the site’s recorded evidence. They do not establish that a missing event happened. See the [event catalog](https://docs.amadalis.ai/reference/event-catalog/) for names, senders and collection gaps.

A dimension is a category for grouping records. A metric is a measure to count or calculate. An event binding connects an element or action to the event it sends.

An event definition can be saved without collecting it. Enabling capture, changing which elements send events or collecting extra arrival parameters needs approval. Google Analytics requests need a configured connection. Connection credentials belong on the Connections screen, never in a copilot message.

In the tables, **Yes** under approval means a separate approval is required before applying the request. **Available** under Undo means the request can be reversed. The specific receipt must offer **Undo**; it can be limited by the input, later changes or the state that was saved. **No** means this request provides no automatic Undo. Reading a fact has nothing to undo.

These are plain-language descriptions of requests, not text you must type exactly. Your role, configured connections and site capabilities determine which requests are available. See [How copilot requests are governed](https://docs.amadalis.ai/reference/copilot/).

## Analytics reports and configuration

| Request | Approval | Undo |
| --- | --- | --- |
| Define a standing analytics alert | Yes | Available |
| Delete a standing analytics alert | Yes | Available |
| Check one analytics alert now | No | No |
| Define a channel group for Sources | Yes | Available |
| Delete a channel group | Yes | Available |
| List your channel groups | No | No |
| Add a dated note to a Google Analytics report | Yes | Available |
| Save a Google Analytics connection through its settings flow | Yes | Available |
| Disconnect Google Analytics | Yes | No |
| Read a connected Google Analytics report | No | No |
| Choose the goal shown in the Analytics overview | No | Available |
| Read the Analytics overview | No | No |
| Query the site’s recorded analytics | No | No |
| List available measures, dimensions, goals and channel groups | No | No |
| Change whether supported analytics count known bots | Yes | Available |

For a selector binding requested in chat, first check that rule in **Composer** > **Track**. The copilot uses the browser’s matching-rule measurement from that conversation context, not a number typed by the model. A missing or older measurement can require another check.

## Event capture

| Request | Approval | Undo |
| --- | --- | --- |
| Archive an event definition | Yes | Available |
| Bind an event to matching page controls | Yes | Available |
| Read event counts | No | No |
| Define a custom event in the catalog | No | Available |
| Disable event capture definitions | Yes | Available |
| Enable event capture definitions | Yes | Available |
| Inspect an event definition | No | No |
| List event definitions and events needing review | No | No |
| Preview an event binding | No | No |
| Check whether an event arrived recently | No | No |
| Read the extra arrival query parameters being collected | No | No |
| Change which extra arrival query parameters are collected | Yes | Available |
| Rename an event’s visible label | No | Available |

The arrival check reads only events already recorded and does not wait. See [Check that an event arrives](https://docs.amadalis.ai/insights/events-and-capture/#check-that-an-event-arrives).

## Reporting groupings

| Request | Approval | Undo |
| --- | --- | --- |
| Define a reporting dimension from recorded data | No | Available |

## Recent events

| Request | Approval | Undo |
| --- | --- | --- |
| Read recent captured events | No | No |

In chat, recent events never name a real visitor. You can narrow them by event type, by country or to a test visitor you marked yourself in **Personalization**. To see which visitor an event came from, use **Events** in **Insights** > **Explore**.

## Funnels

| Request | Approval | Undo |
| --- | --- | --- |
| Define a funnel | No | Available |
| Read what drives progression through a funnel | No | No |
| Read a funnel’s results | No | No |

## Goals

| Request | Approval | Undo |
| --- | --- | --- |
| Archive a goal definition | No | Available |
| Check a goal against past recorded events | No | No |
| Define a goal | No | Available |
| Read a goal definition | No | No |
| List goal definitions | No | No |

## Reporting measures

| Request | Approval | Undo |
| --- | --- | --- |
| Define a reporting metric from recorded data | No | Available |

Return to [the copilot request index](https://docs.amadalis.ai/reference/copilot/).

## Your next step

Choose a request that matches your task, then [ask the copilot](https://docs.amadalis.ai/copilot/copilot/). Review its proposed consequence before approving any change.