How Conversion works with Salesloft
Conversion connects to Salesloft to keep cadences in sync with the lifecycle stage, score, and intent data Conversion maintains for each contact. Those values sit on one record with your Salesforce, warehouse, and engagement data, and workflows respond when they change, so the cadence a contact is in keeps pace with where they actually are.
What you can do
Lifecycle transitions as triggers
A Field is changed trigger can match both the old and the new value, so a contact moving from MQL to SQL brings their cadence up to date and unrelated edits don't.
Score thresholds that hold steady
A criteria-based trigger enrolls a contact when their score crosses the line you set. With re-enrollment on, they re-enter only after the score drops below and crosses again, so small movements don't reshuffle a cadence.
Intent in the same rule
One condition can combine score and lifecycle with intent, such as three pricing page visits in two weeks or research flagged by an intent provider, so a single rule decides when the cadence should change.
