> 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/coda-webstore/personalized-sales-on-web-store.md).

# Personalized Sales on Web Store

Tailor your web store to every user– make how they play, when they buy, and what they value count.

With Personalized Sales on Coda-powered web stores, you can sync in-app behavior and player identity to deliver targeted SKUs, smart discounts, and surprise offers automatically. Whether you're re-engaging lapsed users or rewarding VIPs, every visit becomes more relevant, more engaging, and more likely to convert.

Talk to our team about activating Personalized Sales →

<figure><img src="/files/7pRsJI7fnS3XtwyZZNwE" alt=""><figcaption></figcaption></figure>

## Boost Performance with Personalized Sales &#x20;

**Why Use Personalized Sales?**\
\
Tailored experiences convert better. With the UserSync API, you can link in-app activity, purchase history, and user identity directly to your web store. The result? Offers that matter—and performance that shows it.&#x20;

Use it to:

* **Display in-app nicknames →** Build trust by greeting users with their in-game username, level, class, avatar, and more&#x20;
* **Offer rule-based SKUs and discounts →**&#x20;
  * Trigger offers based on purchase history in-game, level in-game, achievements in-game, etc.&#x20;
  * **Launch surprise SKUs →** Deliver flash deals or exclusive items based on real-time logic
  * **Re-engage, retain, reward →** Target dormant users, high spenders, or birthday bonuses
  * **Recommend complementary SKUs →** Suggest upgrades or add-ons based on current inventory

### How Personalized Sales Works

**Two flexible approaches, same powerful result:**

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

1. **Pre-Defined Segments:**\
   Set up special SKUs in the Coda Portal based on user categories like new buyers, VIPs, or level-based achievements.\
   → When a user logs in or enters their ID, Coda calls UserSync API, where the publisher will return relevant information, ultimately resulting in the player only seeing what’s relevant to them.<br>
2. **Dynamic Personalized SKUs:**\
   Send real-time SKU logic from your backend using the [UserSync API](/codashop-and-distribution/integration-guides/usersync-api-request.md) after Coda passes the relevant player ID information.\
   → Your store adapts on the fly, displaying tailored offers instantly, no need to pre-load products in the 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/coda-webstore/personalized-sales-on-web-store.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.