> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/page-builder/how-do-products-offers-and-pages-relate-in-page-builder.md).

# Products, Offers, and Pages Relationship

This article describes the relationship between Limio pages, offers and products.

Understanding how these entities are interconnected will help you effectively create and manage successful marketing campaigns.

In Limio, each **Product** is associated with a Zuora product, which, in turn, is linked to a rate plan. Products can have a set of entitlements which define the permissions granted to customers who subscribe to that product.

**Offers** in Limio represent bundles or packages of products. An offer can consist of one or multiple products, allowing for versatile product combinations. Additionally, each product can belong to multiple offers, enabling targeted marketing efforts.

Finally, you can create **Pages** aimed at promoting specific products or offers. A page can include multiple offers, providing the flexibility. Similarly, each offer can be associated with multiple pages, ensuring cross-promotion and broad marketing reach. Pages can also be used without offers or products attached, for example in a checkout or static content view.

<figure><img src="https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-c246e547dac0e0cc9de40470e0bdc398ff607691%2Fimage%20(61).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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.limio.com/product/page-builder/how-do-products-offers-and-pages-relate-in-page-builder.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.
