BLM import user guide; getting your properties onto your website
The following document explains how the property data on your website is received from your CRM supplier. It explains exactly how an import of your property data works and outlines what you need to do to ensure the information on your website is correct. It also contains important information to ensure your property alert emails link correctly to your website (in the FAQs section).
Contents
1.1 - Overview
1.2 - Setting up an import to your website
1.3 - What information does the website use to display my property listings?
1.4 - FAQs
1.1 Overview
Your CRM provider sends us a file of your property data (in what’s called a BLM format) periodically throughout the day.
Most suppliers send us this data between 1 - 4 times a day. We process the data as soon as it is sent to us, but you should check with your supplier how often they send the file so you know when you can expect your website to be updated.
We can only display the property information on your website which is sent to us within the file. BLM files are a set format file that mirror an older Rightmove format whereby the information and format are pre defined. They are not customisable, so are both slower and less configurable then some API imports.
1.2 Setting up an import to your website
If you’re having a new website built by Webdadi, your Project Manager will be in touch to setup your import. If you already have a Webdadi website and want to setup a new import from your CRM supplier, please contact your Account Manager.
We will contact your CRM provider on your behalf to setup the relevant import of data. However, you should contact them as soon as possible to inform your CRM provider that we will be in touch and authorise the transfer of your data to us.
1.3 What information does the website use to display my property listings?
The following table outlines what information is used on the website, where it is output, and from where in the file it gets that information.
Please note - although the below guide outlines all the information which could be sent within a BLM file which will be output by the website. Some suppliers differ on what information they actually send as not all of these fields are defined as mandatory. This guide represents all the available options that can be included within a BLM file but are not guaranteed to be sent by your supplier.
Website Option | Where does it display on the website | Sent in the file as | Website Option | Options available in the file |
House Number | Doesn't output on the website specifically. This field is imported purely to help us identify the property in our database for troubleshooting | ADDRESS_1 | NA |
|
Address 1 | Used to output the address on the search results & property details pages | ADDRESS_2 | NA |
|
Address 3 | Used to output the address on the search results & property details pages | ADDRESS_4 (not mandatory) | NA |
|
City | Used to output the address on the search results & property details pages | TOWN | NA |
|
Country | Used to output the address on the search results & property details pages | COUNTRY_CODE (not mandatory) | NA |
|
Postcode | Used to output the address on the search results & property details pages. Only the first part of the postcode will show | POSTCODE1 + POSTCODE2 | NA |
|
Branchcode | Determines what branch the property is allocated to. This should match an office setup on the website. This branches details will apear on the property details page (editable in VIA) and is where any arrange a viewing email requests are sent for that property. Properties allocated to a branch not setup on the website will not display | BRANCH_ID | NA |
|
Additional Features |
|
|
|
|
Mark the property as a New Build (1) | Doesn't output specifically, but allows the property to appear in new homes filter searches if required | NEW_HOME_FLAG | NA |
|
Hidden | Field doesn't output on the website specifically, but when ticked it hides the property from appearing on the website | HIDDEN (not mandatory) | NA |
|
Instructed Date | Field doesn't output on the website specifically, but ensures the newest/oldest filter on the website searches functions correctly. It uses this date to define a property's age. If this is blank, it cannot filter properties by those values | CREATE_DATE | NA |
|
Internal Code | Field doesn't output on the website specifically, but ensure the property can always be viewed by using the clients website URL followed by /property/propertyid eg: estateagent.com/property/12345 | AGENT_REF | NA |
|
Long Description | Field outputs as the description on the property details page | DESCRIPTION | NA |
|
Low Price* | Field outputs as the price on the search results and property details page | PRICE | NA |
|
Main Features | Outputs as the Main Features bullet points on the property details page | FEATURE1 FEATURE2 FEATURE3 FEATURE4 (not mandatory) FEATURE5 (not mandatory) FEATURE6 (not mandatory) FEATURE7 (not mandatory) FEATURE8 (not mandatory) FEATURE9 (not mandatory) FEATURE10 (not mandatory) | NA |
|
Number Bathrooms | Outputs as a numeric symbol on the search results and property details page | BATHROOM (not mandatory) | NA |
|
Number Bedrooms | Outputs as a numeric symbol on the search results and property details page | BEDROOMS | NA |
|
Number Receptions | Outputs as a numeric symbol on the search results and property details page | LIVING_ROOMS (not mandatory) | NA |
|
Property Type | Outputs on the search results and property details page (house, flat, apartment etc) | PROPERTY_SUB_ID (not mandatory) | NA |
|
Short Description | Outputs on the list view of the search results page | SUMMARY | NA |
|
Status | Outputs as the status of the property (for sale, under offer etc) | STATUS_ID | NA | For Sale Under Offer Sold STC Let Agreed Please note - as per the portal feeds, the BLM file format does not support sending Sold or Let properties in the feed, so these will not be displayed on the website |
Tenure | Outputs as the tenure of the property underneath the description | TENURE_TYPE_ID |
|
|
Terms | Outputs near the price of the property (offers in excess, guide price etc). In Vebra, customers can add additional drop down options with customised wording for price qualifier wording. The website can’t support limitless custom options the customer may have added to Vebra Alto, but it supports the default options within Vebra Alto. The options which are supported are to the right. The customer must use the default options in order for it to display correctly on the website. | PRICE_QUALIFIER | Guide | 2 |
Fixed Price | 3 | |||
Offers in the region of | 5 | |||
Offers in excess | 4 | |||
Offers over | 10 | |||
Null | Null | |||
|
| |||
Vacant From | Doesn't output on the website | LET_DATE_AVAILABLE | NA |
|
Video Tour (multi or single) | Outputs as a video symbol on the search results and property details page. When clicked it displays the video(s) | MEDIA_VIRTUAL_TOUR_00 (not mandatory) | NA |
|
Webdadi Sub Type | Field doesn't output on the website specifically, but essentially markes the property as a sales or lettings property so it appears in the relevant search | TRANS_TYPE_ID | NA |
|
1.4 FAQs
How do I make changes to the property listings on my website?
Simply update your property information within your CRM software. The next time your supplier then sends us a file of your data, this change should be in the file so we can update your website
I’ve made a change to a property listing but not displaying on my website even though it has updated on the property portals?
Firstly, it’s important to note updates to the portals are sent in real time. It means the portals update almost instantly once you update a property. However, your CRM supplier sends a file of your property data periodically throughout the day so your website will not update as quickly. You should check with your supplier how often they send this file (usually 1-4 times a day) and when/what time it is sent, so you then know when you can expect the website to update
Ensure you have added/edited the information in the correct field within your CRM. Section 1.3 above outlines what fields are sent to us in the file. You can check with our CRM supplier which field in your software corresponds to the file. If you’re adding information to other fields not listed above, they won’t display on the website.