> For the complete documentation index, see [llms.txt](https://docs.ib.b2core.b2broker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ib.b2core.b2broker.com/for-brokers/back-office-guide/promo/landings.md).

# Landings

{% hint style="warning" %}
The **Landings** section is not available in the Back Office. Landing pages are configured at the system level by your B2BROKER integration team and are used by partners in their IB Room.
{% endhint %}

## How landings work

In the current version of B2CORE IB, each instance has a single referral landing page configured at the system level. This is typically the registration page of your client portal.

When a partner shares their referral link, it redirects the client to this landing page with the partner's unique token appended as a query parameter:

```
{scheme}://{host}{path}?{token}={partner_token}
```

For example: `https://my.example.com/register?referral=abc123`

The following parameters are configured by your B2BROKER integration team:

| Parameter       | Description                                          | Default     |
| --------------- | ---------------------------------------------------- | ----------- |
| Scheme          | Protocol used for the link                           | `https`     |
| Host            | Domain of your client portal                         | —           |
| Path            | Path to the registration page                        | `/register` |
| Token parameter | Query parameter name that carries the referral token | `referral`  |

To configure or update these settings, contact your B2BROKER integration team.

## Partner view

Partners can see and copy their referral links in **IB Room → Promo → Links**. On that page, partners can also:

* Select a landing page from the available options
* Select a language
* Add UTM parameters to their link
* Generate a QR code for the link


---

# 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://docs.ib.b2core.b2broker.com/for-brokers/back-office-guide/promo/landings.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.