Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
AnchorTopTopReal Estate algorithm is developed to identify specific demands of the customer in real estate category.
Panel
titleFollowing steps are covered
Table of Contents

Introduction

Real Estate algorithm is developed to identify specific demands of the customer in real estate category.

The algorithm considers:

  1. Particular characteristics of the property (size, floor)
  2. Transaction type (sale, lease)
  3. 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). 

Info
titleIMPORTANT

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

Additional niches properties of products allow studying user preferences and calculating recommendations more accurately. This section describes allowing filling the product feed with niche features of real estate.



Case Sensitivity

Warning

All parameter names are case-sensitive and should follow the spelling used in this documentation.




Realty

The "realty" element must be inside the "offer" element.


Code Block
languagexml
themeMidnight
<offer ...>
    ...
    <realty>
        ...
    </realty>
</offer>



Price

The "price" element must be inside the "offer" element and have the value of the area cost per 1m².

Code Block
languagexml
themeMidnight
<offer ...>
    ...
    <price>10.52</price>
</offer>


Space

The "space" element must be inside the "realty" element and includes a minimum, maximum and final value of the object's area:

ElementMetric UnitsDescription
minSquare MeterMinimum size
maxSquare MeterMaximum size
finalSquare MeterExact size

Infowarning
titleNOTE

Metric units are always square metermeters, even if the object is a 30 hectares-wide ground area.

Consider the following example of use:


 ...
Code Block
languagexml
titlethemeXML example
Midnight
<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:

ParameterDescription<current>

Floor 

The "floor" element must be inside the "realty" element and includes the current floor of the object and the maximum floors:

ElementDescription
currentObject floor
<total>
totalTotal number of floors in the building

Consider the following example of use:


 ...
Code Block
languagexml
titlethemeXML example
Midnight
<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

Type 

The "action" element must be inside the "realty" element and can have one of the following values:

ValueDescription
rentFor lease
sale

For sale


Infowarning

If the same realty object is both on sale and lease leases simultaneously, XML-file  the product feed should contain two separate objects, each having its own unique ID , and each specifying in the <offer> section the in a separate "offer" element with the required type of action (sale, rent).

Consider the following example of use:


 ...
Code Block
languagexml
titlethemeXML example
Midnight
<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

Property Type

Anchor
type
type
The "type" element must be inside the "realty" element and can have one of the following values:

ValueDescription
flatFlat
office

Office

warehouseWarehouse
landGround area

Consider the following example of use:


 ...
Code Block
languagexml
titlethemeXML example
Midnight
<offer ...>
    ...
	<realty>
	    <type>flat</type>
	</realty>
</offer>
...

Return to the top of the page Return to the main page

Panel
titleTable of Contents
Page TreerootNiche Solutions



Column

Page Navigation

Table of Contents
maxLevel2
indent0px
stylenone




Related Pages

Filter by label (Content by label)
showLabelsfalse
showSpacefalse
sorttitle
cqllabel = "products"