Propertybase CRM now integrates with the property portals Dubizzle, Bayut and Property Finder for all our interested clients in the Middle East! No more need to track your listings in multiple places, all can be done from within Propertybase and simply published to the portals that you are registered with.
If you are interested in adding this integration please contact your Account Executive for more details.
The Middle East Portal package will need to be installed and setup by our support team. In order for support team to install the package they will need access to the ORG and a description of which of the portals you are registered with. Once setup is complete you will find some additional new fields (prefixed with pba_uaefields__) and an additional listing page layout. Please use that page layout as your blueprint to adjust your rent and/or sale layouts accordingly. You must use the fields as listed below in order to successfully publish to these portals.
This article has all instructions needed to setup the pickup feed URLs and publishing listings to those feeds. Once you are ready (bottom of article), you will share the pickup URL(s) with the portal(s) you want to publish listings on. They will check them and if all is ok (no data missing), they will start to pickup your feed regularly.
Note: the following depicts Dubizzle and Property Finder, but following these instructions will also allow usage for Bayut.
Part 1 - Preparing Layout/Fields to use
In order to make sure that a listing can be successfully published to the portal, be aware that the following fields are required:
- Title (marketing title)
- Price (same field for rentals and sales listings)
- Price Unit (for rentals)
- For Property Finder 0 bedrooms is mapped to *Studio*
- For Dubizzle *Studio* can be selected as a Property Type and is not related to the number of bedrooms -> Please select "Propertytype" = "Studio" and enter "0" for bedrooms.
- Bathrooms (0-9)
- Property Type (predefined values)
- Property Sub Type (predefined values)
- Listing Type (Rent / Sale)
- Broker's Listing ID - ID used to identify the listing on the portal side
- RERA Permit Number (Trakheesi) in UAE
The following are optional fields that have been added that can be mapped to the portal fields:
- Title (Arabic)
- Available From
- Available To
- Measurement - Metric or Non-Metric
- Description (Arabic)
- Private Amenities (predefined values)
- Commercial Amenities (predefined values)
- Total Closing Fee [Dubizzle Only]
- Annual Community Fee [Dubizzle Only]
The following tables provide an in depth overview of the fields used by Propertybase to map to both Dubizzle and Property Finder.
|PB Dubizzle Field Mappings||Dubizzle Fields|
|pba_uaefields__price_unit__c||price (based on rent)|
|PB Property Finder Field Mappings||Property Finder|
|pba__listing_agent_firstname__c + pba__listing_agent_lastname__c||name|
*Note: please create a custom text field, if you want to show info by creating the exact value in the field's API name as above, so listing_agent_info (don't worry about the __c, the system adds it to it).
The Listing Agent details will automatically generate a Listing Agent ID in the feed needed for the portal.
The rule for that is:
3 first characters of pba__listing_agent_firstname__c
3 first characters of pba__listing_agent_lastname__c
3 first characters of pba__listing_agent_mobil_phone__c OR pba__listing_agent_phone__c
Add Address Lookup Components
In addition to this you will need to add 2 components to your page layout, one for Dubizzle, the other for Property Finder: The Dubizzle and the Property Finder Location Chooser.
These are used to ensure that the correct address values are set that are acceptable by the portals. They are mandatory. There are two different components due to the fact that each portal treats their locations a bit differently. Both populate defined, specific fields automatically. The page will refresh every time you click on "Update", so add them one-by-one:
On the page layout it can look e.g. like this (if you removed the chooser and need it back but don't know how, please reach out to firstname.lastname@example.org):
Dubizzle Selector (Location Chooser)
When using the Dubizzle Selector the Locationtext field is required, always make sure that this field is populated for a successful validation of the listing. The Building name field is optional, but when filled will auto-populate the Locationtext. Once values have been found click the "Update" button. Both fields use a full text search so that valid values are used upon saving.
Property Finder Fuzzy Finder (Location Chooser)
This a text field uses a full text search to find specific location address allowed by the portal. After a selection is found a green arrow will appear, this is just a notification that the value validates. The "Update" button will need to be clicked in order for it to properly save.
Note: The chosen location will also be applied to the Bayut feed.
When all of the required fields and the portal location components have been properly filled out the listing record is now ready to be added to the portal groups. At the bottom of the listing record page the field "System Allowed for Portal" can be found. This checkbox will allow the listing to be added to the different portals available in the Portal Syndication component:
If any required data is missing validation rules will trigger and notify what fields should be populated. Once this flag is marked true then the Portal Syndication Component will display that the listing is valid and can be added to a portal group.
Once you created an active portal, it will show up on the Portal Syndication section of listings:
By simply clicking the Add/Publish button, the listing record will be added to that particular portal feed group. To verify how many listings are in a portal feed, the Portal tab can be used. Simply open App Launcher and search for the "Portal" tab. On the Portal Tab, select the portal you are interested in and find the active portal listings in its related list:
Part 2: Steps to Publish
After all relevant Listings have been added to the portal(s) and they are ready to be published create the feed URL (1). There will be unique URL's for each of the portals. These URL's will need to be provided to the specific portals for validation (2). If the validation is incomplete the portal will provide the reasons and the listings will need to be fixed. When the portals have validated the listings and confirmed by the client they will be officially added to the portals and available for the public.
1. Identify and copy the MANDA Feed URL.
If you do not know where to find this URL, reach out to
email@example.com, make sure you granted access and provide the Portal name you need the feed URL for. We will identify the URL and provide you with more information.
2. Now send this URL to the portal.
Images & Media
Don't forget to select some images and media for "Portal" on the Listing's (or Property's) Media Manager overview.
Floorplan: by tagging an image file (e.g. jpg, jpeg, png, bmp, gif) with "Floorplan" (note: exact spelling) it will be handed over to the portal correspondingly and if the portal supports this they will show it in a dedicated way.
Virtual Video Tours: virtual video tours by adding the external link (URL) to the video and tagging it with "Virtual Tour" (note: exact spelling) for youtube videos
360 Tours: 360˚ tours can be added by adding the external link (URL) to the video and tagging it with "360tour" (note: exact spelling) for supported 360 Tour URLs. Please check with the portal's specification which 360-tour-provider-links they support.
Should you not have the tags available, please add them to the picklist field "Tags" on the PropertyMedia object in Setup>Object Manager. After adding them, please clear your cache or log out and back if the values don't show in the Media Manager after a page refresh.
For any questions or comments please contact firstname.lastname@example.org