> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/destinations/kameleoon/server-side.md).

# Server Side

Send the mediarithmics vector\_id to Kameleoon through a server-to-server connection.

The server-side Kameleoon connector lets you customise the user experience by segment through a server-to-server connection, rather than through the visitor's browser.

<table data-search="false"><thead><tr><th width="220">Connection</th><th></th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>Server-side</td></tr><tr><td><strong>Category</strong></td><td><a href="/connectors/partner-types/on-site-personalisation.md">On-site personalisation</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>mediarithmics <code>vector_id</code></td></tr><tr><td><strong>Authentication</strong></td><td>Configured with your mediarithmics account manager</td></tr></tbody></table>

## Description

### What is Kameleoon?

Kameleoon is an experimentation and on-site personalisation platform. mediarithmics connects to it in two ways, and they are not interchangeable - [the comparison is on the Kameleoon page](/connectors/destinations/kameleoon.md).

### What you can do with this connector

* Customise the user experience according to the mediarithmics segment a user belongs to, through a server-to-server connection.

### Which identifiers are sent

* **mediarithmics `vector_id`**

Kameleoon is reached by several connectors and they behave differently - [the comparison is on the Kameleoon page](/connectors/destinations/kameleoon.md).

## Connector setup

### Prerequisites

* A Kameleoon account.

### Authentication

The connection is configured with your mediarithmics account manager, who will tell you which information to supply. Contact them before creating your first server-side Kameleoon feed.

Creating and activating the feed on a segment is covered in the **Audience & Activation** section, under *Activate your audiences › Send your first-party data to a destination*.

## FAQ

#### Should I use the server-side or the client-side Kameleoon connector?

Server-side sends the mediarithmics `vector_id` to Kameleoon and covers the whole audience. Client-side keeps every identifier inside your CDP, but only reaches users who visit your site. See [Kameleoon - Client Side](/connectors/destinations/kameleoon/client-side.md).

## Partner documentation

Kameleoon documents its own platform at <https://docs.kameleoon.com/>. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.


---

# 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.mediarithmics.io/connectors/destinations/kameleoon/server-side.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.