Real Estate algorithm is developed to identify specific demands of the customer in real estate category.
Introduction
Real Estate algorithm is developed to identify specific demands of the customer in real estate category.
The algorithm considers:
- Particular characteristics of the property (size, floor)
- Transaction type (sale, lease)
- Type of the property (residential, commercial)
Algorithm then specifies product recommendations based on this data.
Add Additional Parameters to Your XML-file
For the algorithm to work properly every product in your XML Product Feed should have additional properties:
- Object size
- Object type
- transaction type
This data should be included into the XML-file in the form of specific product parameters and send to PersonaClick.
Section <price>
Object price specified in this parameter is the price of 1 square meter of the object (for more information about the basic parameter <price>, see XML Product Feed)
Section <location>
Linking to a specific geographic location is done inside the <locations> section (for more information about the basic parameter <location>, see XML Product Feed).
IMPORTANT
Do not try to set the price of the real property in the <location> section!
Section <realty>
A distinctive real property feature is the presence of the <realty> subsection inside the <offer> section.
Add the following parameters to each product to your XML-File.
Object Size
Optional parameter <space>. Placed within the <offer> subsection, inside the <realty> section.
Consider the following table of possible values:
| Value | Metric Units | Description |
|---|---|---|
| min | Square Meter | Minimum size |
| max | Square Meter | Maximum size |
| final | Square Meter | Exact size |
NOTE
Metric units are always square meter, even if the object is a 30 hectares-wide ground area.
Consider the following example of use:
...
<offer ...>
...
<realty>
<space>
<!-- Here can be set minimum and maximum object group size or precise size of a particular object -->
<min>30</min>
<max>100</max>
<final>37</final>
</space>
</realty>
</offer>
...
Object Floor
Optional parameter <floor>. Placed within the <offer> subsection, inside the <realty> section.
Consider the following table of available subparameters:
| Parameter | Description |
|---|---|
| <current> | Object floor |
| <total> | Total number of floors in the building |
Consider the following example of use:
...
<offer ...>
...
<realty>
<floor>
<!-- Object floor -->
<current>3</current>
<!-- Total number of floor in the building -->
<total>12</total>
</floor>
</realty>
</offer>
...
Transaction type
Mandatory parameter <action>. Placed within the <offer> subsection, inside the <realty> section.
Consider the following table of possible values:
| Value | Description |
|---|---|
| rent | For lease |
| sale | For sale |
If the same realty object is both on sale and lease simultaneously, XML-file should contain two separate objects, each having its own unique ID, and each specifying in the <offer> section the required type of action (sale, rent).
Consider the following example of use:
...
<offer ...>
...
<realty>
...
<action>sale</action>
</realty>
</offer>
...
Type of Property
Mandatory parameter <type>. Placed within the <offer> subsection, inside the <realty> section.
Consider the following table of possible values:
| Value | Description |
|---|---|
| flat | Flat |
| office | Office |
| warehouse | Warehouse |
| land | Ground area |
Consider the following example of use:
...
<offer ...>
...
<realty>
<type>flat</type>
</realty>
</offer>
...