> 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-links/link-users-out-to-coda-powered-webstore.md).

# Link users out to Coda-powered Webstore

If you have a Coda-powered Webstore, you can easily create parameterized URLs based on your Webstore domain. These URLs redirect users from your app to a simplified express checkout page on your Coda Webstore, serving as a designated checkout page.

## User Experience

<figure><img src="https://611292228-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl56STCN5yoV1K1MhVEvU%2Fuploads%2FI7fqYClCjhajn7BGdaSK%2Fimage.png?alt=media&amp;token=61ee1c7e-41d7-4627-9a99-4f3f31a941d1" alt=""><figcaption></figcaption></figure>

## Key Benefits

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><strong>Simple URL-Based Setup</strong></td><td>You only need to generate the correct URL format with the required data points (Session Token, SKU ID, and Locale) to open the express checkout page on your Webstore. No API required.</td><td data-object-fit="contain"><a href="https://611292228-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl56STCN5yoV1K1MhVEvU%2Fuploads%2F1v65jws9wihO0fE2EFJA%2F18403138-ec5c-4cf8-b483-c41ce141a705.png?alt=media&amp;token=af604301-d451-43bf-8b17-0f938966e5a3">18403138-ec5c-4cf8-b483-c41ce141a705.png</a></td></tr><tr><td><strong>Build Out-of-App Loyalty from Day One</strong></td><td>Coda Links via Webstore helps you capture players beyond the app. All Coda Links checkout comes with a post-purchase funnel that converts in-app users into repeat, high-margin Webstore purchasers.</td><td data-object-fit="contain"><a href="https://611292228-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl56STCN5yoV1K1MhVEvU%2Fuploads%2FQPXeM2d5NV03QWCF5DTU%2F5da11076-bfad-469f-98ea-bf42094faa2b.png?alt=media&amp;token=9de00961-b071-4dfd-8a0c-87ba3f5caad0">5da11076-bfad-469f-98ea-bf42094faa2b.png</a></td></tr><tr><td><strong>Optimized Conversion</strong></td><td>The express checkout removes storefront distractions, focusing the user entirely on the selected SKU and the payment process, which increases conversion rates.</td><td data-object-fit="contain"><a href="https://611292228-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl56STCN5yoV1K1MhVEvU%2Fuploads%2FB1pzdKGpcfcg9sr6NekD%2F6f21194d-62d7-48ed-a9d6-c8a0fad5240b.png?alt=media&amp;token=ea2c531d-52bd-462c-9e6a-1a9c25a81ab9">6f21194d-62d7-48ed-a9d6-c8a0fad5240b.png</a></td></tr><tr><td></td><td></td><td></td></tr></tbody></table>


---

# 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-links/link-users-out-to-coda-powered-webstore.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.
