High level on how the Gmaven broker vacancies feed works
As the saying goes, data is the oil that commercial real estate runs on.
And vacancies is data-intense, with lots of admin.
The good news, public domain vacancies are captured by Gmaven, in two ways, either:
- Manually from the vacancy schedules (3 day turnaround), or
- If the property fund is on Gmaven, moved automatically (within minutes) via a data switch.
This information is fed into brokers – subject to that brokerage’s custom settings.
Brokerages are able to choose exactly what stock they want by choosing on one or more of the following filters
- Unit property categories,
- Geographical net,
- Unit size
More detail
Common questions answered
Can I enter my own, private stock?
Yes. And there is no charge for this.
Is my stock private?
Yes – it is not shared with or accessible to any competitor.
Can I enter my own version of information sent to me by you?
Yes, with the obvious exclusions.
Can I see what stock is new / updated?
Yes
Some questions for brokers after go live
Will my data be up to date?
Yes. The vacancies data feed means your data is updated in your system by Gmaven. This happens from one day up to a maximum of 3 days from the vacancy schedules coming out.
How does Gmaven decide what data to give me?
According to your custom filter. Your management team created a filter by defining what data you, and where you want that data from. The where: they drew a polygon – doing this, using Google Earth, . This polygon created a “net”. The Gmaven data feed gives you all properties and property-related data inside of that net. (I.e. you get properties, vacant units, the businesses who own or manage those vacant properties, and the contacts you need to deal with to do leasing deals).
This ensures that you the data that is right for your business (and avoids you paying for or getting data you don’t want).
Will all the stock/listings fed in go automatically to my website?
No. Your stock will arrive in your system as privacy status blank. (You can use our unit filters to identify this stock). You can then select, on the unit level, if you want your stock to go public, or not.
What about my data being over-written
Please see more the section “Okay, but how does it all work – in detail?” below.
Your private data (images, description, even property attributes and names) will not be overwritten. However, for fields where the property fund or manager is the source of truth, those data will be updated when the data is updated by the property fund / manager.
What happens if I delete (custom) data I added in a specific field?
The property fund or manager’s data will now display. If there is no property fund data fed to this specific field, no data will display, as per normal.
My old data
Gmaven can import your old data into the system, with green ticks.
Gmaven can also do a cleaning (renovation/refurb/overhaul) exercise where
- Your existing data is
- enriched (fields like co-ordinates, correct suburbs, unique identifiers etc. were added, and mastering was completed),
- deduplicated and
- removed (if required), and
- new data (info you don’t have – e.g. missing properties and vacancies coming through the broker vacancies feed) is added.
More questions on the broker vacancies feed
What does green ticks mean?
Green ticks indicate your level of data quality (whether your data is mastered or not). Please read here for an explanation
Will data be lost in any cleaning exercise?
No. The good news is no data will be deleted forever. All data is backed up and can be reinstated within a period of 6 months.
Where you cannot see a specific data asset now, your management and Gmaven decided to temporarily archive very specific data based on specific rules. Why? That specific data asset was identified as either being out of date, or a duplicate. If the latter, look for the deduplicated version of your data – it should be a merge of both. But remember, merging data duplicates is hard – it’s very tough to guess which data version should win.
Will some fields in my old data assets change?
As part of the data overhaul project, our job is to fix and clean whatever data we can. This means correcting city/town names, property names to what is on the vacancy schedule or other source of truth, updating co-ordinates etc.
Okay, but how does it all work – in detail?
Short answer: fairly logically for CRE and a broker vacancies feed.
Think about it like this. All data fields on the system belongs to only one of two “families”.
Family 1: property fund/manager data “wins”
These are the data fields that the property funds “own”. Have you heard of the “one version of data truth” golden rule? Well, with these fields, property funds/managers are the source of truth. Therefore, to avoid data chaos, their version wins. Examples of family 1 property fund-owned data: unit GLA or asking rental, property’s street address, suburb, asking basement parking bay rental etc.
Family 2: data fields where you “win”
This is your custom data. Your version of data is never overwritten. You can, if desired, “build on” what is provided by the property fund/manager. Examples here: property name, to let marketing descriptions, property attributes, your entered parking ratio etc.
It’s as simple as that.
For more info, please see this link here.