Introduction to Sisu and BoomTown

In partnership with BoomTown, we are excited to announce our direct Sisu integration.

Accessing the BoomTown integration from the Integration Hub

You will setup and maintain your BoomTown integration from the Sisu Integration Hub (Admin > Integration Hub).

Overview, highlights, key features and BoomTown platform requirements

Here is an introduction video on the integration and configuration overview. In addition to watching this video, please make sure to read all the information below, in detail, and watch the additional videos below.


  • To use the Sisu and BoomTown integration at no additional cost, you will need to make sure you are on BoomTown's Grow or Advanced subscription plan. You can quickly tell if you are on Grow or Advanced by checking out your BoomTown integrations page from your right corner dropdown in BoomTown.


If you do not see Sisu at the top of your Integrations center, you are on a Launch or Core subscription or to pay a minimal integration access fee to the Sisu sync. Reach out to your BoomTown account executive to quickly add this integration.

  • At the current time, the integration only works for BoomTown "Active Users" (Agent or Broker/Admin) and NOT "Profile-Only" users.

  • The integration is designed to run only from the time that you have turned on the integration and NOT pull historical data from BoomTown.

  • If you are running multiple websites in your BoomTown configuration. Please reach out to Sisu prior to setting up this integration. Particularly if you have already implemented Sisu. You will need a separate Sisu team and subscription for each BoomTown instance/site that you are running.

  • Turn off other integrations. If you are currently using a third-party provider in conjunction with Sisu and BoomTown (i.e. Real Synch, API Nation, or Zapier), please disable any integration(s) that may affect your live data. The video below walks you through how to deactivate the likely integrations that you may have in place between Sisu and BoomTown.


  • The integration runs automatically every five minutes, however, a Sisu Admin or TC can run the sync on-demand with the "Run Now" button.

  • If a BoomTown client record was used to create a Sisu transaction through this sync, your Sisu users can open the BoomTown client record directly from Sisu.

  • The integration is designed (unless specified below) to do a one-time Sisu transaction creation from BoomTown client record data. There will not be any BoomTown lead record syncing with the Sisu transaction record (i.e. updating the phone number on the BoomTown lead record will not update the Sisu transaction record).

  • If you specify that you want BoomTown transaction records to be created when Sisu transactions go "Under Contract", the Sisu transaction will be the primary record source for the BoomTown transaction. Your users will make all of their updates to the Sisu transaction which will automatically keep the BoomTown transaction record in sync (i.e. date changes, transaction amount changes will be made in Sisu and pushed to BoomTown).

  • The integration setup has to be performed by a Sisu and BoomTown Administrator.

  • After setup, and to ensure your Activities are accurate, your Sisu configuration will have the following Activities LOCKED. These Activities can only be modified through BoomTown usage.

  • To ensure that your Conversations and Dial metrics are valuable on your team and personal dashboards, leaderboards and in your Sisu Production & Activity, Agent Accountability, Performance & Conversion reporting, BoomTown Dials will automatically add to Sisu's NUMBER OF DIALS core system activity and BoomTown Conversations will automatically add to Sisu's NUMBER OF DIALS and CONVERSATIONS core activities.

  • We have greatly simplified the authentication between Sisu and BoomTown. Your User - Agents table in BoomTown will automatically remain in sync with your Sisu users. The best practice is to add your user to BoomTown first which will automatically add users directly into Sisu. For your existing Agent lead roster in BoomTown, they will initially come over to Sisu as "Active" users and you can manually make any of the users "Inactive". This process could take up to 5 minutes to sync. For Sisu licensing purposes you will need to ensure that you have a Sisu license for each active BoomTown user.

  • Stay in the loop with the BoomTown Logs table. See in real-time what is going on with your BoomTown and Sisu sync.

What the BoomTown and Sisu integration currently DOESN'T do

In an effort to rapidly release this first version of the integration to address the majority of concerns and requirements our BoomTown and Sisu customers had with prior integrations, we weren't able to fit everything into this initial release. After the initial release of this integration, we will be quickly working on the following:

  1. Automated lead source reporting: Automating the total Agent Lead Count and Total Lead Count from your BoomTown agent assignment and reassignment, per lead source is vital and a top priority for the next release. This will ensure that your Lead Source ROI and Lead Sources by Agent reports are automated and accurate.

  2. Support of BoomTown tags: This current integration does not currently support the creation of Sisu transaction tags from the BoomTown tags.

  3. Bi-directional syncing of the Sisu transaction with the BoomTown transaction: The integration is designed to create and keep the BoomTown transaction updated FROM the Sisu transaction when the Sisu transaction goes Under Contract. Best practices are defined below, but it is recommended that the Sisu transaction automatically create the BoomTown transaction and keep the BoomTown transaction up to date - due to Sisu' ability to lock critical transaction information and keep the transaction information pristine in Sisu.

