> 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/client-side.md).

# Client Side

Personalise the Kameleoon experience by segment, through the browser's local storage.

The client-side Kameleoon connector lets you customise the user experience according to the segment a visitor belongs to. No identifier leaves your CDP: the segment list is written to the browser's local storage, and Kameleoon reads it from there.

<table data-search="false"><thead><tr><th width="220">Connection</th><th></th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>Client-side (local storage)</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>None - segment names only, kept in the browser</td></tr><tr><td><strong>Authentication</strong></td><td>None</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

* Personalise on-site experience by mediarithmics segment, without sharing identifiers with Kameleoon.

### Which identifiers are sent

None. The connector stores segment data in the visitor's local storage; Kameleoon retrieves it from there. The value holds the **technical name** of each segment - assigned by default if you did not set one when creating the segment, and editable afterwards.

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

## Connector setup

### Prerequisites

* The mediarithmics tag installed on the site, calling `syncFeeds` - the call that enables client-side feeds. See the **Setup & Monitor** section, under *Collect & manage your data › Collect data in real time › Web tracking*.
* A Kameleoon account.

### Setup steps

{% stepper %}
{% step %}
**Select the Browser Local Storage connector in the client-side section.**
{% endstep %}

{% step %}
**Fill in the configuration.**

<table data-search="false"><thead><tr><th width="260">Field</th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Identifies the feed in the platform. Any name.</td></tr><tr><td><strong>Local Storage Field Name</strong></td><td>Must be <code>mics_kam_seg</code>.</td></tr></tbody></table>

{% hint style="danger" %}
The key must be exactly `mics_kam_seg`. Kameleoon will not find the segments under any other name.
{% endhint %}
{% endstep %}
{% endstepper %}

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*.

## Good to know

This connector is the [Browser Local Storage](/connectors/destinations/browser-local-storage.md) connector with a fixed key. Its timing rules apply here too: a user appears in the key only after the segment has been recalculated following their qualifying visit, and the segment list refreshes once every 24 hours.

## FAQ

#### Can I use a different local storage key?

No. It must be `mics_kam_seg`.

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

Client-side keeps every identifier inside your CDP but only reaches users who visit your site. Server-side sends the mediarithmics `vector_id` to Kameleoon. See [Kameleoon - Server Side](/connectors/destinations/kameleoon/server-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.

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Browser Local Storage</strong></td><td>The underlying connector, its timing rules and its other uses.</td><td><a href="/connectors/destinations/browser-local-storage.md">Browser Local Storage</a></td></tr></tbody></table>


---

# 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/client-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.