An activity is something that happened related to a lead. Some activities are automatic and others actual actions the lead or the assigned agent have performed, like
- a lead performing a search on the website
- an agent adding a note associated with a lead
- an email sent to the lead was opened
- the Lead Manager CRM assigned this lead to an agent automatically using our Round-Robin algorithm
| Field name | Type | Presence | Description |
|---|---|---|---|
type |
string | required | See the list of all types available below |
source |
string | required | Where this activity is coming from |
description |
string | required | Human readable description |
property |
Property object | optional | In case this activity was related to a specific property. If present it is an object with Property fields described below |
user |
User object | optional | Some activities are related to an Agent or a Lender, in those case the user details will be set in a User object |
created |
string | optional | When creating a lead this field is optional and if not provided will be set to the time the request was received. Format must be a combined date and time according to ISO 8601, ex.: “2015-04-01T08:41:51+00:00” |
notify_users |
boolean | optional | Set this to true to trigger a notification in Lead Manager CRM to the assigned agent and/or lender. Make sure the Notification setting Activity shared by another user is enabled. |
Activity Types
Activity type indicates what action was performed by the lead. It’s one of these values:
| Type | Description |
|---|---|
visited |
User visited the site for the first time (initial sign-up) or is back to the site after two hours of inactivity |
search_performed |
User performed a search on the website. Description will contain a summary of the search filters |
saved_search_added |
User not only performed a search but also saved it to their profile. Description will contain a summary of the search filters |
saved_search_removed |
User removed a saved search. Description is the same as “saved_search_added” |
property_viewed |
User visualized a property on the website. Description contains a summary of the property details and a link to it. |
favorite_property_added |
User marked a property as favorite. Description contains a summary of the property and a link to it on the website. |
favorite_property_removed |
User removed a favorited property. Description is the same as “favorite_property_added” |
property_updates_email_sent |
Our systems sent an email to the user with updates about their saved searches and favorited properties, with information like price changes and new properties available |
property_updates_email_opened |
When the property update email is opened by a lead, this activity is sent. This activity also includes a metadata key with the unique ID of this email. You can compare this to the same unique ID sent in the metadata key of the property_updates_email_sent activity to track engagement. |
bad_email_flagged |
Our systems detected that the email address this user signed up with is not valid, emails failed to be sent to it |
bad_email_unflagged |
Our systems can now send emails to this user’s email address |
opted_out |
User opted out of our property updates emails |
deleted |
Lead was deleted from Real Geeks. Please note that a lead can be “restored” by the support team. If this happens, you will receive a “restored” activity to undelete the lead. |
restored |
A lead that was previously deleted was restored by the RG support team. This should “undelete” the lead. |
deleted_from_website |
Lead was deleted from the website. Note that other systems, like our Lead Manager CRM, could still have this lead saved. |
contact_emailed |
user sent a contact message. |
valuation_inquiry |
User used the property valuation tool to see the estimated value of a property. |
shared_property_via_email |
Lead shared a property by email with somebody else, the description will contain the property url and the name and email of the person they shared it with. |
market_report_viewed |
User viewed a market report on the site. |
saved_market_report |
User saved a market report page in their saved searches. |
coming_soon_viewed |
User viewed a coming soon page on the site. |
note |
Agent has added an internal note about this lead on the Lead Manager CRM. The note itself will be in the activity description |
called |
Agent called the lead |
was_assigned |
Agent or Lender was assigned to this lead. For this activity the user field is required. Could happen more than once in case of reassignments, use the created field to ensure you’re handling the most recent one. There is no difference between an automatic lead assignment – from the Round-Robin – and a manual one. |
was_unassigned |
Agent or Lender was unassigned, now this lead not assignment to anyone. The description will have a human readable message of what happened. This activity is always triggered by the Lead Manager CRM. |
waiting_for_manual_assignment |
Sent from the Lead Manager CRM when a new lead is created and there is no automatic lead assignment configured. Since manual assignment requires human interaction it could potentially take a long time so this activity helps you decide whether to wait or not. This activity is always triggered by the Lead Manager CRM. |
received_text_message_from |
Text messaging is enabled and a lead sent a text message to the agent |
sent_text_message_to |
Text messaging is enabled and an agent sent a text message to the lead |
tour_requested |
Lead requested a tour from the website |
imported |
Lead was imported from a CSV file in the Lead Manager CRM |
Property Fields
When an activity was related to a property, like property_viewed, one of it’s fields is property, which is an object with the following fields:
| Field name | Type | Presence | Description |
|---|---|---|---|
mls |
string | optional | MLS number |
url |
string | optional | Full absolute url to visualize property |
street_address |
string | optional | Street portion of the address, ex: “123 Keolu Rd Unit 12” |
city |
string | optional | |
state |
string | optional | |
zip |
string | optional | |
beds |
integer | optional | Number of bedrooms |
full_baths |
integer | optional | Number of full bathrooms |
half_baths |
integer | optional | Number of half bathrooms |
type |
string | optional | Human readable type, ex: “Single Family Home” or “Condo” |
sqft |
string | optional | Property square feet, has no format requirement |
listing_price |
string | optional | If the property is being sold this is the price it’s being listed for. The supported format is a number with optional decimal places, ex.: “100500” or “100500.90” |
listing_status |
string | optional | If the property is being sold this is the current status, any format is allowed. ex.: “For Sale” |
listing_days_on_market |
integer | optional | If the property has pending date, the number of days between list date and pending date. If the property has no pending date, but has a closing date, the number of days between list date and closing date. If the property has no closing date, but has a list date, the number of days between list date and today. Otherwise, nothing |
list_date |
string | optional | When this property was listed for sale. Format must be a combined date and time according to ISO 8601, ex.: “2015-04-01T08:41:51+00:00” |
estimated_value |
string | optional | Estimated value this property could be sold for, useful for Seller or Potential Seller leads. Could be from an automated or personalized valuation. The supported format is a number with optional decimal places, ex.: “100500” or “100500.90” |
last_sold_date |
string | optional | Doesn’t have any format requirement, could be something like “2015-12-25” |
last_sold_price |
string | optional | If present will be a number with optional decimal places, ex.: “100500” or “100500.90” |
rent_price |
string | optional | Monthly rent price, used if this property is for rent |
tags |
[]string | optional | Search tags, could be address components or any other field that destinations might use to easily implement a search feature. For Real Geeks websites we send things like street address, neighborhood, state, island, MLS number, etc. i.e. [“kailua”, “212”, “oahu”, “981112”] |
latitude |
float | optional | |
longitude |
float | optional | |
year_built |
integer | optional | Year this property was built |
User Fields
When an activity was related to an Agent or Lender from the Lead Manager CRM, like was_assigned, one of its fields is user, which is an object described in ourUsers API.