Connecting Sisu and BoomTown

Setting up Sisu and BoomTown the first time is a snap. Here are the highlights of the setup:

Configuring your Sisu and BoomTown integration and running your initial sync with BoomTown

Configuring your Sisu and BoomTown integration is easy. However, there are some key strategies to follow prior to setting up your integration. Click on the BoomTown tile to start your setup.

1. Strategies on your initial synchronization

Garbage In... Garbage Out... The data in Sisu will only be as good as your data and configuration in BoomTown. If you have been lax in the management of your BoomTown platform - then you run the risk of corrupting your existing Sisu production data (if you are an existing Sisu customer) or new Sisu production data (if you are a new Sisu customer). Here are some great strategies to follow on your initial synchronization with BoomTown.

2. Ensuring that your team settings reflect the correct timezone

All of your activity and logged date will be based on your team, timezone settings. Make sure you have ensured that the timezone is accurate.

3. Setting and thoroughly reviewing your BoomTown categories prior to your initial sync:

By design, Sisu provides a powerful sales performance management system so you and your agents can focus on those "Hot" and "Pending" clients from your BoomTown system. These Sisu transactions are vital in your weekly accountability coaching meetings. If your "Hot", or 1st APPOINTMENT SET BoomTown clients are inaccurate - then your coaching meetings are ineffective.



To allow for this focus, the creation of Sisu PIPELINE transactions trigger off of the current BoomTown Categories settings you determine in Sisu and the current category of the BoomTown lead. Either 1st Appointment Set (i.e. To Do Meetings in BoomTown), Hot and Pending BoomTown categories.

That is why it is vital to thoroughly review your existing BoomTown Hot and Pending categories in Sisu prior to your first initial sync.

For example, if there is an update on BoomTown client record (i.e. web visit, notes added, e-Alerts) AFTER the initial sync has run and you have inaccurate BoomTown "Hot" category leads set, even going back many years, the integration will automatically add Sisu transactions for any leads in those categories (i.e. Hot or Pending). This is by design to ensure that your agents are focusing on those Hot

For example, if you have your CREATE SISU TRANSACTION ON" BoomTown Category is 'hot' category setting enabled and you have any e-Alerts occurring, a client visits your BoomTown site, an agent sends a text, email, or note on that "hot" BoomTown client; after your initial integration sync has been set and is running, the integration will create a transaction in Sisu based on the recent date creation update on that BoomTown record.

Again, this is by design and provides a very powerful tool to provide granular focus on those "Hot" or "Pending" Sisu transactions during your weekly coaching meetings.

4. Your BoomTown and Sisu sync doesn't occur until you click on "Run Now"

After your unique configurations have been set, your integration will start when you click on the "Run Now" button. After that, it will run every 5 minutes, unless you manually click on "Run Now"

5. Moving BoomTown clients into Sisu on-demand; Hots
Importantly when starting your initial configuration of Sisu, you, your team, and importantly agents need to know the importance of those triggers that will move BoomTown clients into Sisu and create transactions. As mentioned earlier, as updates occur to those Hot and Pending clients our intelligent sync design ensures (after you have started your sync) that as automated eAlerts, emailing, and texting by the agents, these Hot clients will automatically create a transaction in Sisu.

During Hot review with your agents of your BoomTown clients, it is really easy to manually and on-demand move these BoomTown clients into Sisu.

The video below provides a great overview.


6. Moving your BoomTown Pending clients into Sisu on-demand and verifying your Under Contract dates

Much like the video above demonstrates, it is vital to ensure that your agent Sisu's Pendings are moved over from BoomTown to Sisu and additional information is added to the Sisu transaction in order to ensure that the forecasted transaction amount, the Under Contract date is accurate and the agent paid income is indicated. This is vital information for agent and team leader coaching meetings and importantly for income and profitability reporting.

By design, the Sisu sync with BoomTown will likely catch many of these Pending after the sync has been turned on because we monitor activity on these client records such as eAlerts, notes, dials, and other client updates on these records.

