> For the complete documentation index, see [llms.txt](https://docs.nosto.com/techdocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nosto.com/techdocs/implementing-nosto/implement-on-your-website.md).

# Implement on your website

## Choosing the implementation method

Most customers implement Nosto by installing a Nosto extension to their e-commerce platform. The extension provides a working out of the box implementation for majority of websites handling installing tagging and product updates. However, for customized PWA/SPA environments, you should follow the additional SPA/PWA guides.

| Implementing by a Nosto Extension | <p><a href="https://docs.nosto.com/magento/">Magento</a></p><p><a href="https://docs.nosto.com/magento-2/">Magento 2</a></p><p><a href="https://docs.nosto.com/shopware">Shopware</a></p><p><a href="https://docs.nosto.com/shopify">Shopify</a></p><p><a href="https://docs.nosto.com/prestashop">Prestashop</a></p><p><a href="https://docs.nosto.com/bigcommerce">BigCommerce</a></p><p><a href="https://docs.nosto.com/salesforce">Salesforce</a></p> |
| --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

| Implement on your SPA | [Session API](/techdocs/apis/frontend/implementation-guide-session-api.md) |
| --------------------- | -------------------------------------------------------------------------- |

| Implement on your PWA | [Session API](/techdocs/apis/frontend/implementation-guide-session-api.md) |
| --------------------- | -------------------------------------------------------------------------- |

| Implement on your Headless | [GraphQL](/techdocs/apis/graphql-an-introduction.md) |
| -------------------------- | ---------------------------------------------------- |

| Implement on a standard e-commerce store | [Manual Implementation](/techdocs/implementing-nosto/implement-on-your-website/manual-implementation.md) |
| ---------------------------------------- | -------------------------------------------------------------------------------------------------------- |

When implementing in SPA and PWA environments, product updates must be done via [REST API](/techdocs/apis/rest.md). In case you are using some of the platforms that Nosto has extension for the extension takes care of the product updates.

## SPA / PWA on top of a platform that Nosto has extension for

If you have implemented SPA / PWA on top a platform that Nosto has extension for you will still need to implement the frontend part using Session API. The extension will take care of the product updates, order confirmations, exchange rates and other background processes but displaying the recommendations, popups, etc. must be done using Session API.

## When dynamic functionality is needed / no page reload

In case your website implement some dynamic functionality, you can use the [JS API](/techdocs/apis/frontend/js-apis.md). Note that you cannot mix Session API and Page Tagging.


---

# 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.nosto.com/techdocs/implementing-nosto/implement-on-your-website.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.