In many mid-market and enterprise orgs, Salesforce is the center of gravity with no third-party marketing automation platform in front of it — sometimes Salesforce alone, often paired with Pardot (now Marketing Cloud Account Engagement), Salesforce's own B2B marketing automation tool built natively into the platform.
Breakout integrates directly with this stack: it captures buying signals on your site, writes lead data into Pardot so scoring and nurture keep running, and logs the rich context of every conversation — summaries, transcripts, sales follow-ups — natively onto the Salesforce Lead and Contact objects. Marketing automation stays fed, sales gets full visibility, and Breakout never becomes a disconnected system to reconcile.
How Breakout divides work between Pardot and Salesforce
Breakout captures lead attribute data plus discrete behavioral events — a hand raise, a booked meeting. Pardot has a mechanism for ingesting third-party behavioral events (External Activities), and Breakout supports writing to it, but most Salesforce-plus-Pardot teams prefer a cleaner split: Pardot owns the lead record and nurture logic, Salesforce owns event history and rep workflow.
So instead of streaming activity events into Pardot, Breakout writes lead data into Pardot and creates Activities and Tasks directly on the Salesforce Lead or Contact — carrying chat summaries, transcript links, and any follow-up a rep needs to take. That's what most customers on this stack actually want, and it keeps each system doing what it does best.
Architecture: a hybrid sync model
Breakout combines real-time event triggers with scheduled batch processing. Event-driven sync handles lead data and high-intent signals — the moment a visitor hits a milestone, Breakout writes it so Pardot scoring/automation and Salesforce routing can act without lag. Batch processing handles bulk, non-time-critical operations: syncing full chat transcripts into Salesforce, and, for customers who need it, mapping aggregate account deanonymization data into Salesforce or Pardot.
Setup and authentication
Breakout connects over secure, OAuth-based APIs, with no field-mapping UI for your team to configure — Breakout's integration specialists handle setup. For Salesforce, it uses a dedicated Integration User profile authorized via OAuth; passwords are never seen or stored. For Pardot, it authenticates through the Pardot API (v5) via an OAuth connection tied to your business unit, and writes prospect data through that connection.
The read integration: real-time intelligence
Breakout performs instant lookups to Salesforce to understand who a visitor is — the read access behind routing chats and meetings to the right rep, and feeding BDR signals. This part is identical whether or not Pardot is in the stack.
For account identification, it uses reverse-IP to identify visiting accounts and read their Salesforce attributes, alerting reps when their accounts are on-site and prioritizing Tier 1 accounts for live chat. For lead identity, once an email is identified Breakout queries Salesforce for an existing Lead or Contact and pulls the OwnerID to personalize the experience.
The write integration: Pardot for lead data, Salesforce for context
Breakout writes signals into both systems with a clear division of labor. Lead data goes to Pardot — Breakout creates and updates the prospect record via the Pardot API, feeding the scoring, lists, segmentation, and nurture your marketing team already runs (an Engagement Studio program, for example, watching for a field Breakout sets to flag high intent).
Conversation context and rep actions go to Salesforce. For each meaningful conversation, Breakout logs a Salesforce Activity on the Lead or Contact with the chat summary and a link to the full log, so complete history stays attached to the record the rep already works from. A Salesforce Task is created only when a conversation actually warrants follow-up, so reps aren't flooded with a task for every interaction.
Breakout also supports writing External Activities into Pardot for teams that want conversation events feeding Pardot's own automation directly — but most Salesforce-plus-Pardot customers prefer the Salesforce-native approach, since it gives sales richer context than Pardot's external-activity model is built to carry.
Native calendar: meeting-booked signals
Breakout's native calendar lets visitors book meetings directly in the conversation. When a meeting is booked, Breakout captures the assigned rep and writes it through: the prospect record updates in Pardot, and Breakout creates a Salesforce Activity on the Lead or Contact plus an optional Task where follow-up is needed — so the meeting and its ownership land on the record the rep works from, not just in a calendar tool.
How data flows: three lead-capture scenarios
Level 1 – explicit hand raise: the visitor requests a demo, routes to sales, or books a meeting. Breakout updates the Pardot prospect record to reflect the high-intent signal and logs a Salesforce Activity with the conversation summary and chat-log link; for a booked meeting, that Activity records the assigned rep and Breakout creates a Task for them. Pardot automation can enroll the lead in a fast-track program off the updated field, while the rep sees full context and their follow-up directly in Salesforce.
Level 2 – implicit lead capture: the visitor shares an email during a chat or resource download, but intent is softer. Breakout updates the Pardot prospect record and logs a Salesforce Activity with the summary and chat-log link — no Task unless the interaction calls for rep action. Pardot accumulates the behavior into scoring or nurture based on the updated record.
Level 3 – conversation with no lead capture: the visitor chats without submitting identifying information. If they're already resolved to an existing Salesforce Lead or Contact, Breakout logs a Salesforce Activity so the conversation is captured, without creating a new lead or a Task unless follow-up is needed. If anonymous, Breakout holds the engagement internally under the deferred write pattern — nothing is written until the visitor identifies themselves, at which point full history is written retroactively.
When Salesforce is the center of the stack, Breakout divides the work along its natural seam: lead data flows into Pardot to keep scoring and nurture running, while conversation context and rep actions are written natively onto the Salesforce Lead and Contact objects where sales already works. Conversation summaries and transcript links are always logged as Activities; Tasks are created only when a rep needs to act; meetings booked through Breakout's calendar carry their rep assignment through to both systems; and anonymous visitors are handled through a deferred write pattern that holds data until they identify themselves — richer, higher-intent signal for your existing automation, without new manual workflows.
