> 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/advocate-program/manage-advocate-participant-experiences/install-custom-npm-packages-for-advocate.md).
# Install Custom NPM Packages for Advocate
You can install custom NPM packages for use in your Advocate program's microsite or widgets.
#### Install a custom NPS package
{% tabs %}
{% tab title="Install custom NPM packages for a microsite" %}
If you want to use custom components to build your microsite, then you can install a custom package.
1. In the left navigation menu, select  **\[Engage] → Content**.
2. On the *Microsite card*, select **Edit Settings**.
3. Under the *Site Hosting* section, select **+ Add Package** → **Add from NPM**.
4. Enter the package name, *Version*, and *File* path.
5. Select **Add**.
* Return to the [microsite editor](/brand/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences/microsite-editor-explained.md) to start adding your custom components to your site.
{% endtab %}
{% tab title="Install custom NPM packages for program widgets" %}
If your program has a custom widget that doesn’t use our components, then you can install a custom package.
1. In the left navigation menu, select  **\[Engage] → Content**.
2. On the widget card, select **Edit widgets**.
3. Under *Program Widgets*, select a widget.
1. In the left navigation menu, select **Packages**.
2. Select  **Add package**.
3. Select **Add from NPM**.
4. Enter the package name, version, and file path.
5. Select **Add**.
{% endtab %}
{% endtabs %}
Learn more about how to [Customize Program Widgets](/brand/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/widget-experiences/customize-program-widgets.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/advocate-program/manage-advocate-participant-experiences/install-custom-npm-packages-for-advocate.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.
