Skip to content
English
Sign in
Go to goconsensus.com
  • There are no suggestions because the search field is empty.

June 2026 Consensus Release Notes

This document describes the functionality released on June 11, 2026.

Included in this Release:

  • Google Tag Manager (GTM) Integration
  • In-Demo Buyer Reactions
  • Co-Pilot Support for Consensus AI Agent Connect
  • Historical Account & Opportunity Auto-Matching for Salesforce
  • New Consensus API Endpoints
  • Salesforce Integration Improvements
  • Dynamic Tour Heatmap Metrics
  • Discovery Demo Question and Response Tracking
  • Streamlined Public Link Creation Page
  • Consensus Slack App Update

Watch the June Release Demo

Google Tag Manager (GTM) Integration

What is it?

The Google Tag Manager (GTM) Integration is a native connection that allows marketing teams to sync Consensus demo engagement data directly with their existing analytics and ad attribution infrastructure. By connecting your GTM Container ID to Consensus, the platform automatically pushes key demo events into your GTM data layer, turning your "demo blind spot" into actionable marketing intelligence.

Benefits

  • Closed-Loop Attribution: Finally tie demo views back to specific ad campaigns and marketing touchpoints to prove ROI and optimize spend.
  • Zero Engineering Required: Skip the custom code. Once the container is connected, marketers can route data through GTM to downstream tools without needing a developer.
  • Universal Compatibility: Route Consensus event data to any tool supported by GTM, including Google Analytics 4 (GA4), Google Ads, and more.
  • Granular Engagement Signals: Go beyond the "view." Track high-intent actions like lead submissions, feature rankings, and CTA clicks to build sophisticated retargeting segments.

Set up

Setting up the integration takes less than a minute for a Consensus Admin:

  1. Go to the Integrations section within the Consensus web app.
  2. Find the Google Tag Manager tile and click to configure.
  3. Click the Connect button.
  4. Enter your GTM Container ID (e.g., GTM-XXXXXXX) and click Save.

How to use

Once the connection is established, Consensus pushes events to your GTM data layer automatically. To utilize this data:

  1. In your GTM workspace, create new triggers based on Consensus custom events (e.g., consensus_demo_viewed or consensus_lead_submitted).
  2. Attach tags to these triggers to route the data to your destination of choice (like GA4).
  3. To capture metadata like demo_id or email, create Variables in GTM for each field. Then, add them as Parameters in your tag configuration.
  4. Use the demo data in your analytics platform to build audience segments, conversion goals, or attribution reports.

Frequently Asked Questions

Q: Which demo link types trigger GTM events?

A: Currently, only Public Links trigger GTM events. DemoBoard and Mail Merge link types are not included in this initial release.

Q: What specific events are pushed to GTM?

A: There are five core events supported:

  • Demo Opened: When a viewer first lands on the demo.
  • Lead Submitted: When a viewer completes a lead capture form.
  • Demo Viewed: Tracks the total duration watched.
  • Feature Rankings Selected: Captures the viewer's "Very/Somewhat/Not Important" selections.
  • CTA Clicked: When a viewer clicks an external link within the demo.

Q: Does this work with Google Analytics 4 (GA4)?

A: Yes! Once the GTM integration is configured, you simply set up a GA4 Event Tag in GTM that fires on the Consensus triggers.

Q: Why am I seeing the event in GA4 but missing specific data like Demo Title?

A: You must manually create "Data Layer Variables" in GTM for the specific metadata fields we send (e.g., demo_id, demo_title). Once those variables are created, you must add them as parameters in your Tag configuration.

Q: What metadata is available for these events?

A: Most events include the Demo ID, Demo Title, Demo URL, Host URL, and a Unique Event ID. Specific events include extra data, such as Lead Email for lead submissions or External URL for CTA clicks.

Resources

In-Demo Buyer Reactions

What is it?

