> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/account-administration/account-settings/self-serve-requests/create-a-new-event-type.md).
# Request a New Event Type
{% hint style="success" %}
**Note:** You can create your own event type without requesting help from support. See [Create an Event Type](/brand/what-would-you-like-to-learn-about/platform-features/event-types/create-an-event-type.md).
{% endhint %}
To create a new event type, you'll need to complete a checklist with all the necessary information to help you set up the new event type. Fill out the checklist with as much information as possible.
1. From the top navigation bar, select  **\[User profile] → Settings**.
2. On the right, under *Tracking*, select [**Event Types**](https://app.impact.com/secure/advertiser/tracking-settings/actiontracker/view-actiontracker-flow.ihtml).
3. In the upper-right corner, select **Create Event Type**.
4. Complete the information in the following main sections:
Overview
1. Indicate which event type you would like to add to your program (standard or mobile). Refer to [Event Types Explained](/brand/what-would-you-like-to-learn-about/platform-features/event-types/event-types-explained.md) to get a brief overview of event types.
2. **Technical Contacts (optional):** Your technical contacts who will be working through the integration, as well as anyone else who should be looped into this integration.
Standard Events (General Details)
If you selected the standard event section, complete the information associated with your new standard event type:
1. How many event trackers do you want to add?
2. The event type name, e.g., “Online Sale” to record the data of a sale.
3. Event type flow: How does the conversion event occur? E.g., a user visits an online store, adds a product to their cart, and proceeds to checkout.
4. What is the commission structure for the event type? Choose between paying the partner a fixed fee, a revenue percentage, or a combination of both for driving a conversion event.
5. Relationship with existing event types, if any.
1. For example, you can require one event to happen before another (e.g., a lead that later converts to a sale) by creating [chained event types](/brand/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/actions/track-your-conversion-funnel-using-chained-actions.md).
Standard Events (Technical Details)
1. Enter the domains and sub-domains associated with the event type.
2. Specify the checkout engine associated with this event type, e.g., Shopify. If this field doesn’t apply to you, enter NA (Not Applicable).
3. If you know what integration method you’re using, select the method from the drop-down menu. Refer to our [available integrations](https://integrations.impact.com/integration-guides/for-brands) in our Integrations Portal.
Mobile Events (General Details)
If you selected the mobile event section, complete the information associated with your new mobile event type:
1. How many event trackers do you want to add?
2. The event type name, e.g., App install to record when a customer installs a brand’s defined app.
3. The operating system for which the app is built.
4. Name of the app.
5. Commission structure for the event type. Choose between paying the partner a fixed fee, a revenue percentage, or a combination of both for driving a conversion event.
Mobile Events (Technical Details)
1. Indicate whether you’re using a [Mobile Measurement Partner](https://integrations.impact.com/integration-guides/for-brands/plugin-integrations/mmp-mobile-measurement/integrate-with-adjust) (MMP).
2. If you know what integration method you’re using, select the method from the drop-down menu. Refer to our [available integrations](https://integrations.impact.com/integration-guides/for-brands) in our Integrations Portal.
3. Indicate whether you’re already using an MMP to track other events.
Confirmation
You completed your request. An impact.com representative will review your request and be in touch.
---
# 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://help.impact.com/brand/what-would-you-like-to-learn-about/account-administration/account-settings/self-serve-requests/create-a-new-event-type.md?ask=&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.