> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cometly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# list_custom_events

> List this space's configured custom conversion event slots with their human labels.

Cometly stores custom conversion events in 50 generic slots (`custom_event_1` … `custom_event_50`). Each space configures human labels for the slots it uses. This tool returns the label map so the agent can resolve a user phrase like "deals" → `custom_event_2` without guessing.

## When to use

* The user references an event by its human name and you need to pass the slot id to [`query_ad_metrics`](/mcp/tools/query-ad-metrics) or [`list_events`](/mcp/tools/list-events).
* You're answering "what custom events does this space track?".

## Parameters

| Parameter | Type   | Required | Description                         |
| --------- | ------ | -------- | ----------------------------------- |
| `format`  | string | No       | `csv` (default), `json`, or `yaml`. |

## Output

```csv theme={null}
slot,label,include_in_gross_revenue
custom_event_1,Lead Magnet,true
custom_event_2,Deal Created,false
custom_event_5,Webinar Registration,true
```

Only configured slots appear — empty `custom_event_*` slots are omitted by default.

## Tip — label resolution works either way

You don't always need to call this tool first. The label resolver accepts either form on analytics tools:

```json theme={null}
{ "metrics": ["custom_event_2"] }
```

```json theme={null}
{ "metrics": ["Deal Created"] }
```

Both work. Calling `list_custom_events` is still cheaper than a `[validation_error]` round-trip on a misspelled label, though.

## Related

* [`get_workspace_context`](/mcp/tools/get-workspace-context) embeds the same map for session-start use.
* The `cometly://catalog/custom-events` MCP Resource serves the same data — OAuth-aware clients can subscribe and avoid re-fetching.