> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/component-basics/inserting-and-editing-screens/deep-linking/setup-deep-linking.md).
# Setup Deep Linking
Walkthrough of integrating Deep Linking into your app.
Let's configure a deep link for one of your app screens.
{% hint style="warning" %}
Preview Links ***do not*** support Deep Linking.
{% endhint %}
### Step #1. Click on the Screen Name
Let's configure a deep link for one of your app screens. Open the Adalo app builder and click on a screen title (the blue badge that sits above a screen). The left-side drawer will open, and inside it you'll see a section titled "Deep Linking".
### Step #2. Open the "Deep Linking" Menu
Open the Deep Linking menu located in the screen drawer. Then set a screen route name which will be used when routing the user who clicks on the link. This can be any name you want, it does not have to be the name of the screen in the builder.
For example, this screen will have the path "events" so that users will be directed to the "events" screen.
### Step #3. Copy URL
Click "Copy URL" to copy the specific URL needed to your clipboard to route users to the designated screen. In this example, the URL would be "adalo-internal.adalo.com/deep-linking-example/**events**"
Of course, it is also possible to integrate the link into your user interface for the benefit of users who want to share it.
### Step #4. Test your link
Test the link below to see the events page from the app example.
{% embed url="" %}
---
# 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://help.adalo.com/component-basics/inserting-and-editing-screens/deep-linking/setup-deep-linking.md?ask=&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.
