> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/brand-api-reference/reference/promo-codes.md). # Promo Codes *Promo Codes* are used to track partner involvement in your program. You can use this endpoint to manage your promo codes and to add promo codes. Utilize promo codes to give partners another channel to promote your product or service. Promo code setup is only necessary if the promo code will be used to track partner-driven actions. Promo codes passed in conversion events that were not previously set up and configured in impact.com will not affect impact.com crediting logic. Promo codes are also related to [Deals](/brand-api-reference/reference/deals.md). Deals can affect sale details, like the type of discount a customer gets, the discount amount, and can have start and end dates of their own, all of which associated promo codes can sync to. See the [Promo Codes screen](https://app.impact.com/secure/advertiser/engage/ads/view-adv-promo-codes-flow.ihtml) to manage promo codes via the impact.com web app. --- # 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://integrations.impact.com/brand-api-reference/reference/promo-codes.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.