For these historical Pendings that are getting entered into Sisu, we will move them to a Pending status in Sisu by using the date that the Sisu transaction was created. We recommend that you review your historical Pending. This video walks you through how to build a "Pending" filter in Sisu.



This video provides a quick overview of how to manually move your Pendings over into Sisu by creating a quick Note record on the BoomTown lead record. By design Sisu will create the Under Contract date as the date of Sisu transaction creation so entering the correct Under Contract date is advised, in addition to other key transaction values such as amount, GCI, and Agent Paid Income.

7. Running your initial synch

Check out this helpful video on running your initial sync and ensuring your BoomTown data is updated.

8. Verifying your agent roster

After you run your initial sync we automatically create your Sisu agent roster, retrieving profile photos and attempt to identify the user role from the BoomTown user table. This video will walk you through some additional steps to inactivate users (to free up Sisu licenses), change user roles, and update the user start date.



Monitoring your Sisu and BoomTown integration

At least initially, we recommend creating a couple of saved transaction filters to monitor your BoomTown and Sisu integration. The video below walks you through how to set up these specific transaction filters from your Sisu transaction filter drawer.

How do I select multiple options in my configuration screen?

If you have never used a multi-select selection screen in other systems, it is really easy to select multiple items by using Command + Mouse Click (in Mac OS), Control + Mouse Click (in Windows), or Control + Mouse Click (in Chrome OS).

Understanding the BoomTown logs

The BoomTown Logs screen provides real-time sync information for your BoomTown and Sisu Admins and TC's. This will assist you during ongoing usage when BoomTown users have questions about records and activities syncing. Our Sisu Customer Success team will leverage this for troubleshooting as well.


Manually running the sync and clearing your BoomTown logs

The integration runs automatically every five minutes, however, a Sisu Admin or TC can run the sync on-demand with the "Run Now" button.

What Sisu custom activities are created on the integration setup

To ensure lead measure metric accuracy upon setup of the integration, we will automatically create the following Sisu Custom Activities:

This ensures that the only way these activities can be updated by your agents is through their BoomTown usage. By default, these activities are set to display (checked) and are LOCKED.

Where are my custom activities on the record screen?

Being that these Custom Activities cannot be manually updated, and can only be updated through BoomTown usage, they will not display in the Record screen for your agents.

These Custom Activities will be available in the following:

Leaderboards

Team and personal dashboards

Agent and team activity logs
Check out this video below.





Team and personal snapshot displays

Goal setup

Goal display

Setting Team and Agent Goals on BoomTown Activity Metrics


Why does Sisu report on BoomTown Leads added per agent?

Lead's are the lifeblood of your team, agent leads are EVEN more valuable. For each lead that your agents add to BoomTown, the Sisu and BoomTown integration will keep track on a daily basis to encourage and motivate your agents to add their agent SOI leads directly in BoomTown.

How can I disable my BoomTown sync?

At any time, you can disable the integration between Sisu and BoomTown with the "Disable" button. You also have a visual prompt indicating the integration's status: Enabled or Disabled.

Logging dials, 1:1 emails, and 1:1 texts in BoomTown

Do you want dials, 1:1 emails, and 1:1 texts to only count for prospecting efforts (vs. counting them on any contact in BoomTown)? If so, you can limit the updating of Sisu Activities to only BoomTown Active Lead Categories ("New", "Qualify", "Watch", "Nurture", "Hot") rather than Non-Active Lead Categories ("Pending", "Closed", "Archive", "Trash"). We provide the ability to customize this based on your business processes:

BoomTown category definitions

Sisu Automation Hub configuration for Sisu custom activities

The integration will update corresponding Sisu Custom and Sisu Core Activities when the following BoomTown activities are created:

BoomTown activity

Updates these Sisu custom activities

Also updates these Sisu core activities

Talked to Prospect

BOOMTOWN CONVERSATIONS and BOOMTOWN DIALS

CONVERSATIONS and NUMBER OF DIALS

Left Message

BOOMTOWN DIALS

NUMBER OF DIALS

Call Attempt

BOOMTOWN DIALS

NUMBER OF DIALS

Opted Out

BOOMTOWN DIALS

NUMBER OF DIALS

Wrong Number

BOOMTOWN DIALS

NUMBER OF DIALS

1:1 manual sending a BoomTown email

BOOMTOWN EMAILS

