> For the complete documentation index, see [llms.txt](https://help.konnektive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.konnektive.com/konnektive-crm/crm-setup/campaign-setup/landing-page-setup-form-code/multiple-product-lander.md).

# Multiple Product Lander

Multiple Product Landers are great when you want to give your customer a choice between several different products or packages on your checkout page. For instance, you may want to offer 1-month, 3-month and 6-month supplies of a product, and allow the customer to choose which they prefer.

The setup is essentially the exact same as the the setup for the single-product lander, with one notable difference.

1\) Set the Lander Type as Multi Product

<br>

2\) Checkout page shows Product Options

-Your checkout page will show all your campaign offers in a product selection area. This can be customized by your designer to fit your site's look and feel.

For more details about setting up this type of landing page. Please refer to the single-product lander tutorial.


---

# 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://help.konnektive.com/konnektive-crm/crm-setup/campaign-setup/landing-page-setup-form-code/multiple-product-lander.md?ask=<question>&goal=<endgoal>
```

`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.