The Mixmax Real-Time Sync (MX-RTS) package for Salesforce is designed to bring all necessary updates into Mixmax in real time. This means that the package only handles traffic from Salesforce to Mixmax and not the other way around.

Customers using MX-RTS to sync data from Salesforce to Mixmax also need a Salesforce Sync User so Mixmax can connect to the correct Salesforce deployment for the Mixmax org. MX-RTS benefits customers because it doesn't use API quota for its portion of the bi-directional sync. API quota will only be used by individual users syncing their changes from Mixmax to Salesforce (i.e., updating records).

Let's dive in and see how MX-RTS works.

MX-RTS is purely Salesforce Apex-based and uses minimal Apex code, so it has a negligible impact on your Salesforce Apex code limit. The lion's share of the package is Apex triggers, with a few Apex classes that receive data from the triggers and send it to Mixmax.

MX-RTS uses triggers to identify when an Account, Contact, Event, Lead, Opportunity, Task, or User is changed. These triggers fire after the change is saved in Salesforce.

Because these triggers run in the same Salesforce transaction as your org's other automation (Flows, Apex triggers, validation rules, and other installed packages), they share the same per-transaction Apex limits, such as CPU time and SOQL queries. In orgs with a lot of automation on these objects, large bulk updates can reach those limits. If that happens, you can use Sync Conditions to limit which field changes Real-Time Sync acts on, or temporarily disable Real-Time Sync while your Salesforce admin reviews the automation. If the error message names a Mixmax class, contact Mixmax Support.

Each trigger sends the update to one of a few MX-RTS Apex classes, which then sends the information to Mixmax.

When you delete records in Salesforce, Mixmax usually picks up the deletions right away through MX-RTS. For deletions MX-RTS doesn't send, such as Contacts that Salesforce deletes along with their Account, Mixmax picks them up in a daily check within about 24 hours.

Deleting records in Salesforce doesn't delete anything in Mixmax. Mixmax contacts stay in any Sequences they're in, and their messages and engagement history are kept. To learn more, see How Mixmax syncs Contacts data with Salesforce.

The MX-RTS package uses zero of your Salesforce API quota for its applicable portion of the bi-directional sync, sending information from Salesforce to Mixmax. API quota is used only when individual users sync changes in the other direction, from Mixmax to Salesforce (i.e., updating records).