> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/codashop-and-distribution/personalized-sales.md).

# Personalized Sales

Out-of-app personalization on dedicated web stores and third-party distribution channels offers partners a powerful way to enhance user engagement and drive revenue growth. With Coda’s comprehensive suite of tools, partners can deliver a uniquely tailored shopping experience using the [**UserSync API**](/codashop-and-distribution/integration-guides/usersync-api-request.md). This API synchronizes in-app user activity, purchase history, and identity details so that personalized offers, discounts, and exclusive SKUs can be showcased on webstores.

### <mark style="color:purple;">**Key Benefits and Use Cases of Personalized Sales**</mark>

#### <mark style="color:purple;">**1. Display In-App Nicknames**</mark>

* **Objective:** Boost conversions by displaying users' familiar in-app names or nicknames.
* **Benefit:** Enhances trust and personalization, making the experience feel more engaging and recognizable.

#### <mark style="color:purple;">**2. Rule-based SKU Discount eligibility based on purchase history and in-app activity**</mark>&#x20;

* **Objective:** Configure rules to display specific SKU discounts based on user's purchase history and in-game activity (e.g., New user or First-time buyer).
* **Benefit:** Targeted discounting strategy to boost new user acquistion

#### <mark style="color:purple;">**3. Dynamic Surprise SKUs**</mark>

* **Objective:** Fetch and display exclusive SKUs in real-time based on user engagement, re-engagement needs, or flash promotions.
* **Benefit:** Creates excitement and urgency by offering dynamically generated SKUs personalized to the user.

#### <mark style="color:purple;">**4. Additional Use Cases**</mark>

* **Re-Engagement Promotions:** Trigger special offers for users who have been inactive or have not made a purchase in a while.
* **VIP & High-Spender (Whale):** Identify high-value or repeat customers and showcase exclusive SKUs or discounts encouraging continued spending and increased retention.
* **Event-Based Personalization:** Use metadata, such as the user's birthdate, to offer exclusive bonuses or discounts during special occasions
* **Complementary SKUs suggestions**: Recommend SKUs that complement a user's existing in-app inventory, enhancing their experience and increasing conversion rates

## <mark style="color:purple;">How Personalized Sales Works?</mark>

The [**UserSync API**](/codashop-and-distribution/integration-guides/usersync-api-request.md) is triggered when a user logs into the Codashop/Store or enters their game/user ID. It enables two primary personalization approaches:

1. **Pre-Defined Segments:**
   * Partners configure special Product SKUs on the Coda Portal based on predefined user segments (e.g., first-time buyers, high spenders, level-based offers).
   * Coda shows the relevant Product SKUs based on the segment information provided by the partner during the purchase flow.
2. **Dynamic Personalized SKUs:**
   * Partners send real-time product SKUs based on in-game activity, allowing for a dynamic, out-of-app personalization experience.
   * The Shop displays tailored SKUs upon user login, without requiring partners to maintain SKU configurations separately on Coda Portal.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.coda.co/codashop-and-distribution/personalized-sales.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.