How often should I re-run a list?

It depends on volatility. Hospitality and retail move fast enough to justify monthly refreshes; professional services drift far more slowly.

Is the timestamp per row or per export?

Per row. A long-running job that spans hours records when each row was actually collected.

Provenance field

Scraped at

The timestamp the row was extracted, which is what turns a static list into something you can measure change against.

Column name: scraped_at
Group: Provenance
Availability: Every plan, free included

What this column contains

An ISO 8601 timestamp recording when this row was collected.

Where the value comes from

Stamped by the extractor at collection time, per row rather than per export.

Example value

2026-08-23T18:42:11.000Z

What people use it for

01Decide when a list is stale enough to re-run.
02Diff two runs to see which businesses gained reviews, changed hours or disappeared.
03Resolve relative review ages against a real date.
04Prove data age to a client or an auditor who asks.

What it will not tell you

Local business data ages continuously — hours, phone numbers and closures change weekly. A row is a snapshot, and this column is the honest label on it.

Questions about this field

How often should I re-run a list?: It depends on volatility. Hospitality and retail move fast enough to justify monthly refreshes; professional services drift far more slowly.
Is the timestamp per row or per export?: Per row. A long-running job that spans hours records when each row was actually collected.

This is one of 41 columns on every row, on every plan. See the full field reference or check pricing.