# Judge.me Review Monitor - Ratings & Merchant Replies — workflow

## Choose this tool

For teams reviewing product feedback: collect published Judge.me ratings, review text and merchant replies from supported public product widgets. Low-rating flags help you inspect unanswered feedback without collecting reviewer contact or order data.

Useful output columns: `productTitle`, `productUrl`, `reviewId`, `stars`, `title`, `publishedAt`.

## Practical workflow

- **First run:** Use the existing **Owala FreeSip - Public Review Sample** below: one product, up to 10 reviews and 10 saved rows. Keep comparison off while you inspect the first result.
- **Read the results:** Open the default Dataset for review rows and the **SUMMARY** record in the default key-value store for source coverage. The review text and merchant reply columns provide the evidence behind each flag.
- **Keep in mind:** This is the widget's visible review window, not a complete review archive. A review missing from a later window does not prove deletion; comparison covers saved observations.

**Owala FreeSip - Public Review Sample** — copy this input into the JSON editor in Console.

```json
{
  "productUrls": [
    "https://owalalife.com/products/freesip"
  ],
  "maxReviewsPerProduct": 10,
  "maxResults": 10
}
```

## Check the fit

- `productUrls`: up to 30 public product page URLs. Empty input uses the Owala example.
- `maxReviewsPerProduct`: 10 by default, up to 1,000 inspected identities, including unchanged ones.
- `maxPagesPerProduct`: 10 by default, up to 100 public widget pages.
- `maxResults`: 100 saved reviews by default, up to 10,000.
- `lowRatingThreshold`: 3 by default, from 1 to 5. All inspected reviews are returned unless onlyChanges suppresses unchanged ones.
- `comparePrevious`, `onlyChanges`, `snapshotName`, `maxRunSeconds`: described below.

Coverage is the **published review window exposed by the widget**. The source controls ordering and visibility. `reportedReviewCount` is source metadata, not a promise that this run retrieved that many reviews. Pagination can shift as reviews are published. Replies or edits to reviews outside the selected window are not detected; increase the window for broader checks. A disappearing review is not treated as deleted. Dates or reply dates absent from widget markup remain null.

## Real output sample

One selected row from a 2026-10-17 run. One saved row, selected scalar columns only. Contact details, patient demographics and long text are omitted. Original values and nulls are preserved.

Run: N6PWUByJa3rqspa0Z. Summary status: ok. Incomplete: false.

Historical output from this run; the current example input is a separate starting configuration and may produce different records.

```json
{
  "productTitle": "FreeSip®",
  "productUrl": "https://owalalife.com/products/freesip",
  "reviewId": "c54a6fab-9373-5c01-8fe8-6566122074cd",
  "stars": 5,
  "title": null,
  "publishedAt": "2026-10-17T02:52:59.000Z",
  "merchantReply": null,
  "needsMerchantReply": false,
  "comparisonStatus": "new",
  "observedAt": "2026-10-17T14:11:59.130Z"
}
```

## Combine with companion tools

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

### [UCP Commerce Profile Monitor - Capabilities & Changes](https://mayd-it.com/data-tools/actors/ucp-commerce-profile-monitor/)

Monitor merchant UCP profiles: declared commerce capabilities, protocol versions, service endpoints and saved changes. Read-only discovery; no checkout calls or API keys. Keep this UCP Commerce Profile Monitor evidence alongside the original source in a reviewed commerce catalog review workflow.

1. Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured.
2. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

Products and variants across stores are not automatically equivalent. Keep currency, variant, condition and observation date; public listings do not prove sales or revenue.

### [Pinterest Board & Profile Pin Monitor](https://mayd-it.com/data-tools/actors/pinterest-board-pin-monitor/)

Export recent Pinterest pins from public boards and profiles with image URLs, dates, keyword evidence and saved changes. No login, proxy or API key required. Keep this Pinterest Board & Profile Pin Monitor evidence alongside the original source in a reviewed commerce catalog review workflow.

1. Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured.
2. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

Products and variants across stores are not automatically equivalent. Keep currency, variant, condition and observation date; public listings do not prove sales or revenue.
