This article is for Ruuster 1.0. If your brokerage has moved to 2.0, read the 2.0 version.

Tags Passed via CRM Integrations

A reference table of every tag Ruuster exchanges with Follow Up Boss and Sierra Interactive, including direction and what triggers each tag.

This reference table lists every tag that passes between Ruuster and your CRM via the Follow Up Boss, Sierra Interactive, and/ or SureSend API integration.

These are system-wide tags common to all Ruuster accounts, separate from custom tags that individual clients apply to their own saved searches.

Description

Tag

Direction

Apply this tag to a client in the CRM to add that client to your associated Ruuster account.

Ruuster

CRM → Ruuster

Apply this tag to a client in the CRM to apply the default saved search via AI Nurture inside Ruuster.

Ruuster Default Search

CRM → Ruuster

An invitation to sign up or download your custom-branded mobile app was sent to the client.

appClientInviteSent

Ruuster → CRM

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.

appClientOnboarded

Ruuster → CRM

The client viewed a property inside the client portal. The specific property is not signified via tag. Agents can view the client activity tab in the mobile app for details, and Ruuster also logs specific property views as notes in the lead detail page in the integrated CRM.

appViewedProperty *

Ruuster → CRM

The client ran a property search inside the client portal. The specific search is not signified via tag. Agents can view the client activity tab in the mobile app for details, and Ruuster also logs specific property searches as notes in the lead detail page in the integrated CRM.

appPropertySearch

Ruuster → CRM

The client viewed a page inside the client portal. This could be a property listing, a vendor portal page, the budget calculator, or another page.

pageViewedInApp *

Ruuster → CRM

The client selected to contact a vendor from within the client portal. The specific vendor is not signified via tag. Agents can view the client activity tab in the mobile app for details, and Ruuster also logs specific vendor contacts as notes in the lead detail page in the integrated CRM.

clientRequestPreferredVendorContact *

Ruuster → CRM

The client updated their info (name, email, or phone number) from within the client portal.

clientInfoUpdatedFromApp

Ruuster → CRM

The client was manually reassigned by an admin to another agent from within the client portal.

clientReassignedFromApp *

Ruuster → CRM

The client has registered on a landing page provided via the Ruuster IDX.

clientHasSignedUpOnLandingPage

Ruuster → CRM

The client has sent an inbound chat message through the client portal. The specific message contents are not signified via tag. Agents can view the client activity tab in the mobile app for details, and Ruuster also logs specific chat message contents as notes in the lead detail page in the integrated CRM.

appChatMessage *

Ruuster → CRM

The client has favorited a property through the Ruuster IDX. The specific property is not signified via tag. Agents can view the client activity tab in the mobile app for details, and Ruuster also logs specific favorited properties as notes in the lead detail page in the integrated CRM.

appFavoriteProperty *

Ruuster → CRM

The client has saved a search performed via the Ruuster IDX. The specific saved search is not signified via tag. Agents can view the client activity tab in the mobile app for details, and Ruuster also logs specific saved searches as notes in the lead detail page in the integrated CRM.

appSavedSearch *

Ruuster → CRM

The client has chosen in the portal to stop receiving notifications. They will no longer receive any actively applied notifications via email, text message, or push notification. This action does not impact any communication methods in the lead's connected CRM.

Stop notifications

Ruuster → CRM

The client has placed a phone call to their agent via the client portal by selecting "Call Agent".

appInitiatedCallWithAgent *

Ruuster → CRM

The client has requested a property tour from within the client portal. The specific property and tour information are not signified via tag. Agents can view the client activity tab in the mobile app for details, and Ruuster also logs specific property and tour information as notes in the lead detail page in the integrated CRM.

appPropertyTourRequested *

Ruuster → CRM

The client has submitted a "Contact Agent" form from a property detail page as part of their account creation.

ruusterNewLeadFromContactForm

Ruuster → CRM

The client has submitted a "Contact Agent" form from a property detail page and their lead information was updated as part of their submission.

ruusterUpdateLeadFromContactForm

Ruuster → CRM

The client has submitted a "Contact Agent" form from a property detail page.

ruusterContactForm

Ruuster → CRM

A new lead was created in the CRM from the Ruuster IDX or mobile app. This tag is added alongside a tag containing the email address of the assigned agent.

RuusterNewLead

Ruuster → CRM

The client clicked the unsubscribe button in a property alert sent via the client portal. This action does not impact any communication methods in the lead's connected CRM.

ruuster_e-alert_user_unsubscribed

Ruuster → CRM

The client was unsubscribed from a property alert because of an email bounce or another reason other than manually selecting to unsubscribe. This action does not impact any communication methods in the lead's connected CRM.

ruuster_e-alert_auto_unsubscribed

Ruuster → CRM

This tag is added to any client for whom Ruuster has imported searches from another service.

Ruuster E-Alert

Ruuster → CRM

Good to know

  • Asterisk tags fire repeatedly. Any tag marked with * will apply more than once when applicable. Each time the tag fires, if it is already applied to the lead, Ruuster removes it and immediately re-adds it. This allows you to trigger the same CRM automation multiple times without any manual action from your agent.

  • Activity details live in the app and CRM notes. For tags that do not carry specific details (such as which property was viewed or which vendor was contacted), agents can find the full details in the client activity tab in the mobile app, in the Ruuster widget inside Follow Up Boss, or as notes on the lead detail page in the integrated CRM.

  • Notification and unsubscribe tags are Ruuster-only. The "Stop notifications" and e-alert unsubscribe tags affect delivery within Ruuster only. They do not change communication settings in Follow Up Boss, Sierra Interactive, and/ or SureSend.

  • RuusterNewLead includes an agent tag. When this tag fires, a second tag containing the assigned agent's email address is added to the lead at the same time.

FAQ

Which CRMs receive these tags?

These tags are exchanged via Ruuster's direct API integrations with Follow Up Boss, Sierra Interactive, and/ or SureSend. They apply to all Ruuster accounts using either of those integrations.

Why does a tag get removed and re-added instead of just staying on the lead?

CRM automations typically only fire when a tag is first added. Removing and immediately re-adding a tag causes the CRM to treat it as a new application, so the automation can run again without an agent having to touch anything manually. Only tags marked with an asterisk (*) behave this way.

Can I tell which property or vendor triggered an activity tag?

Not from the tag itself. Tags for actions like property views, vendor contacts, and saved searches do not carry specific details. To see what triggered the tag, check the client activity tab in the mobile app, the Ruuster widget in Follow Up Boss, or the notes on the lead's detail page in your CRM.

Will unsubscribing from Ruuster alerts also stop emails from my CRM?

No. The "Stop notifications" tag and the e-alert unsubscribe tags only affect notifications sent through Ruuster. They have no impact on emails, texts, or other communication managed by Follow Up Boss, Sierra Interactive, and/ or SureSend.

What is the difference between ruusterNewLeadFromContactForm and RuusterNewLead?

ruusterNewLeadFromContactForm fires when a client submits a "Contact Agent" form as part of creating their account. RuusterNewLead fires whenever any new lead is created in the CRM from the Ruuster IDX or mobile app, and it is always accompanied by a tag showing the assigned agent's email address.

Was this helpful?

Related articles