Does DDF include sold data?

No. The DDF carries active listings only — the slice of the market whose brokerages opted in to national sharing, delivered at portal-grade field depth. Sold prices, sale history, and off-market statuses never enter the pool under any feed type, as of mid-2026. On a Canadian agent website, sold data arrives through exactly one legitimate route: a VOW feed licensed from your board and served behind a registration gate. If a sold-data site is the goal, the DDF is not a partial answer; it is the wrong feed class entirely.

Why the pool stops at active listings

The DDF is a syndication service: it moves public-display listing content outward to many websites with light paperwork. Sold data is the opposite kind of asset — member-licensed, board-governed, and released to consumers only under conditions boards can enforce: an identified, signed-in visitor who has accepted terms of use. An open national pool cannot carry content whose display rules require a closed door. The absence is structural, not a missing feature awaiting an update — which is why no DDF feed type, filter, or plugin setting unlocks it.

The route that actually works: a VOW

A Virtual Office Website is the feed class boards created for exactly this content. The trade is defined by the gate: visitors register and accept terms, and in exchange the site can show them sold prices and history under the board’s rules — password-expiry requirements, audit obligations, and display conditions included. Those rules are real and they vary by board: TRREB’s regime runs 90-day visitor password expiry while the Greater Vancouver tri-board rules require 30, which is one small illustration of why a VOW is a compliance build and not a plugin. The full comparison of the two lanes is on IDX vs VOW, the build itself on VOW website, and the Ontario rulebook on Ontario sold data rules. Worth noting for strategy rather than compliance: the gate earns its keep. Sold prices are the data buyers and sellers want most and cannot browse on an open page, so the sign-in wall in front of them converts anonymous traffic into named, consenting contacts at a rate no open-page call to action approaches. Agents tend to arrive at the VOW question thinking about compliance and leave thinking about lead capture.

Red flags when a vendor says otherwise

Any pitch that promises sold prices “through DDF,” solds on an open page with no sign-in, or historical data with no board agreement in the chain is selling one of two things: a misunderstanding of the feed, or a compliance exposure that would live under your own domain name. The same caution applies to “sold data coming soon” roadmap promises from DDF-only vendors — the limitation is contractual and structural, so no software release on their side changes what the pool contains. The polite version of the question to ask is: which board VOW agreement does this run under, and where is the registration gate? Vendors operating the real thing answer instantly, because the agreement and the gate are the product. Vendors who change the subject have answered too.

The decision, cleanly

Use the DDF for what it is — the light-paperwork national pool of active listings — and decide separately whether your market position needs solds. If it does, that is a board VOW agreement and a gated build, full stop. The two feeds are not competing answers to one question; they are different products for different jobs, and knowing where the line sits is what keeps a website both useful and defensible.