# URL parameters

## Adding tracking parameters

For the purpose of tracking, you can add the following parameters to the URL:

| Parameter  | Description                                                                   |
| ---------- | ----------------------------------------------------------------------------- |
| `referrer` | Name of the partner                                                           |
| `campaign` | <p>ID of the campaign from the marketing tool<br><em>Can be empty</em></p>    |
| `param1`   | The platform where our campaign is located (website / mobile / display, etc.) |
| `param2`   | The page where our campaign is located (homePage, matchPage, etc.)            |
| `param3`   | The type of integration (banner / iframe / API)                               |

By setting these parameters properly, we can share conversion data with you.

Incorporating them into the URL, it would resemble this:

<pre class="language-url" data-overflow="wrap"><code class="lang-url"><strong>https://app.socios.com/partner/[PARTNER_ID]?partnerWebAppId=[PARTNER_ID]&#x26;referrer=paris_saint_germain&#x26;campaign=FB_psg_20456&#x26;param1=website&#x26;param2=homePage&#x26;param3=banner
</strong></code></pre>

Separating each parameter to make it more readable:

```sh
https://app.socios.com/partner/[PARTNER_ID]?partnerWebAppId=[PARTNER_ID]
&referrer=paris_saint_germain
&campaign=FB_psg_20456
&param1=website
&param2=homePage
&param3=banner
```

{% hint style="info" %}
The`param1`,`param2` and`param3` parameters can be tailored to a partner's usage, hence the generic names. \
They have an impact on the charts that we create internally, which we can share with you.
{% endhint %}

## Incorporating login/registration information as parameters

To facilitate a better user experience, you can auto-fill the login/registration form by supplying user information: country code, phone number, etc.

This requires a base64-encoded JSON value, which you can provide through the `userInfo` parameter. \
This encoded value may include the following JSON:

```json
{
    "countryCode": "+33",
    "phoneNumber": "0623456789",
    "email": "example@mail.com",
    "username": "username",
    "country": "France",
    "dob": "1970-01-01"
}
```

Incorporating the above base64-encoded JSON within the URL, it would resemble this:

{% code overflow="wrap" %}

```bash
https://app.socios.com/partner/[PARTNER_ID]?partnerWebAppId=[PARTNER_ID]&userInfo=ew0KICAgICJjb3VudHJ5Q29kZSI6ICIrMzMiLA0KICAgICJwaG9uZU51bWJlciI6ICIwNjIzNDU2Nzg5IiwNCiAgICAiZW1haWwiOiAiZXhhbXBsZUBtYWlsLmNvbSIsDQogICAgInVzZXJuYW1lIjogInVzZXJuYW1lIiwNCiAgICAiY291bnRyeSI6ICJGcmFuY2UiLA0KICAgICJkb2IiOiAiMTk5OS0wMS0wMSINCn0%3D
```

{% endcode %}

### Retrieve user session (to avoid multiple logins)

In order to simplify user flow and more especially the login, you can add login\_redirect=true parameter. Having this parameter will check if the user has an active session on Socios.com and avoid to ask him to log in again.

{% code overflow="wrap" %}

```
https://app.socios.com/partner/[PARTNER_ID]?partnerWebAppId=[PARTNER_ID]&login_redirect=true
```

{% endcode %}


---

# 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://connect.socios.com/partner-web-app/url-parameters.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.