Tags passed via CRM integrations

Ruuster's API integrations with Follow Up Boss and Sierra Interactive use standardized tags to sync client information between platforms. Two tags travel from your CRM into Ruuster to trigger actions; the rest travel from Ruuster into your CRM to record what the client did, so you can build filters and automations on them.

Complete tag reference

Direction	Tag	Description
CRM to Ruuster	Ruuster	Applying this tag to a client in the CRM in order to also add that client to your associated Ruuster account.
CRM to Ruuster	Ruuster Default Search	Applying this tag to a client in the CRM will apply the default saved search via AI Nurture inside of Ruuster.
Ruuster to CRM	appClientInviteSent	An invitation to sign up/download your custom-branded mobile app was sent to the client.
Ruuster to CRM	appClientOnboarded	The client has logged in to their account via the client portal. This is a one-time tag to signify that the client's account has been created.
Ruuster to CRM	appViewedProperty *	The client viewed a property inside of the client portal. The specific property is not signified via tag; agents can see it in the client's activity in the app and in the Ruuster widget inside of FUB. We also log specific property views as notes in the lead detail page in the integrated CRM.
Ruuster to CRM	appPropertySearch	The client ran a property search inside the client portal. The specific search is not signified via tag; agents can see it in the client's activity in the app and in the Ruuster widget inside of FUB. We also log specific property searches as notes in the lead detail page in the integrated CRM.
Ruuster to CRM	pageViewedInApp *	The client viewed a page inside the client portal. This could be a property listing, a vendor portal page, the budget calculator, etc.
Ruuster to CRM	clientRequestPreferredVendorContact *	The client selected to contact a vendor from within the client portal. The specific vendor is not signified via tag; agents can see it in the client's activity in the app and in the Ruuster widget inside of FUB. We also log specific vendor contacts as notes in the lead detail page in the integrated CRM.
Ruuster to CRM	clientInfoUpdatedFromApp	The client updated their info (name, email, and/or phone number) from within the client portal.
Ruuster to CRM	clientReassignedFromApp *	The client was manually reassigned by an admin to another agent from within the client portal.
Ruuster to CRM	clientHasSignedUpOnLandingPage	The client has registered on a landing page provided via the Ruuster IDX.
Ruuster to CRM	appChatMessage *	The client has sent an inbound chat message through the client portal. The specific message contents are not signified via tag; agents can see it in the client's activity in the app and in the Ruuster widget inside of FUB. We also log specific chat message contents as notes in the lead detail page in the integrated CRM.
Ruuster to CRM	appFavoriteProperty *	The client has favorited a property through the Ruuster IDX. The specific favorited property is not signified via tag; agents can see it in the client's activity in the app and in the Ruuster widget inside of FUB. We also log specific favorited properties as notes in the lead detail page in the integrated CRM.
Ruuster to CRM	appSavedSearch *	The client has saved a search performed via the Ruuster IDX. The specific saved search is not signified via tag; agents can see it in the client's activity in the app and in the Ruuster widget inside of FUB. We also log specific saved searches as notes in the lead detail page in the integrated CRM.
Ruuster to CRM	Stop notifications	The client has selected in the portal to no longer receive notifications, which means they will not receive any actively applied notifications via email, text message, and/or push notification. This action will not impact any communication methods in the lead's connected CRM.
Ruuster to CRM	appInitiatedCallWithAgent *	The client has placed a phone call to their agent via the client portal by selecting "Call Agent".
Ruuster to CRM	appPropertyTourRequested *	The client has requested a property tour from within the client portal. The specific property and tour information is not signified via tag; agents can see it in the client's activity in the app and in the Ruuster widget inside of FUB. We also log specific property and tour information as notes in the lead detail page in the integrated CRM.
Ruuster to CRM	ruusterNewLeadFromContactForm	The client has submitted a "Contact Agent" form from a property detail page as a part of their account creation.
Ruuster to CRM	ruusterUpdateLeadFromContactForm	The client has submitted a "Contact Agent" form from a property detail page and their lead information updated as a part of their submission.
Ruuster to CRM	ruusterContactForm	The client has submitted a "Contact Agent" form from a property detail page.
Ruuster to CRM	RuusterNewLead	When a new lead is created in the CRM from the Ruuster IDX or mobile app, this tag is added to the lead. This tag will accompany a tag with the email address of the assigned agent.
Ruuster to CRM	ruuster_e-alert_user_unsubscribed	The client has clicked on the unsubscribe button in a property alert sent via the client portal. This action will not impact any communication methods in the lead's connected CRM.
Ruuster to CRM	ruuster_e-alert_auto_unsubscribed	The client has been unsubscribed from a property alert because of an email bounce or another reason other than manually selecting to unsubscribe. This action will not impact any communication methods in the lead's connected CRM.
Ruuster to CRM	Ruuster E-Alert	This tag is added to any client for whom we have imported searches from another service.

Good to know

• Tags marked with an asterisk (*) apply multiple times when applicable. Every time one of those tags fires from Ruuster to your API-connected CRM, if that tag is already applied, then the initially applied tag is removed and added again immediately after. This lets you trigger automations on recurring client actions without manual intervention.
• The appInitiatedCallWithAgent tag comes from the "Call Agent" action in the client portal. In the redesigned client app, calling happens through the agent's contact details rather than a dedicated Call Agent button, so expect this tag to fire rarely from clients on the new design.
• For the tags that control property-alert emails, see Tags and property search unsubscribes.

FAQ

A tag disappeared and reappeared on a lead within seconds. Is something broken?

No. That is the repeat-action behavior for asterisked tags: remove, then immediately re-add, so your automations fire again.

Does "Stop notifications" or an unsubscribe tag stop my CRM's own emails?

No. These tags only reflect the client's notification choices inside Ruuster. Communication methods configured in your CRM are untouched.

Still need help? Reach out to us at helpme@ruuster.com and we'd be happy to assist!