Results, insights, and exports
Understand the controls shared by Cloud result pages and background exports.
Result status
Cloud job histories distinguish successful, failed, and in-progress runs. A completed result records its completion time, processed counts, failures, credits used, and an error message when applicable. The counts describe that run only; they do not represent every run of the job.
Tables and filters
Result tables commonly provide:
- address search;
- City, ZIP, State, property-status, or job-status filters;
- sortable headings;
- visible-column controls;
- row selection;
- rows-per-page and page navigation.
Some address filters apply to the current loaded page. If you cannot find a record, clear filters and check the next result page.
Property records
Open a street address to inspect the retained record. Fields are grouped by purpose rather than by their original source order. Nested values, such as property-tax history and image URLs, appear as readable lists. Use the copy control beside a value to copy it.
A property page reports how many fields were populated and when the record was captured. “Complete data retained” means the complete stored record is being shown; it does not mean every possible Zillow field had a value.
Result insights
Insights are deterministic summaries built from the result's retained properties. Depending on the workflow they can include price ranges, locations, property types, bedrooms, listing statuses, changes from a previous monitoring run, and data-coverage percentages.
- Generate insights creates them for a result that does not have them yet.
- View insights opens an existing analysis without fetching properties again.
Insights describe the result at capture time and are not a live market appraisal.
Export options
Select rows for a partial export or use Export all properties for the complete result. Available result-download formats are:
| Format | Extension | Best suited to |
|---|---|---|
| CSV | .csv | Broad compatibility with spreadsheet and database tools |
| Excel | .xlsx | Opening and reviewing results directly in spreadsheet software |
| Parquet | .parquet | Large datasets, analytics tools, and typed columnar storage |
| JSON | .json | APIs, scripts, automations, and structured data processing |
These formats are available for Cloud Importer, Aggregator, Monitoring, and Fetcher result exports. Field choices still depend on the workflow, export depth, plan, and templates. Google Sheets and Cloud Importer Email are delivery destinations rather than file formats. Email delivery uses CSV, while the retained result can still be exported manually in any format supported by its result page.
An export action creates a file from retained result data; it does not start a new property-scraping run or consume credits for fetching the properties again.
Background exports
Monitoring and Fetcher provide a Background exports page for files that need time to prepare. It shows preparation status, start and completion times, expiration, download link, errors, and a link back to the source result.
Completed download links remain available for 24 hours. Download the file before Link expired appears. Expiration removes access to that generated file, not the underlying job result.