EMAILS SENT

1:1 manual sending a BoomTown text

BOOMTOWN TEXTS

TEXT MESSAGES

Why do we add to CONVERSATIONS and NUMBER OF DIALS?

Conversations and Number of Dials are core Sisu activities that drive additional functionality throughout the Sisu platform. Additionally, by having specific activities for BoomTown, we provide valuable optics for you and your team on your BoomTown usage in isolation. Then, rolling these numbers up appropriately to the Sisu core system activities allows you to fully leverage the following Sisu reports:

Production & activity reporting

Agent accountability reporting

Performance & conversion

Here is a quick video overview:

Creating Sisu transactions from BoomTown category changes (Hot, Pending), BoomTown "Meeting" To-Do's, or Never

Sisu allows you to set multiple BoomTown categories to trigger the creation of your Sisu transactions or "Meeting" To-Do's or never.


A few items to highlight:

  • Unless designated below, the Sisu transaction creation from BoomTown is intentionally designed to be a one-way push of BoomTown client record data to Sisu.

  • To enforce data entry practices and processes, some Sisu teams prefer to control the entry of Sisu transactions by using Virtual Assistants, Transaction Coordinators, and Sales Administration staff to manually enter in all transactions To ensure that we align with these customers, you have the option to "Never" create a Sisu transaction from BoomTown and only utilize the integration for metric tracking.

  • For Buyer/Seller transactions in BoomTown, the sync will create TWO Sisu transactions: One for the Buyer side and one for the Seller side.

  • Check out this video for a detailed walkthrough:

What Sisu transaction information is initially added from BoomTown category changes and/or To Do "Meeting" creation?

Unless specified below, the sync is designed to be a one-time push of the following BoomTown client information to create the Sisu transaction:

From BoomTown client→

To Sisu transaction:

When:

First

FIRST NAME

One time creation on initial submission

Last

LAST NAME

One time creation on initial submission

Buyer Agent or Listing Agent (designated by B, S, or B/S)

AGENT

One-time creation on initial submission. For B/S transactions, a unique Sisu transaction will be created for the Buyer side and one for the Listing side (possibly two different agents).

Phone

MOBILE PHONE NUMBER

One time creation on initial submission

Email Address

CONTACT EMAIL

One time creation on initial submission

"Hot" Category

Sets the Sisu status to "PIPELINE" (meaning no other dates have been populated)

One time creation on initial submission

"Pending" Category

Sets the Sisu status to "PENDING" with the current date as the "Under Contract" date

One time creation on initial submission

Source

LEAD SOURCE

One time creation on initial submission

To-Do of "Meeting" (Date Set) created by a user with a Sisu agent role

1ST TIME APPT SET date is populated based on the creation date of the BoomTown To-Do "Meeting". This causes the Sisu status to be "APPT SET"

Can occur anytime after the transaction is created in Sisu from BoomTown. Only the first To-Do "Meeting" creation date will populate the 1ST TIME APPT SET date in the Sisu Transaction, regardless of the number of subsequent To-Do "Meetings" that are created in BoomTown for that client record.

To-Do of "Meeting" (Date Set) created by a user with a Sisu ISA role

1ST TIME APPT SET date is populated based on the creation date of the BoomTown To-Do "Meeting". This causes the Sisu status to be "APPT SET".

The APPT SET BY (ISA) is populated with the Sisu ISA user and is based on the logged-in BoomTown user who created the "Meeting" (i.e. rather than who is assigned to the "Meeting")

Can occur anytime after the transaction is created in Sisu from BoomTown. Only the first To-Do "Meeting" creation date will populate the 1ST TIME APPT SET date in the Sisu Transaction, regardless of the number of subsequent To-Do "Meetings" that are created in BoomTown for that client record.

The completion of the To-Do of "Meeting" (Date Set)

1ST TIME APPT MET date is populated based on the completed date for the To-Do "Meeting". This causes the Sisu status to be "APPT MET"

Can occur anytime after the transaction is created in Sisu from BoomTown. Only the first To-Do "Meeting" completed date will populate the 1ST TIME APPT MET date in the Sisu Transaction, regardless of the number of subsequent To-Do "Meetings" that are created in BoomTown for that client record.

Registered (date of the lead registration)

Lead Date

One time creation on initial submission

Viewing BoomTown custom activity logs from the team and personal dashboards

