# Simple lander creation

Before you start adding the lander to Trackwill, you need to have the landing page URL accessible for quick reference.

To add the lander to the Trackwill platform, perform the following steps:

1. Go to the **Landers** tab
2. And click **Create** button

![](/files/-LvHyF1ZoRfxSjFO9LTF)

In the **Lander Creation** popup you need to:

1. Set **lander name;**
2. Set **workgroup;**
3. Set **Lander URL.**

![](/files/-LvHznN3sAU8x782vdU2)

> Trackwill note: Without thouse 3 simple steps you will not be able to save a lander in Trackwill.

### URL and Available tokens to use

In the URL field, enter the URL of your landing page. You can use tokens in order to transfer various click parameters to the landing page, such as the type of the device, operating system, and user's browser, country, city etc.

![](/files/-LvI0OZagXBfs1Uruq9F)

For example, you want to transfer a referrer to a landing page. Then the landing page URL will look like: <http://trackwill-testlander.com/?referer={referer}> . You can click on the token buttons under the URL input field and the parameter along with the token will automatically be added to the URL. When you click this button again, the parameter with the token will be removed from the URL.

When lander configuration is done click **Save** button.


---

# Agent Instructions: 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:

```
GET https://docs.trackwill.com/landers/simple-lander-creation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.