Where are people actually looking?
Demand is not published for individual properties. This rung stops aggregating places and draws the homes themselves, and every reading on this map is pooled across at least 5 people so that no one person's activity can be read out of it. A single property has no pool to hide in — "someone is watching this address" is the exact sentence the floor exists to prevent. Zoom out to a city view to read demand by locality.
Demand is 5 behavioural signals, weighted by how much intent each one shows, counted in distinct people and pooled so no individual can be read out of it.
Demand is not published at this zoom.
Demand is not published for individual properties. This rung stops aggregating places and draws the homes themselves, and every reading on this map is pooled across at least 5 people so that no one person's activity can be read out of it. A single property has no pool to hide in — "someone is watching this address" is the exact sentence the floor exists to prevent. Zoom out to a city view to read demand by locality.
1 signal not counted — and why
- Video engagement
- This platform owns none of its video. All 13 clips play from the agents' own YouTube accounts in an embedded player, and an embed reports nothing back to the embedding site — watch time, completion and drop-off are measured by YouTube, for the channel owner, and `media.meta` carries no statistics on any of the 13 rows. The two ways to fill this are both real work with a real cost: pull public view counts through the YouTube Data API on the existing re-sync sweep (cheap, but it counts views from YouTube's own surfaces — people who never came near this site — so it is not Realty.tube behaviour and must never be labelled as such), or host video ourselves and measure playback directly (accurate, and a different platform). Until one of those is chosen, a video-engagement number here would be a guess with a percent sign.