> For the complete documentation index, see [llms.txt](https://community.commandersact.com/customer-success/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.commandersact.com/customer-success/inspiration/audience-sharing/optimising-the-user-experience.md).

# Optimising the user experience

To remedy this, we show you how to leverage the reconciliation capabilities of our solutions.

Here, you will learn how to unify your data around a unique identifier to push enriched segments to AB Tasty, Kameleoon Audience or Target2Sell.

#### **Benefits:**

* **Cross-channel recognition:** Thanks to the reconciliation capabilities of our solutions, you can welcome your loyal customers with personalised messages based on their actual interactions, regardless of the point of sale.
* **Highly relevant recommendations:** Feed Target2Sell with additional offline events to offer products that truly complement your customers' past purchases.
* **Reliable experiments:** Optimise your A/B tests in AB Tasty or Kameleoon by targeting segments based on customer value (LTV) calculated from all your stored data.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://community.commandersact.com/customer-success/inspiration/audience-sharing/optimising-the-user-experience.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.