Ecwid Product Review Extractor & Monitor

Turn a public Ecwid storefront into a clean, row-per-review dataset. Ecwid Product Review Extractor & Monitor finds the public storefront ID, checks every visible product, and returns reviewer names, 1–5 ratings, review text, dates, product IDs, product URLs, and a review-count summary for every reviewed product.

Paste a storefront URL and export public reviews as JSON, CSV, Excel, XML, or RSS. You do not need an Ecwid account, a merchant API key, browser automation, or a proxy for normally reachable public storefronts. The Actor reads only reviews that public shoppers can already see.

Why use this Ecwid product review extractor?

• Get one normalized record per public product review with reviewer, rating, text, date, product ID, storefront ID, and product URL.
• Receive an additional product summary for each reviewed product. It contains the current review count and review sources, so spreadsheets and dashboards can rank products without grouping raw rows.
• Read both Ecwid's built-in published reviews and public Fera product-review widgets. The review source field tells workflows which public system supplied each row.
• Start with an Ecwid Instant Site, a normal storefront domain, an embedded catalog page, or a numeric Ecwid store ID. Tracking parameters and fragments are removed automatically.
• Schedule repeated runs with the same monitor ID to find new, edited, and disappeared review rows and changed product review counts.

The Actor uses direct HTTP requests to public storefront endpoints and retries temporary errors. When one storefront in a multi-store run is unavailable, its failure is logged while the remaining storefronts continue.

Pricing

This Actor uses pay per event pricing: $0.001 per run plus $0.0008 per Dataset record. A Dataset record is either a product-review row or a per-product review summary; the minimum total charge is $0.002.

Dataset records	Actor event price
1	$0.002 minimum
100	$0.081
1,000	$0.801
10,000	$8.001

For example, a product with one review normally produces two Dataset records: the review and its product summary. Prices cover the Actor's chargeable run and Dataset-record events. Standard Apify charges for retention or downloads may apply.

How to use this Actor

Add one or more public Ecwid storefront URLs to the storefrontUrls input. A numeric Ecwid store ID such as 110505292 is also accepted. Use the storefront page that contains the product catalog when the store is embedded in another website.

Quick start

{
  "storefrontUrls": ["https://ferademo.company.site/"],
  "maxReviews": 100
}

Set maxReviews to 0 to export every public review. The prefilled example uses 1 to keep the Store health check small, but the Actor still snapshots the complete review set for accurate scheduled monitoring.

Compare several storefronts

{
  "storefrontUrls": [
    "https://example.company.site/",
    "https://merchant.example/shop/"
  ],
  "maxReviews": 0,
  "useApifyProxy": false
}

Use Apify Proxy only for a merchant domain that rejects direct requests. Ecwid's public storefront and Fera endpoints normally work directly.

Monitor new, updated, and removed reviews

Run the Actor on a schedule with the same monitor ID and storefront URLs. The first successful run creates a baseline. Later successful runs compare the current review rows and product summaries against that baseline.

{
  "storefrontUrls": ["https://ferademo.company.site/"],
  "monitorId": "competitor-review-watch",
  "onlyChangesSince": "2026-09-01T00:00:00.000Z",
  "maxReviews": 0
}

Change type	Meaning
new	The public review or product summary was not in the prior snapshot.
updated	A monitored field changed; changedFields names it.
unchanged	The record is still public and has not changed.
removed	The record was public in the prior snapshot but is no longer returned.

When onlyChangesSince is set, unchanged records are excluded. A removal is emitted once, on the first successful run that detects it.

API example

curl -X POST \
  "https://api.apify.com/v2/acts/Clintsa~ecwid-product-review-extractor/run-sync-get-dataset-items" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"storefrontUrls":["https://ferademo.company.site/"],"maxReviews":10}'

For longer runs, start the Actor asynchronously and read its default Dataset once the run succeeds.

Input options

Field	Type	What it controls
storefrontUrls	string array	Required public Ecwid storefront or catalog URLs, or numeric store IDs.
maxReviews	integer	Review rows exported per storefront; 0 means no review limit.
monitorId	string	Persistent namespace used for review change tracking.
onlyChangesSince	ISO timestamp	Returns only new, updated, or removed records detected since the timestamp.
requestDelayMillis	integer	Optional delay between storefronts.
useApifyProxy	boolean	Enables Apify Proxy as an optional fallback.
proxyConfiguration	object	Proxy settings used only when proxy use is enabled.

Output

The default Dataset contains both review and product summary records. A review row contains the stable record ID, storefront URL and ID, product name and ID, reviewer, rating, text, date, review source, and change state. The associated product summary contains the current review count and review sources. Each run also writes a SUMMARY record with target counts, review and summary totals, change totals, and completion time.

Use cases

• Monitor competitors for newly published product feedback and changes in review volume.
• Export review text and ratings for sentiment, topic, or complaint analysis.
• Compare review velocity between merchant storefronts and product categories.
• Build a normalized review feed for a marketplace, research database, or dashboard.
• Audit which public Ecwid products have reviews and which review system supplied them.

FAQ

Do I need an Ecwid account or API key?

No. The Actor uses public storefront endpoints and does not use the OAuth-protected Ecwid Admin API.

Can I extract every product review from an Ecwid store?

It checks every publicly visible catalog product and returns public reviews from Ecwid's built-in review feature or Fera. Products with no public reviews are skipped. A store with reviews disabled, no published reviews, or an unsupported review widget can legitimately return an empty Dataset without being an error.

Does it support Fera reviews on an Ecwid storefront?

Yes. Public Fera product-review widgets are detected from storefront configuration and normalized alongside Ecwid-native public reviews.

Does it extract Yotpo, TrustSpot, or every other review widget?

Not in this version. Third-party widgets have different public contracts and may require separate source support. The reviewSource field makes supported coverage explicit rather than guessing from page text.

Can I monitor new reviews?

Yes. Schedule the Actor, keep the same monitor ID, and use changeType or onlyChangesSince to consume the change feed.

Why are some review texts empty?

Ecwid permits a customer to submit a rating without review text. The Actor preserves that public rating and returns an empty text value.

Limitations and responsible use

• Only publicly visible reviews are returned; unpublished, account-only, or private reviews are not accessed.
• Review availability depends on merchant settings, moderation, plan, and public review widget.
• A missing row means the public endpoint did not return it during the run; it does not prove a merchant has never received that review.
• Respect applicable laws, target-site terms, and the privacy expectations of public reviewers when using exported data.

Support

Report a problem or request a review-source integration through the Issues tab on this Actor's page. Include the run ID, storefront URL, and input used so the issue can be reproduced.