Ensuring that you and your team always know when and who created your BoomTown Custom Activities is an important query for you to run from the team and personal dashboards.

Here is a quick overview:


Opening BoomTown client records directly from Sisu

We make it easy to access your BoomTown client records directly from Sisu after the transaction is created from a BoomTown category change ("Hot" or "Pending") or after a BoomTown "Meeting" To-Do item is created (and thus the Sisu transaction would be in the "APPT SET" status).

Here is a quick overview:

Creating the initial Sisu transactions and setting the Appointment Set and Appointment Met from BoomTown To-Do "Meeting" type and APPT SET BY (ISA) Setting

Adding the 1ST TIME APPT SET date and 1ST TIME APPT MET date in Sisu from BoomTown is simple. We have also taken special consideration for your Sisu ISA users. A couple of highlights to ensure you have everything set up correctly:

  • To create the Sisu transaction from a BoomTown To-Do of "Meeting", make sure you have "BoomTown todo: meeting created" as one of your Sisu transaction creation settings:

  • The Agent that is assigned on the Sisu transaction record will get credited for the Appointment Set.

  • If a Sisu ISA user (typically an Agent role in BoomTown) sets the BoomTown To-Do This is regardless of who is assigned to the To-Do "Meeting".

Here is a quick overview:


Setting appointments on any transaction that was created from the BoomTown and Sisu sync

For those "Hot" BoomTown Category changes that created a Sisu transaction, your agents or ISA's can still set the 1ST TIME APPT SET and 1ST TIME APPT MET Sisu dates directly from BoomTown by using the "Meeting" To-Do type.

If your BoomTown user who sets the "Meeting" To-Do is identified in Sisu as an ISA role, we will automatically associate the APPT SET BY (ISA) field to the ISA who set the appointment.



For example, if you have other procedures of when to move BoomTown clients into Sisu, but you still want to motivate your agents to set appointments within BoomTown, the video below walks you through how to accommodate for this. Regardless of the number of To-Do "Meetings" that were set on your BoomTown client record, Sisu will only populate the 1ST TIME APPT SET and 1ST TIME APPT MET dates once - i.e. the first time.

Automatically updating BoomTown categories on Sisu transaction status changes

Keeping your BoomTown categories in sync with Sisu is vital to ensure your CRM stays the primary source of record for your clients.

Update your BoomTown categories on Sisu "Under Contract", "Closed", and/or "Deletes" status changes.

Here is a quick video overview:

Creating BoomTown transactions from Sisu transactions

Creating BoomTown transactions from Sisu transactions provides a wealth of historical information for you and your team and greatly eliminates duplicate entry.

To ensure that you are creating the initial BoomTown transaction from Sisu, make sure that you have turned on the "CREATE BOOMTOWN TRANSACTION WHEN:" setting to create a BoomTown Transaction when a Sisu transaction goes "Under Contract"

A few automatic and time-saving steps we provide on the BoomTown Transaction creation:

  • Automatically changes the BoomTown Transaction status to Under Contract

  • When Sisu Transactions are Closed, we automatically change the BoomTown Transaction status to Closed

  • If you have set the "SET BOOMTOWN CATEGORY ON SISU TRANSACTION STATUS CHANGE:" to "Sisu Under Contract is BoomTown Pending" and "Sisu Closed is BoomTown Close" setting we will update the BoomTown Categories. This setting does not require that you use the "CREATE BOOMTOWN TRANSACTION WHEN:" setting and can be used independently if you do not want to create BoomTown Transactions from Sisu Transactions when they go Under Contract in Sisu.

Making sure to track BoomTown transaction required fields and have them on your transaction forms

Sisu automatically by design stores and initiates the majority of the required fields needed to create a BoomTown transaction. Those fields include;

  • Agent

  • Representing (Buyer/Seller)

  • Status (Under Contract)

  • Address

  • City

  • State

  • Price


If your Sisu transaction form(s) do not have the appropriate fields; specifically City, State, here is a quick overview of how to ensure that this information is tracked.

Best practices to keep BoomTown transactions up to date

The majority of Sisu customers thoroughly use Sisu transaction management functionality as their core system of record. Largely, in part:


This being said, the current design of how Sisu interacts with the BoomTown Transaction records is a ONE-WAY, continuous update of Sisu transaction information to the corresponding BoomTown transaction record. Changes in the BoomTown transaction will be overwritten by the Sisu transaction.

