> 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/data-activation/connectors/solute/solute-troubleshooting-400-bad-request.md).

# Solute Troubleshooting: 400 Bad Request

The Solute connector requires specific URL parameters. This also applies when testing the connector.

#### Identify the issue

In the **JENTIS Preview Monitor**, the Solute tag returns status `400`.

The response body includes this error:

```
Required 'val' must be a number. Required 'url' was empty. No soluteclid, gclid or msclid found.
```

#### Use a valid click ID

Append a click ID to the visited pages URL before testing. The `soluteclid` value must contain exactly 32 hexadecimal characters.

* ❌ `?soluteclid=test` This value is too short and has an invalid format.
* ✅ `?soluteclid=b9300fec85b1ba9b7ad874d5dad1912f` is a well formatted value and will pass the strict validation with Solutes API 

#### Test the connector

1. Open your website with a valid `soluteclid` appended to the URL.
2. Open the **JENTIS Preview Monitor**.
3. Trigger the Solute tag (ie. the "Server-side soluteclid detection" or a conversion tag, such as by completing a test purchase.
4. Confirm that the tag returns status `200`.


---

# 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/data-activation/connectors/solute/solute-troubleshooting-400-bad-request.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.