> 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/self-serve-requests-overview.md).

# Self-Serve Requests Overview

impact.com lets you submit self-serve requests via step-by-step checklists to add new features or add-ons to your account without contacting support.

The checklist helps you define what you want to add and how it should be configured, so everything is set up correctly. Provide as much detail as possible in the checklist, so that our team has all the necessary information to support if needed.

You don't need to submit a request to add an event type. See [Create an Event Type](/brand/what-would-you-like-to-learn-about/platform-features/event-types/create-an-event-type.md) to set one up yourself.

You can provide setup details to [Request a New Program](/brand/what-would-you-like-to-learn-about/account-administration/account-settings/self-serve-requests/request-a-new-program.md).

Learn how to [Create a CPC Tracking Event Type](/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/create-a-cpc-tracking-event-type.md).


---

# 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/self-serve-requests-overview.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.