Connect Trustpilot to Rig

    Sync your full review history, the replies your team wrote and your TrustScore into the warehouse. Reviews are only half a conversation on their own, so the point of landing them next to orders and support tickets is being able to ask what happened before a bad week of ratings.

    Requirements
    A Trustpilot Business account with the API module enabled
    Time required
    5 mins, once you have API access

    Before you start

    Check you have API access first
    Trustpilot sells API access as a paid add-on, and it is not offered at all on the Free and Starter plans. If you are not sure which plan you are on, or the Developers section is missing from your dashboard, talk to your Trustpilot Customer Success Manager.

    • A Trustpilot Business login that can reach Integrations.
    • Your company domain, the one your Trustpilot profile is registered against.

    Create the API application

    1. Log in to Trustpilot Business.
    2. Go to Integrations, then Developers, then APIs.
    3. Under Create a new application, give it a name and click Create application.
    4. Find it under Your applications and expand it.
    5. Copy the API key.

    The key, not the secret
    Trustpilot shows you both, and only one of them is what Rig wants. The secret exists for the OAuth flows that let an application post replies on your behalf, which Rig does not do because it only reads. Copy the key and leave the secret where it is.

    You do not need your business unit ID
    Almost every Trustpilot API call is addressed to a business unit, and Trustpilot gives you no screen that displays yours. You can skip the hunt: give Rig your company domain and Rig looks the business unit up for you at sync time.

    Connect it in Rig

    1. In Rig, open Connections and go to Sources & actions.
    2. Search for Trustpilot and open the card.
    3. Trustpilot API key: paste the key you copied.
    4. Company domain: the bare domain, with no protocol and no path.
    5. Click Test, then Sync.

    What Rig pulls in

    Trustpilot lands in its own trustpilot schema in your warehouse, in two tables.

    Reviews carries three things worth knowing about separately:

    • The review: stars, title, body text, language, when it was written and when the experience happened, whether it is verified, and whether it counts towards your TrustScore
    • The reply your team wrote, including its text, who wrote it and when. This is what makes response rate and reply speed answerable rather than estimated
    • The reviewer: their display name, their location and how many reviews they have written on Trustpilot

    Business unit carries the headline numbers already computed: your TrustScore, your average stars, the total review count and the full one to five star breakdown. You do not have to rebuild those from rows to match what your Trustpilot page shows.

    The first sync takes your entire review history, not a recent window. One connection covers one domain, so a second brand or a second market with its own Trustpilot profile is a second connection.

    Good to know

    • Rig syncs at about one request a second, which is deliberate. Trustpilot throttles above that and asks integrations to stay under ten thousand calls an hour, so a large back catalogue takes a little while on the first run and is unremarkable after that.
    • Your API plan has an annual call budget, tiered by the module you bought. Nightly syncing of one business unit sits well inside the smallest tier.
    • Edited reviews and late replies are picked up. Rig merges on the review ID rather than only appending, so a review that gains a reply after the fact updates in place instead of arriving twice.

    Troubleshooting

    • The key is rejected: you probably copied the secret. Expand the application again and take the value labelled API key.
    • No business unit found: check the domain. It should be the bare domain, so example.com rather than https://example.com/reviews, and it has to be the one your Trustpilot profile is registered against.
    • Every call is refused: the application exists but the API module is not enabled on your plan. Creating an application in the dashboard does not by itself grant API access, which is the confusing part. Your Customer Success Manager can confirm.
    • Review counts do not match your Trustpilot page: your page shows reviews used for the TrustScore, which is not every review you have received. Both numbers are in the business unit table, so compare like with like.

    What people use this for

    • Track review volume and rating trends
    • Measure response rate and reply speed
    • Analyse sentiment and recurring themes
    • Watch the TrustScore and the star breakdown

    More ideas for using Trustpilot

    Was this guide helpful?