> 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/partner/what-would-you-like-to-learn-about/platform-features/working-with-brands/applying-to-brands/opt-out-of-the-brands-marketplace.md).
# Opt Out of the Brands Marketplace
After you create partnerships with 2 brands, impact.com will automatically add your [public profile](/partner/what-would-you-like-to-learn-about/platform-features/working-with-brands/applying-to-brands/profile-management/update-and-manage-your-public-profile.md) to the Brands Marketplace so that more brands can learn about you and propose contracts, potentially increasing your revenue. You will be notified that your listing is live in the Brands Marketplace by an in-app guide that appears when you log into your impact.com account.
## Hide the listing
1. From the top navigation bar, select  **\[User profile] → Settings**.
2. Under the *Profile* section, select [**Public Profile**](https://app.impact.com/secure/mediapartner/accountSettings/view-directorysettings-overview-flow.ihtml).
3. Under *Pause Profile*, select  **\[Checked Box]** to stop your profile from being displayed to new brands.
4. Select **Save**.
{% hint style="success" %}
**Note:** When you are ready for your listing to go public, you simply have to uncheck this setting to unpause your profile.
{% endhint %}
---
# 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/partner/what-would-you-like-to-learn-about/platform-features/working-with-brands/applying-to-brands/opt-out-of-the-brands-marketplace.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.
