Exported field statuses and changes

PropertyDataLabs exports data made available by Zillow pages and the supported Cloud collection workflows. Those sources can change their field names, meaning, availability, or payload structure. As a result, the fields available in an export can also change over time.

The exported-field reference pages show the current availability of each field by product, plan, and export mode. Release notes describe material changes that may affect existing files, templates, or spreadsheet workflows.

What TBR means

TBR means to be removed.

A field marked (TBR) is still retained temporarily for compatibility, but it is scheduled for removal from the export schema. Its value may already be blank when the source no longer provides reliable data. Keeping the field temporarily gives you time to update export templates, spreadsheets, imports, and automations before the column or key is removed.

Do not build a new workflow that depends on a TBR field. For an existing workflow:

1. Identify where the field is used.
2. Remove that dependency or replace it with a documented alternative, when one exists.
3. Check the release notes before updating the Extension or changing a Cloud export workflow.

TBR does not mean that a replacement field is guaranteed. If no reliable equivalent is available, PropertyDataLabs may remove the field without adding another one.

Why a field may change

An exported field may be changed or removed when:

• the source stops providing the value;
• the source changes what a value represents;
• the same label has different meanings across listing types or collection modes;
• a value cannot be populated consistently enough to be useful;
• a clearer or more reliable field replaces it.

PropertyDataLabs avoids guessing missing values when doing so could create misleading data. A blank value is preferable to a value that appears precise but does not represent the advertised field.

Availability can differ by export mode

The browser Extension, Basic Cloud exports, and Advanced Cloud exports do not always collect data from the same page or payload. A field can therefore be unavailable in one mode and available in another. Check the relevant exported-field reference page instead of assuming that a field is shared across every workflow.

Latest pending sale price in Advanced sold exports

(Advanced) Latest pending sale price (USD) is available only for Advanced Cloud sold exports. It is the public price attached to the most recent Pending sale event in Zillow's Advanced price history. It is not the accepted offer, contract price, or final sale price.

The field is blank when price history is unavailable, no dated Pending sale event exists, the latest matching event has no valid positive price, or the event date/time cannot be validated. PropertyDataLabs does not substitute the listing price, current property price, or sold price.

Latest contingent price in Advanced sold exports

(Advanced) Latest contingent price (USD) is available only for Advanced Cloud sold exports. It is the public price attached to the most recent Contingent event in Zillow's Advanced price history. It is populated independently from the pending-sale price and is not the accepted offer, contract price, or final sale price.

The field is blank when price history is unavailable, no dated Contingent event exists, the latest matching event has no valid positive price, or the event date/time cannot be validated. PropertyDataLabs does not substitute the pending-sale, listing, current property, or sold price.

For questions about a field used in an existing workflow, contact support with the listing type, export mode, field name, and a sample property URL. Do not include private account data or signed download links.