> 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/partner-types/on-site-personalisation.md).

# On-site personalisation

Adapting your own site to the segment a visitor belongs to, without sending anything to a third party.

This is the one partner type where, in most cases, **no identifier leaves your CDP at all**.

Instead of sending an audience to a platform that will act on it elsewhere, mediarithmics writes the list of segments a visitor belongs to into **that visitor's own browser**, under a key of your choosing. A personalisation or experimentation tool already running on your page reads the key and adapts the experience.

## How it works

1. You activate a client-side feed on a segment.
2. A visitor arrives on a page carrying the mediarithmics tag. The tag calls the platform with every ID available in the browser.
3. The platform resolves the identity, works out which segments the visitor is in, and returns them to be written to local storage.
4. Your on-site tool reads the key and decides what to show.

{% hint style="warning" %}
**A newly activated segment does not appear immediately.** Three things must all have happened: the visitor had a qualifying visit, the segment was **recalculated after** that visit, and the visitor came back **more than 24 hours later**. The segment list refreshes once every 24 hours, based on `lastFeedRefreshDate`.
{% endhint %}

## Connectors

<table data-search="false"><thead><tr><th width="300">Connector</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/destinations/browser-local-storage.md">Browser Local Storage</a></td><td>The general case, with a configurable key. Use it for partners with no dedicated connector, or for a custom process.</td></tr><tr><td><a href="/connectors/destinations/ab-tasty.md">AB Tasty</a></td><td>The same mechanism with the key fixed to <code>mediarithmics-segments</code>, plus the JavaScript each AB Tasty campaign needs.</td></tr><tr><td><a href="/connectors/destinations/kameleoon/client-side.md">Kameleoon - Client Side</a></td><td>The same mechanism with the key fixed to <code>mics_kam_seg</code>.</td></tr><tr><td><a href="/connectors/destinations/kameleoon/server-side.md">Kameleoon - Server Side</a></td><td>The exception: a server-to-server connection sending the mediarithmics <code>vector_id</code>.</td></tr></tbody></table>

**Prebid.js** is not a connector but a documented consumer of what the platform writes to the browser - see [Curated Audiences (SDA)](/connectors/destinations/curated-audiences-sda.md), which includes a worked example.

## What to watch

* **On-site only.** Local storage is readable by code running on your pages. Nothing reaches a partner's servers, which is the point, but it also means this type cannot be used for off-site activation.
* **Exits cannot be signalled.** The mechanism only knows which segments a visitor is in at the moment of the visit. To exclude previously matched users, build an exclusion segment and use it in the tool's own targeting.
* **Blocked tags send nothing.** An ad blocker or a refused consent means the tag does not fire.


---

# 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/partner-types/on-site-personalisation.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.