Important Events to Track

Which Events Should You Track?

Generally, you should track every event that your website or system supports. Your Brytelytics dashboards and user profiles will be more accurate and interesting if you track all of your events.

Events are tracked for specific purposes and each has its use. Events can be used for reporting, for lead scoring and profiling, or for generating leads to be sent to your agents.

You may want to focus on lead-generating events first, to ensure all leads get captured and pushed into Lead Voyager. If you are not using the lead routing features of Lead Voyager, this may not be a priority, and you may want to focus on which events are used for reporting app and site activity for your brokerage and marketing teams.

Reporting Events

These events drive the charts in your reporting dashboards. If these events are not tracked, some of your reports will be missing or incomplete.

Scoring Events

These events add data used by the Brytelytics machine learning algorithms to understand lead personas and aggregated information, such as target neighborhood and price. Without these events, the accuracy of predictions and behavior thresholds may suffer.

Lead-Generating Events

These events create new leads that can be assigned to agents. Without these events, you may not capture all situations where a lead may expect to be contacted by an agent.

The table below should help you prioritize which events should be tracked by your system.

Required events marked with an asterisk (*). Please note that adding only the required events is almost never the correct way to implement the API. If your system does not have an event marked as required, please contact Brytecore Support.

Which Properties Should You Track?

Many events expect an object as one of the parameters. Similar to event tracking, you should track every property on objects that your system supports. This section should help you prioritize which object parameters you should provide.

listing

• address (an address object)
• bedrooms
• features (an array of strings, ex: ["master on main", "fireplace", "level lot"])
• fullBaths
• geoLocation (a geo object)
• halfBaths
• isCommercial
• isCondo
• isForeclosure
• isLot
• isMultiFamily
• isRental
• isSingleFamily
• listingURL
• mlsId
• photoURL
• price

address

• streetAddress
• streetAddress2 (null if unavailable)
• city
• stateProvince
• zipPostal
• country

geo

• latitude (ex: 33.859821)
• longitude (ex: -84.168221)

search

Note these are parameters passed by the user when performing a search. As such, none are required, because the user may not pass any parameters at all, or only a few. Send us what the user searches for.

• address (an address object, ex: {"state":"RI"} when searching only for properties in Rhode Island)
• bedroomsMin
• bedroomsMax
• cities (an array of strings, ex: ["Cape Cod", "Boston"])
• counties (an array of strings, ex: ["Barnstable"])
• features (an array of string values of features that the user checked in their search, ex: ["Beach", "1 Car Garage", "Bungalow"])
• fullBathsMax
• fullBathsMin
• halfBathsMax
• halfBathsMin
• isCondo
• isForeclosure
• isLot
• isMultiFamily
• isRental
• isSingleFamily
• mlsIds (an array of strings, ex: ["1118198"])
• postalCodes (an array of strings, ex: ["02840", "02891"])
• priceMax
• priceMin
• resultsCount (the number of matching search results)
• searchURL
• yearBuiltMax
• yearBuiltMin

realEstateForm

Note that these fields will vary by form - send what you have.

• agentName
• fromEmail
• fromName
• fromTelephone (a telephone object)
• isPrequalified
• isWorkingWithAgent
• message
• name
• relatedListing (a listing object)
• subject
• toEmail
• toName

telephone

Note that this can include more than one number, but only one number of each type.

• mobile
• home
• work
• fax
• direct