> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/merchandising-experiences/offers-integrating-widgets.md).
# Integrating Components
Learn how to add the Intelligems Components to your site.
When setting up a test or personalization, you can add onsite components to merchandise your offers directly on your site to ensure your customers are aware of the offers they are eligible for, improving conversion and driving additional AOV. Components are listed on the right side of the experience editor and include:
* **Quantity buttons** — Add to product pages so customers can select multiple units and unlock tiered discounts
* **Progress bar** — Show customers how close they are to a discount or free shipping threshold
* **Offer message** — Add a promotional message to your storefront to surface active offers
{% hint style="warning" icon="traffic-light-go" %}
**Before you start:** You'll need the Intelligems JavaScript snippet installed in your theme to use offer components. If you haven't added it yet, see our [integration guide](/getting-started/adding-intelligems-script-to-your-theme.md). Quantity buttons and progress bars also require a short additional code snippet — details are in each component's article below.
{% endhint %}
See installation instructions and examples for each component at the links below. Please reach out to our support team [here](https://portal.usepylon.com/intelligems/forms/intelligems-support-request) if you would like help installing any of these components!
---
# 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://docs.intelligems.io/merchandising-experiences/offers-integrating-widgets.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.
