Judge.me Review Monitor - Ratings & Merchant Replies

Reviews that need a closer look

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.

Open this Actor in Console · First run · Results · Cost · Full guide

Try this Actor

• 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.

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

Result preview

The dataset view highlights these columns:

• Product · productTitle
• Product URL · productUrl
• Review ID · reviewId
• Stars · stars
• Review title · title
• Review text · body

Use the original source links and the field definitions below when interpreting the results. CSV works well for flat columns; JSON preserves nested values.

Usage and pricing

Base result rate on the FREE tier: $3 per 1,000 review observations. The Pricing tab shows your plan's result rate and any Actor Start charge. Set a small result limit for the first run; the requested limit is not a guarantee of that many results.

---

Full guide

Turn published product reviews into a repeatable feedback and reply-triage feed. The Actor reads the documented Judge.me public widget using configuration already exposed in product HTML. No merchant API key or login is required. Empty input {} reads up to ten public Owala FreeSip reviews.

What each row contains

One published review: stable reviewId, supplied productUrl, widget product ID/title, stars, review title/body, published date when provided, public merchant reply and date when provided, verified-buyer flag when exposed, observation time and optional comparison details. isLowRating uses your threshold; needsMerchantReply requires both a low rating and no visible reply. These are flags, not filters.

Reviewer names, contacts, location, avatar, and order/customer information are omitted. The storefront's public widget token is used only in a request header and is never included in output, history or logs. The Actor does not request private review APIs, unpublished reviews, customer records or merchant credentials.

The product page must expose jdgm.SHOP_DOMAIN, jdgm.PUBLIC_TOKEN and one unambiguous .jdgm-review-widget product ID in its HTML. Browser-only or customized integrations that hide those values are unsupported. Public review text is source content, not verified evidence that a purchase or event occurred.

Inputs and historical coverage

• 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.

Three example inputs

Owala FreeSip - Public Review Sample

Read up to ten published widget reviews with ratings, text and merchant reply status.

Use the copyable first-run input above.

Owala FreeSip - Low Rating Reply Triage

Inspect a 50-review window and flag ratings of one or two stars that lack a visible merchant reply. All inspected reviews are returned.

{
  "productUrls": [
    "https://owalalife.com/products/freesip"
  ],
  "maxReviewsPerProduct": 50,
  "maxResults": 50,
  "lowRatingThreshold": 2
}

Owala FreeSip - Merchant Reply History

Compare a 20-review window against saved observations and identify visible review edits and merchant reply changes. First run establishes a baseline.

{
  "productUrls": [
    "https://owalalife.com/products/freesip"
  ],
  "maxReviewsPerProduct": 20,
  "maxResults": 20,
  "comparePrevious": true,
  "snapshotName": "owala-replies"
}

Saved observations and change detection

comparePrevious: true enables persistent, named comparison history. onlyChanges: true also enables comparison and suppresses unchanged rows. The first observation emits comparisonStatus: "baseline"; later rows are new, changed, or unchanged. Without comparison they are not_requested. changedFields, changeTypes and previous explain each comparison.

Only confirmed saved rows update history. Existing records outside the selected window are retained. A partial run never establishes removals, and neither Actor emits deletion events. Comparison means last successfully saved observation, not an uninterrupted history of every change between runs. The state limit is 50,000 identities per source and snapshot name.

Run a given snapshot name sequentially. A reread detects an already changed snapshot before writing and reports a conflict, but this is not a transactional lock. Dataset and history writes are separate: a storage failure can leave saved rows without a new baseline; retrying may repeat observations. Use distinct names for independent workflows.

Coverage, limits and failures

maxResults caps saved rows across sources. Source/product/page limits select a bounded sample and are reported through SUMMARY.sourceCoverage, including hasMore; reaching a selected cap is not itself an operational failure. Always inspect SUMMARY before interpreting an empty or partial dataset. The output tab links to both results and SUMMARY.

Requests honor robots.txt, reject nonpublic network destinations and unsafe redirects, and stay within maxRunSeconds (default 240, range 30–3600) and 25 seconds before the platform deadline. HTTP 429, server errors and transient connection failures receive at most two bounded retries, honoring Retry-After. No browser rendering, login, proxy or anti-bot bypass is used.

Failures appear in failedSources, never as data rows. If all sources fail before usable output, the run fails. Genuine empty results or no changes produce a warning and succeed. Spending limits stop output cleanly, preserve existing rows, and prevent unsaved observations from advancing history. A source outage, robots restriction or time limit can produce partial coverage.

Development

Node 20 Docker image; exact Apify SDK 3.7.2 and Cheerio 1.1.2 lockfile. npm ci installs dependencies and npm test runs offline regression tests. npm start reads the normal Apify INPUT record. Public storefronts may change independently of this Actor.

Pricing

Planned pay-per-result rate: $3.00 per 1,000 saved review observations, plus the configured Actor-start event. The current Apify pricing tab is authoritative. An unchanged row is billable when saved; onlyChanges avoids saving unchanged rows. Errors are not dataset results.

Source documentation

Judge.me API help · Official OpenAPI definition

Help with your run

Open the Issues tab on this Actor with the run URL, the input field that caused trouble and what you expected to receive. Remove API keys and private information before posting.

Explore more Mayd-It Actors

Understand your run

Open Run report in the run’s Output tab for saved-record counts, reported source issues and limits, and suggested next steps. Use CSV export to take the saved results into a spreadsheet. The existing JSON results and detailed machine-readable summary remain available.

The report reflects this run’s recorded coverage. A successful run or a saved result does not establish that every possible source record was collected.