> ## 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.

# How events work

> See how Cometly events work: the standard events in every space, the custom events you name yourself, and the four metrics each event adds to reports.

Cometly events track the actions people take on the way to becoming a customer, such as form submissions, lead qualification, call scheduling, deal creation or purchases. They can come from your website, funnel, CRM or payment processor. Every Cometly space (a workspace with its own settings, integrations and data) comes with a set of standard events, and you can create up to 50 custom events in the **Events Manager**.

Events are what Cometly attributes to your ads. Once an event receives data, you can see how many times it happened, what it was worth and what it cost for each campaign, ad set and ad. When you are ready to set events up, see [Create and configure events](https://docs.cometly.com/getting-started/events.md).

## Standard events

* Add Payment Info
* Add to Cart
* Complete Registration
* Contact
* Initiate Checkout
* Lead
* Purchase
* Schedule
* Sign Up
* Start Trial
* Submit Application
* Subscribe
* Upsell Purchase
* View Content
* Webinar Registration

If you use the Cometly API, the `event_name` value of each standard event is listed on the [Create Event](https://docs.cometly.com/api-reference/endpoint/create-event.md) page.

To learn more about the metrics of standard events, see the [metrics glossary](https://docs.cometly.com/guides/analyzing-data/metrics-glossary.md#standard-event-metrics).

## Custom events

Custom events are events you name yourself, for actions the standard events do not cover. See [Manage custom events](https://docs.cometly.com/guides/events/custom-events.md).

## Metrics created for each event

When you create an event in Cometly, four metrics are generated for it automatically:

1. **\{Event}:** the number of times the event occurred.
2. **\{Event} Value:** the total value associated with the event.
3. **Cost per \{Event}:** the average cost to generate the event.
4. **\{Event} ROAS:** the return on ad spend for the event.

**Example:** if you create a custom event called "Deal Created", these metrics appear in your Cometly reporting:

* **Deal Created**
* **Cost per Deal Created**
* **Deal Created Value**
* **Deal Created ROAS**

To keep everything organized, set up one event at a time, based on your [tracking plan](https://docs.cometly.com/getting-started/tracking-plan.md).

## Frequently asked questions

### What event name do I send for a custom event through the API or Zapier?

You send the custom event's fixed `event_name`, not the name you gave it. For example, if you named your first custom event Deal Created, you send `custom_event_1`. To find the exact value, go to **Events Manager**, click **Manage custom events** and select the event.

### Does a custom event's value count toward Gross Revenue?

Only if you choose it. When you configure a custom event, you can tick the option to include its value in the **Gross Revenue** metric, which suits events that are confirmed revenue. The **Purchase** event already counts toward Gross Revenue.

### Are custom events sent back to ad platforms?

Yes. By default, Cometly sends a custom event back to the ad platform as a custom event. Under **Advanced settings**, you can map it to a standard event (for example Lead or Purchase) so the ad platform receives it as that standard event.

## Next steps

* [Create and configure events](https://docs.cometly.com/getting-started/events.md)
* [Manage custom events](https://docs.cometly.com/guides/events/custom-events.md)
* [Create a tracking plan](https://docs.cometly.com/getting-started/tracking-plan.md)
* [Look up metrics in the metrics glossary](https://docs.cometly.com/guides/analyzing-data/metrics-glossary.md)

Still have questions or need a hand? We're happy to help. Reach our team at [support@cometly.com](mailto:support@cometly.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.