> 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/loyalty-engine/rewards-and-points/rewards/reward-types/offers.md). # Offers Use offer-type rewards to promote perks, highlight incentives, or share program info. Offer-type rewards promote perks, communicate program information, or link users to external promotions. Unlike voucher or gift card rewards, offers don’t deliver direct value through the Loyalty Engine — they exist for communication and engagement. Offers are best suited to things that aren’t themselves an earning opportunity — external links, sign-up forms, or general program information. If you want to promote and reward an earning activity, a **campaign** is usually the better fit: campaigns carry their own title, description, and artwork that are shown to users, and they handle the underlying earning logic and progress tracking in one place. See [Getting started with Campaigns](/product/loyalty-engine/campaigns/getting-started-with-campaigns.md). There are two types of offer, based on how you configure the URL field. #### Non-purchasable offers These are visible to users but can’t be purchased or redeemed. Use them to communicate: * Program information (e.g. *Welcome to the program*, *Membership terms*) * External promotions or partner links * Announcements that point users to another page All offer-type rewards are non-purchasable by default. #### Purchasable offers To make an offer purchasable, enable a dynamic URL. This lets users “purchase” the offer (optionally for points) and be directed to an external page — such as a sign-up form or third-party promotion. Purchasable offers are best for: * Linking users to personalised offers or services * Handing over user-specific info like Account ID via the URL *** ### Offer URLs The URL field attaches a web link to an offer. It can be either: #### Static URL * Shown to all users who can view the reward * Used for general info or landing pages * Offer remains non-purchasable * Tracked clicks are not recorded #### Dynamic URL * Requires the user to purchase the offer to access the URL * Can include dynamic parameters (e.g. userId, accountId) * Offer becomes purchasable * Points deducted if a price is set * Tracked through the `PURCHASED_REWARD` event {% hint style="info" %} You can use a dynamic URL without dynamic parameters if you simply want the user to “purchase” before accessing a static URL. {% endhint %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://kbase.whitelabel-loyalty.com/product/loyalty-engine/rewards-and-points/rewards/reward-types/offers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.