Skip to main content
Trustvox, part of Reclame AQUI, is a platform that collects verified reviews from e-commerce customers: after a purchase it asks shoppers to review the products and the store, and shows those reviews and the shoppers’ questions on the store’s product pages. This connector reads your store through the Trustvox API and brings your product reviews (with photos and survey answers), store reviews, the orders sent to Trustvox, product questions and answers, products with their rating totals, marketplace sellers and their reviews, and tags.
The connector only reads data. It never creates, changes or deletes anything in Trustvox.

Configuring Trustvox as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Trustvox option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

The connector uses your store’s Store Token and Store ID. An administrator of your store finds the token in the Trustvox panel, in the Preferências da Empresa menu. If it is not there, ask Trustvox support for the store token of your store at meajuda@reclameaqui.com.br. The Store ID is the number of your store in Trustvox; Trustvox support can confirm it too. The following configurations are available:
  • Store ID: The number of your store in Trustvox.
  • Store Token: The store token of your store.
  • Start Date: Earliest creation date read for product reviews, store reviews and orders on the first sync and on full syncs. The other tables are always read in full.
  • Lookback Days (advanced, optional): On each sync, product reviews and store reviews created this many days before the last sync are read again, to pick up recent changes such as votes and moderation. From 0 to 365. Default: 30.
  • Orders Lookback Days (advanced, optional): The same for orders, which keep changing for weeks after they are created (status, and the reviews the customer leaves). From 0 to 365. Default: 90.
Once you’re done, click Next.

2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data, which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data, which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

How the data is kept up to date

  • Product Reviews, Store Reviews and Orders are read by creation date: each sync reads what was created since the last sync, plus the lookback period before it (Lookback Days for reviews, Orders Lookback Days for orders). Trustvox only filters by creation date, so a change made to an older record (a vote on a review, a moderation, an order that changed status) is picked up only within the lookback period, or by a full sync. The reviews themselves are never missed: they are always in Product Reviews and Store Reviews, even when the order that brought them is older.
  • Questions, Products, Sellers, Seller Reviews and Tags are read in full on every sync, so answers given at any time and updated rating totals always arrive.
Schedule an Additional Full Sync (for example, once a week) in step 4. It brings the latest state of older reviews and orders and removes from your tables the records deleted in Trustvox.
If your store token cannot read some tables (Trustvox answers “You do not have access to this resource”), or your store does not have them (for example, Sellers and Seller Reviews only exist on marketplace stores), those tables are skipped and named in the sync log, and the other tables keep syncing. Ask Trustvox support to enable the access, or deselect those tables. If the token cannot read any selected table, the sync fails and asks you to check the Store Token and Store ID.

Fields by stream

Nested objects sent by Trustvox are split into columns where they are small (customer, product, answer, store review) and kept as JSON text where they are lists or larger objects (order items, photos, survey answers). Any field Trustvox sends that has no column of its own is kept in extra_fields.
Every product review (opinion) of the store, with the rating, text, recommendation, votes, photos, survey answers, the customer and the order it came from.Table: product_reviews · Primary key: id · Sync: Incremental (by created_at)
Reviews of the store itself (purchase and delivery experience), with the rating, text and customer.Table: store_reviews · Primary key: id · Sync: Incremental (by created_at)
Orders the store sent to Trustvox to request reviews, with customer, tags, products, the review links and the reviews left for each order.Table: orders · Primary key: id · Sync: Incremental (by created_at)
Questions shoppers asked about products, with the store’s answer when there is one.Table: questions · Primary key: id · Sync: Full table
Products of the store in Trustvox with their rating totals.Table: products · Primary key: id · Sync: Full table
Marketplace sellers of the store with their rating summary (average, NPS, histogram and survey summaries). Marketplace stores only.Table: sellers · Primary key: id · Sync: Full table
Reviews of marketplace sellers. Marketplace stores only.Table: seller_reviews · Primary key: id · Sync: Full table
Tags of the store, orders, products and customers.Table: tags · Primary key: belonging_to, id · Sync: Full table

Implementation Notes

  • Dates and times are stored in UTC. Trustvox filters by days in São Paulo time; the store reviews list sends only the day of each review, which is stored as midnight in São Paulo time.
  • Ratings, averages and prices keep their exact decimal values.
  • Trustvox does not publish a rate limit. The connector sends one request at a time and waits when Trustvox asks it to slow down.