> 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/user-login/frictionless-player-id.md).

# Frictionless Player ID

The Frictionless UID feature aims to streamline the purchase flow on your web store by automatically passing the player's unique identifier (player ID) or Nickname from your app to the web store via a URL parameter.

## When should you use Frictionless Player ID?

You do not need your users to login to complete a purchase on your web store. You also want to reduce the friction of users finding their unique identifier within your app, and then entering it on the web store.

With Frictionless Player ID, your users will arrive on the web store, from in-app, fully identified and ready to immediately initiate a purchase.

## Integration requirements

* You must extract the nickname of the currently logged-in user from your app.
* You must append the nickname as a URL parameter when redirecting to the web store.
* You must use the format: `https://store.example.com?userId=<nickname>`
* All redirects must use HTTPS.

### Web store handling

The web store will automatically:

* detect the `userId` parameter in the URL.
* extract the value.
* pre-fill the corresponding text field in the product page.


---

# 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.coda.co/coda-webstore/user-login/frictionless-player-id.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.