> For the complete documentation index, see [llms.txt](https://kbase.whitelabel-loyalty.com/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kbase.whitelabel-loyalty.com/product/interfaces/white-label-interfaces/loyalty-microsite/loyalty-microsite-setup/1.-deployment-type.md).

# 1. Deployment type

Learn about the three deployment options for the Loyalty Microsite: standalone website, embedded in a website, or embedded within a mobile app.

The Loyalty Microsite can be accessed by your users in several ways depending on your deployment choice. This guide explains how to configure user access to the microsite—whether as a standalone website, embedded within your existing website, or integrated directly into your mobile app.

Each method allows you to offer a seamless loyalty experience tailored to your program’s goals and the preferences of your audience.

### Embedded in a website

Embed the Loyalty Microsite within an iFrame on an existing webpage of your website. This approach keeps users within your site environment while providing seamless access to loyalty features. Embedded authentication can be used to allow users logged into your website to access loyalty information without an additional login step.

Read more: [1.a iFrame embed](https://kbase.whitelabel-loyalty.com/product/interfaces/white-label-interfaces/loyalty-microsite/loyalty-microsite-setup/1.-deployment-type/1.a-iframe-embed.md)

### Embedded in a mobile app

Integrate the microsite within your mobile app’s WebView, creating an in-app loyalty experience. Users can access loyalty features directly from your app’s interface, with no need to leave the app environment. Authentication can be handled by passing the user’s session to the microsite for seamless login.

Read more: [1.b Mobile app embed](https://kbase.whitelabel-loyalty.com/product/interfaces/white-label-interfaces/loyalty-microsite/loyalty-microsite-setup/1.-deployment-type/1.b-mobile-app-embed.md)

### Standalone website / progressive web app (PWA)

Deploy the microsite as a standalone website with a dedicated URL, such as rewards.yourdomain.com. This setup offers users a centralised loyalty portal accessible from any device, and can be configured to work as a Progressive Web App (PWA) for an app-like experience on mobile.

Read more: [1.c Standalone website or PWA](https://kbase.whitelabel-loyalty.com/product/interfaces/white-label-interfaces/loyalty-microsite/loyalty-microsite-setup/1.-deployment-type/1.c-standalone-website-or-pwa.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://kbase.whitelabel-loyalty.com/product/interfaces/white-label-interfaces/loyalty-microsite/loyalty-microsite-setup/1.-deployment-type.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.
