> For the complete documentation index, see [llms.txt](https://litepaper.pixels.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://litepaper.pixels.xyz/ecosystem-flywheel-and-data-loop/smart-reward-plaform.md).

# Smart-Reward Plaform

A reward is a micro-ad with perfect attribution. Instead of paying an ad exchange to show an impression, the studio pays the player after the player performs a verifiable action that lifts a key metric, ie. finish the tutorial, come back seven days in a row, invite three friends, make a first purchase, and so on. The budget that would have gone to Google’s or Meta’s rake now goes 100% to the user who moved the needle.

* Players see an immediate, tangible upside for their time and data.
* Studios buy retention, k-factor, or LTV at a known unit cost instead of renting eyeballs.
* Every token can be traced from treasury-to-wallet, so customer-acquisition cost (CAC) is transparent by design.

The concept works in Web3 first as on-chain rewards are cheap to move and easy to audit, and have less up-front capital risk than using fiat currencies. This model then extends to Web2 once the models are proven.

### The Platform

Pixels aggregates first-party data from all games within the ecosystem to create a powerful, unified dataset. Participating games contribute valuable insights into player demographics, behaviors, monetization patterns, and retention metrics through the versatile Pixels Events API—a straightforward REST endpoint supporting batch and real-time data collection. By integrating this data across multiple titles, Pixels continuously strengthens its ability to deliver precise and impactful rewards.

The strength of this aggregated data allows Pixels to develop sophisticated predictive models that forecast player lifetime value (LTV), retention probabilities, and spending behavior, thereby optimizing reward allocation. The collective intelligence gathered from multiple games creates a reinforcing data loop that continually refines reward efficiency and effectiveness.

### Studio Integration & Toolkit

Pixels is building a toolkit for other studios. Studios can integrate the Pixels Events API, a straightforward REST endpoint supporting batch and real-time event logging.\
\
 Our comprehensive ID graph integrates wallet, device, and social identifiers, enabling seamless user experiences even for traditional Web2 studios that don't yet support blockchain logins. The scale and quality of this unified dataset significantly enhance our ability to accurately predict user behavior and optimize reward targeting.

| Step            | What the studio does                                        | Turn-around |
| --------------- | ----------------------------------------------------------- | ----------- |
| 1. Drop-in SDK  | REST API integration                                        | < 1 day     |
| 2. Define goals | Pick events to reward (D7 retention, share, purchase, etc.) | 30 min      |
| 3. Fund pool    | stake own $PIXEL or borrow from ecosystem emissions         | instant     |
| 4. Watch RORS   | Dashboard shows live spend vs revenue                       | live        |

Studios keep full ownership of their data, yet benefit from the cross-game model improvements.


---

# 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://litepaper.pixels.xyz/ecosystem-flywheel-and-data-loop/smart-reward-plaform.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.