Until now, automated demos have been a "black box" regarding buyer sentiment. While you could see what they watched, you couldn't know what they thought. Buyer Reactions introduces an interactive overlay for Video Demos and Dynamic Tours, allowing prospects to share qualitative feedback in real-time. Whether it's a quick emoji or a detailed question, you now have a direct line to your buyer's mindset during their async viewing experience.

Benefits

  • Capture Instant Sentiment: Move beyond basic view data. Know exactly which features land (❤️) and which cause confusion (👎) with timestamped accuracy.
  • Convert Questions into Dialogue: When a buyer clicks the Comment (💬) icon, the video automatically pauses, allowing them to type a question without missing a beat. This turns a passive recording into a consultative sales tool.
  • Visual Context for Feedback: Every reaction is tied to the exact moment and visual frame the buyer was looking at, so you never have to guess what they are referring to.
  • Zero Notification Fatigue: Instead of being pinged for every click, you receive one clean Session Summary Email after the viewer finishes, containing all reactions, comments, and timestamps.
  • Identify Content Performance: Aggregate analytics help Marketing and Sales leaders identify which demos are "fan favorites" and which ones might need a rework based on viewer feedback trends.

Set up

No setup required! Buyer Reactions is a "always-on" feature enabled for all accounts. There are no toggles to flip or engineering tickets to submit—your existing and future Video Demos and Dynamic Tours are already equipped with these capabilities.

How to use

  1. Distribute: Send your demo as usual via a DemoBoard or Public Link.
  2. Buyer Interaction: As the buyer watches, they will see the reaction bar (❤️, 💬, 👎). They can react at any specific moment or respond to the optional prompt at the end of the demo.
  3. Review the Summary: Once the session ends, check your inbox for the summary email to see a chronological list of their feedback.
  4. Analyze the Heatmap: Navigate to the Heatmap analytics page for that session to see reactions visualized across the timeline of the video.
  5. View Aggregate Data: Check the DemoBoard or Public Link details page to see total reaction counts and sentiment trends across all viewers.

Frequently Asked Questions

Q: Which demo types support Buyer Reactions?

A: This feature is currently available for Video Demos and Dynamic Tours. Standard Simulations are not supported in this release.

Q: Can buyers see reactions left by other people?

A: No. This is a private communication channel between the buyer and the seller. One viewer’s reactions are never visible to another.

Q: What happens if a buyer reacts multiple times?

A: All reactions are captured and timestamped. You will see every interaction mapped out on the session heatmap and listed in your end-of-session summary email.

Q: Do I get an email the second they click "Love it"?

A: No. To keep your inbox clean, we bundle all reactions and comments from a single viewing session into one summary email sent after the session concludes.

Q: Is the end-of-demo prompt mandatory for the buyer?

A: No. The end-of-session reaction prompt is optional and can be easily skipped by the buyer if they choose not to leave feedback.

Q: Does this cost extra?

A: No. Buyer Reactions is a core enhancement included for all Consensus customers at no additional cost.

Resources

AI Agent Connect for Copilot Studio

What is it?

Following the launch of AI Agent Connect, we are highlighting its specific integration with Microsoft Copilot Studio. This capability allows you to transform your standard Copilot agent into a specialized "Consensus Expert." By using the Model Context Protocol (MCP), your agent gains a "real-time bridge" to your demo data, enabling it to act as an intelligent sales assistant that can pull analytics, find content, and manage DemoBoards via natural language.

Benefits

  • Native Microsoft Integration: Leverage your existing Microsoft 365 ecosystem to interact with Consensus data.
  • Unified Workspace: Sellers no longer need to switch between Copilot and Consensus to find the right demo or check if a prospect has watched a video.
  • Streamlined DemoBoard Management: Effortlessly create or update DemoBoards during a chat session, significantly reducing administrative overhead.
  • Enhanced Intelligence: By grounding your Copilot agent in actual Consensus engagement data, its responses regarding sales performance and prospect intent become significantly more accurate.

Set up

