Google Maps Review Complaint Drift Analyzer
Pricing
from $13.30 / 1,000 results
Google Maps Review Complaint Drift Analyzer
Compare supplied Google Maps review datasets to identify new negative feedback, unresolved low-rating clusters and changes in local business review coverage. No invented sentiment or ratings; analyze only supplied public reviews.
Pricing
from $13.30 / 1,000 results
Rating
0.0
(0)
Developer
Rafael Barreto Haddad
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
10 days ago
Last modified
Categories
Features
Share
Compare supplied Google Maps review datasets to identify new negative feedback, unresolved low-rating clusters and changes in local business review coverage. No invented sentiment or ratings; analyze only supplied public reviews.
Why use this Actor
Local businesses and reputation teams need to prioritize observed new complaints by place and topic from collected review datasets.
Key features
- Buyer-native inputs aligned to google maps review analysis.
- Predictable structured output in the default Apify Dataset.
- Pay Per Event pricing tied to measurable result rows or reports.
- Optional MCP connector delivery for downstream automation and AI agents.
Quick start
Start with this working example and replace the target values with your own:
{"currentItems": [{"reviewId": "RV101","business": "Cafe Alpha","topic": "service","category": "negative-unanswered","value": 1,"rating": 1,"date": "2026-10-12"},{"reviewId": "RV102","business": "Cafe Alpha","topic": "waiting time","category": "negative-unanswered","value": 1,"rating": 2,"date": "2026-10-12"},{"reviewId": "RV202","business": "Bistro Beta","topic": "food","category": "positive-answered","value": 1,"rating": 5,"date": "2026-10-12"}],"previousItems": [{"reviewId": "RV100","business": "Cafe Alpha","topic": "service","category": "negative-unanswered","value": 1,"rating": 1,"date": "2026-10-05"},{"reviewId": "RV201","business": "Bistro Beta","topic": "food","category": "positive-answered","value": 1,"rating": 5,"date": "2026-10-05"}],"maxItems": 20000}
The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.
Input
currentItems— Current records: Current source or normalized rows to analyze.currentDatasetId— Current Apify Dataset ID: Optional Apify Dataset ID used when currentItems is not supplied.previousDatasetId— Previous Apify Dataset ID: Optional previous Apify Dataset ID used instead of previousItems.maxItems— Maximum records: Maximum records loaded from a Dataset input.
All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.
Output
The Dataset exposes predictable machine-readable output. Representative fields include results.
Pricing
This Actor uses Pay Per Event. The current factory base price is $0.019000 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.
Use cases
- Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
- Use the Actor from API or schedules for recurring collection, comparison or monitoring.
- Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
- Compare repeat runs when the product supports snapshots or previous-run inputs.
Automation and AI
Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.
Limitations
- Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
- Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
- Analytical outputs depend on the quality and coverage of the supplied or collected source data.
- Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.
Detailed documentation
What the buyer gets
Google Maps review datasets, negative feedback and unanswered issues. Output is a structured Apify Dataset; unavailable source fields are not invented.
First-run example
This is a small example. Replace supplied sample records with authorized data or replace example IDs/searches with real targets.
{"currentItems": [{"reviewId": "RV101","business": "Cafe Alpha","topic": "service","category": "negative-unanswered","value": 1,"rating": 1,"date": "2026-10-12"},{"reviewId": "RV102","business": "Cafe Alpha","topic": "waiting time","category": "negative-unanswered","value": 1,"rating": 2,"date": "2026-10-12"}],"previousItems": [{"reviewId": "RV100","business": "Cafe Alpha","topic": "service","category": "negative-unanswered","value": 1,"rating": 1,"date": "2026-10-05"},{"reviewId": "RV201","business": "Bistro Beta","topic": "food","category": "positive-answered","value": 1,"rating": 5,"date": "2026-10-05"}],"maxItems": 5}
Verified test and limitations
Run SG9KlRFrSKSHH11tR (status SUCCEEDED, sample dataset rows 1). The run processed demonstration or supplied records; it does not prove independent live collection or paying-customer demand.
Input mode: customer-supplied/authorized data only.
Compare supplied Google Maps review datasets to identify new negative feedback, unresolved low-rating clusters and changes in local business review coverage. No invented sentiment or ratings; analyze only supplied public reviews.
Why use this Actor
Local businesses and reputation teams need to prioritize observed new complaints by place and topic from collected review datasets. This Actor sits above raw extraction: supply a current dataset, optionally add a previous snapshot, and receive an aggregated report built for recurring monitoring and AI-agent workflows.
Key features
-
Deterministic current-versus-previous data snapshot comparison.
-
Entity-level change and concentration scoring.
-
Explainable structured action signals for business research.
-
Accepts records or Dataset IDs from compatible upstream Apify scrapers.
-
Reads inline JSON rows or Apify Dataset IDs with limited READ permission.
-
Writes one auditable report to the default Dataset and
INTELLIGENCE_REPORT.
Example
Use the prefilled example or replace currentItems with rows from an upstream Actor. On recurring runs, provide the prior period in previousItems or previousDatasetId. The Actor normalizes common aliases, compares snapshots, ranks the strongest entity changes and emits agentAction.
Use cases
- Recurring performance and risk audits.
- Competitive monitoring and evidence-based alerts.
- Data enrichment and BI pipelines.
- Agent-driven business research.
Pricing
One primary pay-per-event outcome: one decision-ready intelligence report. Base price USD 0.019 before Apify tier discounts. The 256 MB data-first architecture is designed for strong unit economics.
Limitations
- Analyzes supplied public or appropriately licensed data and does not bypass restricted sources.
- Scores are decision-support signals, not predictions or guarantees.
- Keep stable identifiers across snapshots for best change detection.
- Zero-direct-competition status is rechecked before publication because the Store changes continuously.
Workflow
upstream dataset -> current snapshot -> optional previous snapshot -> normalization -> entity aggregation -> change scoring -> ranked signals -> agentAction.
Buyer-first quick start (November 2026)
This workflow is designed for one practical buyer question, with a small, reproducible first run and auditable Dataset output.
Example input
{"currentItems": [{"reviewId": "RV101","business": "Cafe Alpha","topic": "service","category": "negative-unanswered","value": 1,"rating": 1,"date": "2026-10-12"},{"reviewId": "RV102","business": "Cafe Alpha","topic": "waiting time","category": "negative-unanswered","value": 1,"rating": 2,"date": "2026-10-12"},{"reviewId": "RV202","business": "Bistro Beta","topic": "food","category": "positive-answered","value": 1,"rating": 5,"date": "2026-10-12"}],"previousItems": [{"reviewId": "RV100","business": "Cafe Alpha","topic": "service","category": "negative-unanswered","value": 1,"rating": 1,"date": "2026-10-05"},{"reviewId": "RV201","business": "Bistro Beta","topic": "food","category": "positive-answered","value": 1,"rating": 5,"date": "2026-10-05"}],"maxItems": 20000}
Source and limitations
This actor analyzes records and/or Apify Datasets supplied by the customer. It does not independently collect Google Maps, job, finance, social or App Store data. Any example rows in a form or README are DEMO INPUT, not observed customers, live listings or real market signals. For production, replace sample records with your authorized Dataset ID or real records.
Repeatable workflow
Use the default test to understand the output, verify record identifiers and field coverage, then schedule a Task with a bounded input. Compare real earlier snapshots only when available. Check the current Apify Store Pay Per Event rate and set Apify run charge limits for recurring use. Source evidence does not establish paying customers, successful outbound sales, or revenue.