TripAdvisor Review Export Sync Audit

Deduplicate review exports and identify new, replayed and changed reviews against your previous state.

Quick start

Paste this input into the Apify JSON input editor and start a run. The example uses synthetic records for a reproducible first audit.

{
  "scope": "demo-hotel",
  "source": {
    "complete": true,
    "items": [
      {
        "reviewId": "demo-1",
        "text": "Updated review text",
        "rating": 4,
        "publishedDate": "2026-09-10"
      },
      {
        "reviewId": "demo-1",
        "text": "Updated review text",
        "rating": 4,
        "publishedDate": "2026-09-10"
      },
      {
        "reviewId": "demo-2",
        "text": "A new review",
        "rating": 5,
        "publishedDate": "2026-09-11"
      }
    ]
  },
  "state": {
    "version": 1,
    "scope": "demo-hotel",
    "maxObservedReviewDate": "2026-09-10T00:00:00.000Z",
    "reviews": [
      {
        "id": "demo-1",
        "data": {
          "text": "Original review text",
          "title": null,
          "rating": 4
        },
        "publishedAt": "2026-09-10T00:00:00.000Z"
      }
    ]
  }
}

Results

Dataset rows use state new, replay, changed or unknown. ACCEPTED contains eligible new and changed reviews. Reuse STATE within the same hotel or attraction scope.

A platform run marked SUCCEEDED means execution finished. Always inspect the application status and unresolved rows before using the result.

Export sources

Use inline items with an explicit complete declaration, or a completed Apify runId. A datasetId alone does not prove collection is finished. Remote reads check run status and dataset stability. Maximum 10,000 records and 32 MiB per source. Local file paths are CLI-only.

The Actor processes data you supply; it does not collect new reviews, jobs or Maps listings. Remote datasets and previous key-value stores require access by the running account.

Repeated runs

Pass stateStoreId and optional stateRecordKey (default STATE) to load a previous run's state, or supply state inline. Select a successfully completed prior run and keep state separate per customer and scope. The current run writes its own store; no shared historical pointer is overwritten.

Limitations

Requires stable review IDs and text. Conflicting duplicates and incomplete exports are inconclusive. Missing reviews are not treated as deleted. The maximum observed date is not proof of a complete pagination cursor.

Automation and data

Use Apify schedules or its API to run this Actor. Scheduling and external notifications are not enabled automatically. Results stay in the run dataset and key-value store; storage retention follows your Apify settings. Do not include passwords or session cookies in inputs.

Support

Report an issue with the Actor version, run ID, expected result and a small redacted input. Avoid including private customer data or credentials. Owlects is independent of the third-party platforms named here.

Pricing and run budget

Launch Actor fee: USD 0.05 per conclusive audit. Apify platform usage is charged separately. Unresolved or partial audits and blocked results do not generate an Actor fee. See the pricing panel for the active rates.

The maximum cost must cover all requested result fees before work starts. Use smaller batches to reduce the required budget. For remote Funda exports, the budget check uses the 10,000-record source limit.