To connect your existing AI Agent Connect server to Copilot Studio, use the following configuration:

  1. Deployment Type: Use the MCP onboarding wizard within Copilot Studio.
  2. Connection Details:
    • MCP Server URL: https://mcp.goconsensus.com/mcp
    • Transport: Streamable (fully compatible with Copilot Studio's requirements).
    • Authentication: OAuth 2.0.
  3. Optimization: During setup, ensure your Server Description clearly states that this tool handles "searching demos, checking engagement analytics, and creating/updating demoboards." This helps the Copilot orchestrator route queries correctly.

How to use

Ask Copilot to help you find demos or create DemoBoards. For example: "Find demos about product analytics" or "Create a DemoBoard for a healthcare prospect interested in data security."

Frequently Asked Questions

Q: Do we need a Copilot Studio license?

A: Building a custom agent requires a Copilot Studio license. However, as of April 2026, Microsoft also supports deploying MCP connectors organization-wide via the Microsoft 365 admin center, which may bypass the need for individual Studio licenses. Check with your IT admin.

Q: Why does the AI sometimes fail to find the right demo?

A: This is usually a model behavior issue. For the best results, we recommend using a Claude-based model within your agent. If using a GPT model, try to be more specific with your parameters (e.g., provide the exact account name or date range).

Q: Can Copilot see my entire Consensus account?

A: No. Copilot only sees the data it specifically requests to answer your query. Furthermore, the connection is scoped to your individual permissions—Copilot cannot access data that you wouldn't be able to see yourself in the Consensus web app.

Q: Is this compatible with the standard Microsoft 365 Copilot?

A: Yes, once the connector is published as a plugin or deployed through the admin center, it can be made available to users within the standard Microsoft 365 Copilot interface.

Resources

Historical Account & Opportunity Auto-Matching for Salesforce

What is it?

The Historical Account & Opportunity Auto-Matching for Salesforce release provides effortless attribution by automatically linking historical DemoBoards to the correct Salesforce records, ensuring accurate ROI reporting and cleaner CRM data without requiring manual effort from sales reps.

Benefits

  • Effortless Attribution: Increase your attribution coverage without requiring sales reps to circle back and manually update old DemoBoards.
  • Accurate ROI Reporting: Give Sales and RevOps leaders a true picture of how Consensus influences revenue by capturing associations that were previously missed.
  • Cleaner Salesforce Data: Reduce the need for manual data entry and backfilling, ensuring your CRM remains the "single source of truth" with minimal effort.
  • Stronger Strategic Insights: Quantify Consensus’s role in deals during QBRs and renewal conversations with data that accurately reflects your team's activity.

Set up

This feature is available for Salesforce customers using the Consensus managed package. A Consensus Admin can enable it in two clicks:

  1. Navigate to the Integrations section in the Consensus web app.
  2. Select the Salesforce tile.
  3. Locate the "Enable auto-matching" toggle and turn it ON.

How to use

No user action required. Once the Admin enables the toggle, the system takes over.

  • A daily job automatically scans DemoBoards created within the last week that are missing Opportunity data.
  • If a match is found in Salesforce, the DemoBoard is updated automatically.
  • The process runs in the background, allowing reps to focus on selling while the system handles the documentation.

Frequently Asked Questions

Q: Which CRMs are supported?

A: This phase of the rollout is scoped specifically for Salesforce. Other CRM integrations are currently out of scope.

Q: How often does the auto-matching run?

A: The job runs daily. It specifically looks for DemoBoards created within the last seven days that are missing an Opportunity value.

Q: Will this overwrite manual changes made by a rep?

A: No. The sync sequence is designed to respect manual updates. If a rep manually assigns an Account or Opportunity in Salesforce, Consensus will sync that data and ensure we do not overwrite their manual work.

Q: Does this update DemoBoards that already have an Opportunity assigned?

A: No. To ensure data integrity, the job only targets DemoBoards that are currently missing these values.

Q: Can I turn this feature off?

A: Yes. If you prefer to manage associations manually, you can disable the "Enable auto-matching" toggle within the Salesforce integration settings at any time.

New Consensus API Endpoints

What is it?

Consensus launched the initial phase of the V2 API, featuring a more secure authentication framework based on OAuth 2.0. This update provides developers with more granular control and deeper data access, starting with two core endpoints: the Views API, which retrieves real-time engagement analytics and Discovery Demo responses searchable by view time, and the Demo Search API, which allows for programmatic library filtering by tags, favorites, and promoted status.

These endpoints enable teams to sync individual viewer insights directly into internal tools and retrieve detailed usage statistics, including last-updated timestamps and demo metadata. For full technical specifications and authentication details, visit the Public Documentation Portal.

Salesforce Integration Improvements

What is it?

This update streamlines how Consensus data flows through Salesforce, ensuring that demo engagement remains visible and actionable as deals progress through the pipeline. By automating the link between Lead-stage activity and newly converted Opportunities, RevOps teams can now maintain a continuous line of attribution from the first demo view to closed-won revenue. Additionally, we’ve introduced more granular tracking and UI flexibility to give your sales team the exact context they need directly within their CRM environment.

Key Enhancements:

  • Lead-to-Opportunity Mapping: Consensus DemoBoard and View data are now automatically linked to the converted Opportunity, preserving early stage engagement that was previously lost during the conversion process. Additionally, the converted Opportunity is related to the Invitation in a new 'Converted Opportunity' field for easier reporting.
  • Customizable Component Tables: You can now tailor the Consensus component table in Salesforce by adding custom fields from DemoBoard or Invitation objects. By using formula fields, you can even surface related Account and Opportunity data, such as "Product" or "Deal Size," directly within the component.
  • Initial Opportunity Stage Capture: A new Initial Opportunity Stage field records the specific stage of a deal at the exact moment a DemoBoard is created. This value remains locked even as the deal progresses, allowing leadership to analyze the conversion impact of demos sent during different phases of the sales cycle (e.g., Discovery vs. Proposal).

Dynamic Tour Heatmap Metrics

What is it?

We have expanded the engagement metrics captured for Dynamic and HTML Tours to provide a deeper understanding of how buyers interact with the content. Both the DemoBoard and Qualified Lead Heatmap pages now display specific session data, including the total Duration spent within the tour and the number of Tour Steps Completed. To simplify review, a new "View Tour" link allows you to open the exact path taken by the customer directly within a modal.

For sessions involving multiple assets, new Aggregate Total Cards have been added to the top of the analytics pages. These cards provide a high-level summary of the entire engagement, including total video duration, total tour views, combined tour duration, and cumulative tour steps completed across all assets in the session.

Discovery Demo Question and Response Tracking

What is it?

Consensus has enhanced Discovery Demo reporting to provide deeper visibility into prospect needs at both the account and individual levels. The DemoBoard Detail page now features a comprehensive aggregate Q&A section, which compiles all questions and answers across every recipient of a DemoBoard to reveal broader buyer trends. Additionally, the Heatmap summary for DemoBoards and Qualified Leads now includes a dedicated Questions and Responses section, displaying the specific discovery answers provided during an individual session to help sellers better understand a prospect's unique pain points.



Streamlined Public Link Creation Page

The Create Public Link page has been redesigned to align with the streamlined, two-column experience used in DemoBoard creation. This updated layout eliminates the learning curve between workflows and provides a side-by-side view of demo selection and link settings, significantly reducing the need for scrolling.

The new demo browser improves discovery by displaying creator names and creation dates at a glance. Users can now utilize familiar search, filters, and tabs—such as Favorites, Recents, and Promoted—to find content without navigating away. Additionally, the ability to preview demos directly from the selector ensures the correct content is chosen without the need to switch tabs or windows.


Consensus Slack App Update

We have made key compliance and security updates to our Slack application to meet the official requirements for the Slack Marketplace. By aligning with Slack’s developer guidelines, specifically optimizing our user permission scopes and direct messaging architecture, we are completing the necessary steps to secure official listing approval.

Current users of the Consensus Slack App will need to reauthenticate their connection.