> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/developer-guide/troubleshooting-and-common-errors/redirect-on-landing-page.md).

# Redirect on Landing Page

End-to-end testing with the Preview Monitor is enabled via URL Query Parameters added to the URL of your webpage you want to test. The JENTIS Web SDK recognizes these query parameters to establish the connection to the actual Preview Version and the Preview Monitor.

If your landing page has a built-in redirect (for example, regarding country and language), those parameters might be abandoned during the redirect, and no connection will be established to the Preview Monitor.

**Solution**: To overcome this problem, you need to add the Query Parameters to the URL you are redirected to (given that the JENTIS Basic Tracking Code is implemented on that site). You can find the Query Parameters by right-clicking the Play Button in the Preview Monitor UI and choosing "copy link." From this copy, you can now extract the right Parameters that need to be added to the end of the redirected URL.

Now you can add those parameters to any deep link URL on your site.


---

# 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://docs.jentis.com/developer-guide/troubleshooting-and-common-errors/redirect-on-landing-page.md?ask=<question>&goal=<user_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.