2GIS Reviews Monitor & Alerts

What is 2GIS Reviews Monitor & Alerts?

2GIS Reviews Monitor & Alerts is a stateful review monitoring tool for businesses with one or more 2GIS branches. Instead of exporting the same reviews on every run, it remembers what was already seen and returns only reputation changes that may require attention.

Use it to catch a new 1–3 star review, see when an owner reply is added, detect negative reviews that remain unanswered past your SLA, and track branch rating or review-count changes. The first run can be a quiet baseline, so existing old reviews do not flood your dataset as fresh alerts.

This Actor uses lightweight HTTP requests, does not launch a browser, and does not require a 2GIS login. It works well with Apify Schedules, API calls, Make/Zapier-style workflows, and webhooks.

What can it monitor?

The Actor can emit these event types:

• NEW_NEGATIVE_REVIEW - a newly observed review at or below your configured rating threshold.
• NEW_REVIEW - any newly observed review when emitAllNewReviews is enabled.
• OWNER_REPLY_ADDED - the business added an official reply to a review seen earlier.
• UNANSWERED_NEGATIVE - a negative review stayed without an owner reply longer than your configured SLA.
• REVIEW_UPDATED - review text or rating changed.
• RATING_CHANGED - the branch's aggregate 2GIS rating changed.
• REVIEW_COUNT_CHANGED - the branch's aggregate review count changed.

Unchanged reviews are not repeatedly pushed to the dataset.

How to use the 2GIS review monitor

1. Add one or more 2GIS branch review URLs or numeric branch IDs to 2GIS place URLs or firm IDs.
2. Keep Quiet first run enabled for normal monitoring. The first successful check stores the current state without generating old-review alerts.
3. Choose your negative-review threshold and the number of hours a negative review may remain unanswered.
4. Run the Actor once to create the baseline.
5. Create an Apify Schedule, for example every hour or once per day. Later runs reuse the saved state and return only new changes.
6. Optionally provide a webhook URL. When a run produces alerts, the Actor sends one compact JSON payload containing all events from that run.

Use a different Monitoring campaign name (stateKey) when you want independent monitoring histories for separate clients, brands, or workflows.

Example input

{
  "places": [
    "https://2gis.ru/moscow/firm/70000001044357973/tab/reviews",
    "https://2gis.kz/almaty/firm/70000001076772761/tab/reviews"
  ],
  "placeNames": ["Moscow branch", "Almaty branch"],
  "stateKey": "my-brand",
  "quietBaseline": true,
  "recentReviewsPerPlace": 50,
  "negativeMaxRating": 3,
  "unansweredAfterHours": 24,
  "emitAllNewReviews": false,
  "emitAggregateChanges": true
}

Example alert

{
  "eventType": "NEW_NEGATIVE_REVIEW",
  "placeId": "70000001044357973",
  "placeName": "Moscow branch",
  "placeUrl": "https://2gis.ru/moscow/firm/70000001044357973/tab/reviews",
  "rating": 2,
  "text": "The order took too long.",
  "authorName": "Customer",
  "hasOwnerReply": false,
  "observedAt": "2026-09-15T08:03:22.267+00:00"
}

The default dataset contains alert events only. A compact run summary is also written to the OUTPUT record in the run's default key-value store.

Pricing

This Actor uses pay per event pricing. The primary billable event is a successful 2GIS branch check.

• Price: $0.005 per successfully checked branch.
• Failed branches are not charged by the Actor's custom branch-check event.
• A run with 10 branches costs about $0.05 in Actor event charges.
• Checking 10 branches once per day for 30 days is about $1.50 in Actor event charges.

The Actor is intentionally priced per branch check rather than per review because monitoring usually needs to inspect recent reviews even when nothing changed. This makes recurring costs predictable.

Tips for reliable monitoring

Run often enough that recentReviewsPerPlace covers the number of reviews a branch can receive between runs. For a normal local business, 50 recent reviews per branch is a practical default. High-volume locations may need a higher value or a more frequent schedule.

Keep quietBaseline=true unless you deliberately want all currently visible reviews to be treated as new on the first run. Use resetState=true only when you intentionally want to discard the saved campaign state and rebuild the baseline.

API and integrations

Like every Apify Actor, this monitor can be called from the Apify API, CLI, Python, JavaScript, OpenAPI integrations, and scheduled workflows. Dataset alerts can be consumed programmatically, while the optional webhook is useful when another service should react immediately to new incidents.

FAQ

Does this export every 2GIS review?

No. This Actor is optimized for recurring reputation monitoring. If you need a bulk historical review export, a dedicated raw 2GIS reviews scraper is a better fit.

Does it need a browser, proxy, or 2GIS account?

No browser or 2GIS login is required for normal operation. The Actor uses public web review data over HTTP.

Is this an official 2GIS product?

No. This Actor is an independent monitoring tool and is not affiliated with or endorsed by 2GIS. You are responsible for using collected public data in accordance with applicable laws and platform terms.

Can I monitor several brands or clients independently?

Yes. Give each monitoring campaign a different stateKey, or use separate saved Actor tasks.

Quiet-run dataset heartbeat

If a run produces no reputation alerts, the Actor writes one RUN_SUMMARY row to the default dataset. This keeps scheduled runs observable and satisfies Apify Store health checks without turning old reviews into fake alerts. When real alerts exist, the dataset contains the alert rows only.