All real estate advertising websites, partner sites, and member websites are required to display the “Powered by REALTOR.ca” badge. This badge must link back to the original listing on REALTOR.ca.
If a REALTOR® is managing their own website directly (without using a third-party provider), it is their responsibility to ensure the badge is displayed on every listing page.
Use the following code snippets to embed the “Powered by REALTOR.ca” logos and links into your website:
English
<a href="https://www.realtor.ca/en" alt="Powered by: REALTOR.ca" target="_blank"> <img width="125" src="https://www.realtor.ca/images/en-ca/powered_by_realtor.svg"/></a>
French
<a href="https://www.realtor.ca/fr" alt="Alimenté par: REALTOR.ca" target="_blank"> <img width="125" src="https://www.realtor.ca/images/fr-ca/powered_by_realtor.svg"/></a>
Analytics
In addition to distributing listing data to member websites, brokerage websites, franchisors, and third-party platforms, the MLS IDX API also supports integration with various public websites and mobile applications.
Since a single listing can appear across multiple sites and apps, it’s important for agents and brokerages to be able to track where and how often their listings are being viewed. To enable this, the MLS® IDX API includes support for a data warehousing solution that collects and organizes listing activity.
Analytics can be broken down across several dimensions, such as:
- Website or application where the listing was viewed
- Listing agent
- Real estate firm
- Brokerage owner
- Franchisor
This ensures agents and brokerages have clear insight into the performance and visibility of their listings across multiple channels.
Analytics Web Service
The Analytics Web Service is used to capture listing activity and statistics from various sources. Whenever a listing-related event occurs (such as a property being viewed), the website or application should send a request to the Analytics Web Service to record the event.
No response handling is required, which means these requests can be made asynchronously without interrupting the user experience.
End Point
https://analytics.crea.ca/LogEvents.svc/LogEvents
Request Arguments
| Argument | Type | Description | Required | Supported Values |
|---|---|---|---|---|
| ListingID | Integer | Specifies the ID of the listing. | Yes | |
| DestinationID | Integer | Specifies the ID of the destination where the data is being sent or recorded. | Yes | Specifies the destination ID of the data feed where the event takes place. |
| EventType | String | Specifies the event being tracked by the analytics system (for example, a property view or other listing interaction). | Yes | Refer to the Event Types section below for supported values. |
| UUID | String | Specifies the unique identifier for a user or device. This value should remain consistent across all requests made by the same user or device. | Yes | A GUID or device identifier combined with the Destination ID. Note: UUIDs are tracked in 5-minute windows. If the same UUID generates an identical event within that timeframe, the duplicate event is ignored. |
| IP | IP Address | Provides the IP address of the client or device, if available. | No | Note This parameter is used to resolve geographic data. If it is not provided, geographic information will not be included in the results. |
| RefererralURL | URL | Specifies the URL associated with the event, which is validated during analytics processing. | No | |
| LanguageID | Integer | Indicates the language preference of the user. | No | 1: English 2: French |
Event Types
| Event | Description |
|---|---|
| View | Event to be triggered when a listing is viewed on a website. |
| Click | This event applies to third party websites only. It should be triggered when the MoreInformationLink (included in the PropertyDetails payload) is clicked. |
| email_realtor | This event applies to third party websites only. It should be triggered when an email inquiring about a particular listing is sent to the REALTOR®. |
Example
Appendix – Payload Legend
This appendix describes the columns used in the payload tables in Appendix A-J
Cardinality is used to identify how many times an element can be expected within the Standard-XML payload.
1 Exactly one instance of this element.
0..1 Zero or one instance of this element.
0..* Zero or more instances of this element.
1..* One or more instances of this element will be included
Type is used to identify the type of data to be expected in an element within the Standard-XML payload.
Boolean True/False
Collection A collection of similar elements
Complex Comprised of primitive data types and/or other complex elements.
DateTime A date and time
Integer A whole number
Lookup A value taken from the associated lookup. In Encoded format, the
both the lookup ID and text value is available.
Lookup
(CSV)
A comma separated list of values taken from the associated lookup.
In Encoded format, the both the lookup ID and text values are
available.
Script A JavaScript script to be used for gathering analytics data from client
websites (deprecated, still included for backwards compatibility)
String String
(CSV) Free text representation of the value
A comma separated set of free text values
URL Website address
Type is used to identify the metadata lookup table associated with the element. Any values available in the element can be found in the identified Lookup table.