A recommended process for your TC's and Agents who interact with the Sisu transaction before and after it is locked, is to make all updates to the Sisu transaction in order to automatically keep the BoomTown transaction information up-to-date for historical review from BoomTown and/or Dotloop or other document generation/compliance updates.

What BoomTown transaction information is updated initially and ongoing from the Sisu transaction?

The sync is designed to update BoomTown transactions from the creation of the Sisu transactions and ongoing updates in the Sisu transaction. Changes made in the BoomTown transactions will not be reflected in the Sisu transactions upon saving and will be overwritten from Sisu with ongoing transaction syncs. Required BoomTown and Sisu fields are indicated below with an asterisk:

From Sisu Transaction →

To BoomTown Transaction:

STATUS (Under Contract, Closed)

Status * (UNDER CONTRACT, CLOSED)

AGENT *

Agent

TRANSACTION TYPE * (Buyer, Seller)

Representing * (Buyer, Seller)

ADDRESS LINE 1

Address *

CITY

City *

STATE

State *

POSTAL CODE

Zip

TRANSACTION AMOUNT

Price *

GCI

Gross Commission Income

GROSS AGENT(S) PAID INCOME

Agent Split

UNDER CONTRACT DATE

Acceptance Date

CLOSED (SETTLEMENT) DATE

Closing Date

This video provides a detailed walkthrough of creating BoomTown transactions from Sisu transactions and updating Sisu transactions and having those changes reflected in the BoomTown transaction:

Creating dual-sided (Buy/Sell) transactions from BoomTown and how to create BoomTown transactions from these dual side Sisu transactions

We understand that your dual-sided transactions will move through your sales cycle at a very different pace. Both Sisu and BoomTown can easily accommodate this part of your business.

For those dual-sided transactions in BoomTown, the sync will create two separate transactions in Sisu when you set the BoomTown Category change - one for the buyer side and one for the seller side.

This also accommodates the possibility that different agents may handle the buyer side and listing side since there is one transaction per side in Sisu.

If you have the "CREATE BOOMTOWN TRANSACTION WHEN: Sisu goes Under Contract" setting turned on in your configuration, we will create a distinct BoomTown transaction record for each Sisu transaction when it goes Under Contract, and we will ensure that updates to each Sisu transaction get pushed to the corresponding BoomTown transaction (i.e. pricing, GCI, the agent paid income changes and setting the BoomTown transaction status to "Closed" on Sisu CLOSED status change).

This detailed video provides a great overview:

Lead Source Mapping: Multiple BoomTown Leads Source = Single Sisu Lead Source

Sisu provides powerful lead source reporting to ensure that you are making data-driven decisions on what lead sources to allocate your marketing spend and what agents to assign for certain lead sources.

Powerful searches and filter creation from your transaction screen can include specific Lead Sources and Lead Source reports provide quick and detailed access to make decisions based on those lead sources that are originally being set from your BoomTown lead/contact records. Specifically;

Lead source decisions can only occur if proper lead sources are initially being set in BoomTown, however, BoomTown's lead source table is not readily accessible by administrators and Sisu lead sources provide extreme flexibility, modification, and addition.

To ensure that your BoomTown lead sources provide optimal alignment and reporting to Sisu, we provide the ability to map multiple BoomTown lead sources down to singular Sisu lead sources to ensure accurate reporting.

Mapping your multiple external BoomTown lead sources to singular Sisu lead sources can be managed in your Lead Mapping configuration screen (Admin > Team Settings > Lead Mapping)

This video provides a detailed overview;

Using BoomTown with Mojo and Sisu

If you are using Mojo integrated with BoomTown (not importing call lists outside of BoomTown), then the Mojo activity will update BoomTown activity (i.e. dials, contacted) which will update Sisu. Being that the Mojo user data could be independently pulled into Sisu via our direct Mojo integration, we don't recommend setting it up isolated as it would duplicate activity data. Essentially if the same Mojo user (i.e. Mojo login is the same as the BoomTown and Sisu login email) is using BoomTown and Mojo - we natively track this activity data. If that Mojo user uses Mojo outside of BoomTown (i.e. FSBO calls) then the integration would DUPLICATE the activity.

Our recommendation would be to use Mojo and BoomTown exclusively together if possible to account for Sisu account (i.e. import your FSBO's into BoomTown).

There is extreme value to start your transaction from the BoomTown lead record so that lead source data can be accurately tracked from the start.

Did this answer your question?