KEY TAKEAWAYS
- Interactive demo engagement data flows directly into Salesforce and HubSpot opportunity records.
- Walnut’s Insights AI pushes section-level, stakeholder-level data into the CRM automatically.
- Reps see which sections buyers engaged with before making their follow-up call.
- Demo engagement signals improve forecast accuracy at the pipeline level.
- The difference between a view-level and intent-level CRM integration changes deal outcomes.
- Setting up the integration takes minutes. No third-party connector required.
Your CRM knows a demo happened. It has almost no idea what it meant.
Most demo tools log a view. The prospect opened the link, the CRM records it, and the rep moves on with the same follow-up they would have sent regardless. The richest signal in the funnel is what the buyer actually looked at, where they spent time, what they shared internally, and when they came back. This disappears the moment the browser tab closes.
The gap between what a demo generates and what a CRM captures is where pipeline quality problems originate. A rep who knows that a buyer spent 14 minutes on the pricing section and forwarded the demo to 3 new stakeholders follows up very differently than a rep who only knows the demo was opened. That difference compounds across every deal in the pipeline.
This post covers how interactive demos integrate with CRM systems, what data actually flows in, and what that means for how reps follow up and how revenue leaders forecast.
How Do Interactive Demos Integrate With CRM Systems?
The integration between an interactive demo platform and a CRM works in one of 2 ways, and the difference matters significantly.
View-level integration logs that a demo was opened. The CRM records a demo event on the contact or lead record — timestamp, demo name, sometimes a completion flag. This is useful for tracking that outreach is being consumed. It tells you almost nothing about buyer intent.
Intent-level integration pushes behavioral data from the demo session directly into the CRM opportunity record. Which sections did the buyer view and for how long? Did they return to a specific part of the demo? Did they share the link with new stakeholders? Did they ask questions in a deal room conversation? All of this appears on the deal record, automatically, without the rep having to log anything.
Walnut’s integration with Salesforce and HubSpot is intent-level. Insights AI captures engagement data at the session level and pushes it into the CRM opportunity record in real time. The rep opens the deal in Salesforce and sees the demo engagement alongside every other activity on the opportunity. No separate dashboard. No manual sync. No data that lives outside the workflow the rep already uses.
What Data Flows From an Interactive Demo Into the CRM?
The specific data that flows into the CRM from a Walnut demo session includes:
Section engagement depth. Which screens or sections of the demo did the buyer spend time on, and how long did they spend on each one? A buyer who lingered on the security architecture section for 8 minutes is signaling something specific about their evaluation criteria. That signal appears on the deal record.
Stakeholder spread. Did the original recipient share the demo with additional stakeholders? Walnut captures internal sharing events — when a new viewer opens the demo from a forwarded link — and surfaces those as engagement signals on the opportunity. A deal where 5 stakeholders have engaged with the demo is in a different place than a deal where only 1 person has opened it.
Return visits. Did the buyer come back to the demo after their first session? A second session before a scheduled call is a strong intent signal. Walnut logs return visits with timestamp and session detail so the pattern is visible in the CRM.
Deal room activity. For deals where the demo lives inside a Walnut Interactive Deal Room, engagement with the room’s content, including documents, the Mutual Action Plan, and conversation threads, also surfaces in the CRM alongside the demo engagement data.
Session timeline. A structured timeline of demo activity for each session, showing which events happened in what order, appears on the opportunity record through Insights AI. The rep can read the buyer’s session the way they would read a call transcript.
For more on the specific metrics worth tracking from demo engagement data, see the guide to why your demo metrics are wrong.
How Does Demo CRM Integration Work in Salesforce?
In Salesforce, Walnut’s Insights AI integration pushes demo session data into the opportunity record as activity events. The rep sees demo engagement in the same activity feed where they see email opens, call logs, and meeting notes.
The data appears at the opportunity level, not just the contact level. This is the distinction that makes it useful for deal management. A contact-level integration tells you that a specific person opened a demo. An opportunity-level integration tells you what is happening across the entire buying committee for a specific deal.
For revenue operations teams, the integration also enables reporting. Demo engagement becomes a field that can be queried in Salesforce reports: which deals have multi-stakeholder demo engagement, how does demo engagement depth correlate with closed-won rate, which stage in the pipeline shows the highest demo re-engagement rate. These are the pipeline intelligence questions that most teams cannot currently answer because demo data lives outside the CRM.
For more on how digital sales rooms extend this intelligence across the full post-demo buying journey, see the guide to how enterprise teams use digital sales rooms to close faster.
How Does Demo CRM Integration Work in HubSpot?
In HubSpot, Walnut’s Insights AI integration pushes demo session data into the deal record as timeline events and properties. The deal view shows demo engagement in the activity timeline alongside emails, calls, and meetings.
HubSpot’s deal properties can be updated with demo engagement data — including a most-recent demo engagement date, a stakeholder count from the demo sessions, and engagement depth indicators — which enables list segmentation and workflow automation based on demo behavior.
For example: a workflow that triggers a follow-up task for the deal owner when 3 or more stakeholders engage with a demo in a 48-hour window. Or a sequence that sends a specific email when a buyer returns to a demo they already viewed. Demo engagement becomes a trigger condition in HubSpot, not just a data point to review manually.
The native integration requires no third-party connector. It activates from Walnut’s integration settings and begins pushing data to the connected HubSpot portal immediately.
What Reps Do Differently When Demo Data Is in the CRM
The practical impact of intent-level demo CRM integration shows up most clearly in how reps prepare for follow-up calls.
A rep preparing for a follow-up with view-level data has: the demo was opened 3 days ago. They send a generic follow-up email and prepare a standard agenda.
A rep preparing for a follow-up with intent-level data has: the buyer opened the demo on Tuesday, spent 11 minutes on the integration section, 4 minutes on the pricing overview, skipped the onboarding flow entirely, and shared the demo with 2 new email addresses on Wednesday. On Thursday they opened it again for 6 minutes and spent most of that time back on integrations.
The second rep’s follow-up email references integrations specifically. Their call agenda leads with the integration question rather than a generic “any questions from the demo?” The new stakeholders who received the forwarded link get a personalized outreach. The rep asks whether the team has reviewed the pricing section with the wider group.
That is not a marginal improvement. It is a fundamentally different sales motion, made possible by data that already exists inside the demo platform and previously had no route into the workflow where reps actually operate.
For more on how interactive demo conversion rates change when reps follow up with engagement context, see the 2026 benchmarking data.
How Demo Engagement Data Improves Forecast Accuracy
At the revenue leadership level, demo CRM integration changes how pipeline is assessed.
Deals with high demo engagement from multiple stakeholders close at measurably higher rates than deals where the demo was viewed once. When that engagement data is visible in the CRM, revenue leaders can distinguish between deals where the buying committee is genuinely active and deals where only the champion has engaged.
This matters most at the late stages of the pipeline. A deal marked as close-probable because “the champion said they’re interested” looks different when the CRM shows that only 1 of the 12 buying committee members has ever engaged with a demo. A deal at the same stage where 8 stakeholders have engaged, 3 have returned for second sessions, and the Mutual Action Plan shows completed tasks looks much more like a close.
Insights AI surfaces this engagement picture at the deal level and in aggregate across the pipeline. The result is a forecast built on what buyers have actually done, not what they said they would do on the last call.
For more on how AI is changing the broader sales intelligence workflow, see the complete guide to AI in sales.
Setting Up the Walnut CRM Integration
Connecting Walnut to Salesforce or HubSpot is configured from Walnut’s integration settings. The setup requires admin access in both Walnut and the connected CRM.
Once connected, Insights AI begins pushing demo session data to CRM records automatically. No webhook configuration, no third-party connector, no manual field mapping. The integration is native to the Walnut platform.
For specific configuration steps, field mapping options, and troubleshooting guidance, the Walnut help center at help.walnut.io is the primary reference. The CRM integration documentation covers both Salesforce and HubSpot setup in detail.
Frequently Asked Questions About Interactive Demo CRM Integration
How do interactive demos integrate with CRM systems?
Interactive demo platforms integrate with CRM systems by pushing demo session engagement data into the CRM deal or opportunity record. The quality of the integration depends on whether it logs a view (basic) or pushes behavioral data — which sections were viewed, how long, whether new stakeholders joined, whether the buyer returned (intent-level). Walnut’s Insights AI integration with Salesforce and HubSpot is intent-level, pushing session-level engagement data to opportunity records automatically.
Does Walnut integrate natively with Salesforce and HubSpot?
Yes. Walnut’s integration with both Salesforce and HubSpot is native and requires no third-party connector. It is configured from Walnut’s integration settings and begins pushing demo session data to connected CRM records immediately after setup.
What data from a demo session appears in the CRM?
Section engagement depth (which parts of the demo the buyer viewed and for how long), stakeholder spread (whether the demo was shared with new viewers), return visits (whether the buyer came back for a second session), deal room activity (engagement with documents and conversations in an Interactive Deal Room), and a structured session timeline showing the sequence of events. All of this appears on the opportunity record through Insights AI.
How does demo engagement data help with forecasting?
Deals with multi-stakeholder demo engagement close at higher rates than deals where only one person has viewed the demo. When engagement data is visible in the CRM, revenue leaders can distinguish between deals with active buying committees and deals where only the champion is engaged. This makes late-stage forecasting more accurate because it is based on what buyers have actually done rather than self-reported status from the rep.
Can I trigger HubSpot workflows based on demo engagement?
Yes. With Walnut’s HubSpot integration, demo engagement properties can be used as trigger conditions for workflows. Examples include: a follow-up task triggered when 3 or more stakeholders engage with a demo, or an email sequence triggered when a buyer returns to a demo they already viewed.
What is the difference between a view-level and intent-level CRM integration?
A view-level integration logs that a demo was opened. An intent-level integration pushes behavioral data from the session — section engagement, time spent, sharing events, return visits — into the CRM deal record. The difference determines whether demo data informs how a rep follows up or simply records that a demo was consumed.
How does demo CRM integration affect rep follow-up?
Reps with intent-level demo data in their CRM can tailor their follow-up to what the buyer specifically engaged with. A rep who knows the buyer spent 11 minutes on the integration section and shared the demo with 2 new stakeholders follows up very differently than a rep who only knows the demo was opened. The personalization is driven by the buyer’s actual behavior, not a guess.
The demo already captures the intent. The question is whether that intent reaches the rep before they make their next move.
Ready to connect your demos to your CRM? Get started with Walnut.
