> For the complete documentation index, see [llms.txt](https://docs-en.shoppy.is/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-en.shoppy.is/shoppy-dashboard/integrations/trustpilot.md).

# Trustpilot

## Overview

**Turn trust into sales!** Shoppy now integrates with **Trustpilot**, allowing you to display authentic customer reviews directly in your app. Strengthen your brand's reputation and help customers make informed purchase decisions by leveraging the power of real reviews.

## How to Enable Trustpilot Integration

{% embed url="<https://cdn.mburger.cloud/359597/Shoppy-X-Trustpilot.mp4?data=eyJtZWRpYV9pZCI6MzU5NTk3LCJieXRlcyI6MjAyMzgzOTUsInByb2plY3RfaWQiOjI3ODcsImhhc19pbWdpeCI6MH0=>" %}
Trustpilot integration
{% endembed %}

1. Go to the **Integrations** section in your **Shoppy Admin Dashboard**.
2. Enable **Trustpilot** integration.
3. Once enabled, a new **Trustpilot widget** will appear among the available widgets in the **Home Page Builder**.
4. Add the **Trustpilot widget** to your home page.
5. Insert the **"Head" HTML code** and **"HTML Widget Code"** provided in your Trustpilot dashboard.

Now, your app will display verified reviews, enhancing credibility and customer trust!


---

# 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-en.shoppy.is/shoppy-dashboard/integrations/trustpilot.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.