> 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/marketing-content/brand-assets/access-widgets-created-by-partnered-brands.md).

# Access Widgets Created by Partnered Brands

Some brands you partner with might share Custom Widgets that you can use to create highly customized content. These widgets can supply you with the tools to completely customize a storefront, build an image asset, query an application programming interface (API), and do much more. The widgets you have access to depend on the brands you're partnered with.

{% hint style="success" %}
**Note:** The Content Widgets option only appears in your top navigation once a partnered brand has made a widget available to you.
{% endhint %}

## Access a widget

Widgets can either be hosted within impact.com or on a brand's website, in which case you'll be redirected from the impact.com platform.

1. From the top navigation bar, select **Manage** → **More** → [**Brand Widgets**](https://app.impact.com/secure/mediapartner/tools/view-mp-tools-flow.ihtml).
2. Select the Custom Widget you want to use.
   * You'll be redirected to the brand page where the widget is provided

     **OR**
   * The widget will appear in the impact.com platform.
3. At this point, use the widget as needed or as outlined by the partnered brand.

<div data-with-frame="true"><figure><img src="https://347878556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2Fgit-blob-b5edba322ab078a4eabfeed203a14f6444dfde2a%2Ffc58dcd512e16414422dc61a838449c685efb7bb51baf5903b8795af945b4eef.png?alt=media" alt=""><figcaption></figcaption></figure></div>


---

# 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/marketing-content/brand-assets/access-widgets-created-by-partnered-brands.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.