New Features:
Agentforce Prospecting Agent (available October 2025)
Demandbase has launched its first Agentforce agent within the Salesforce Agentforce ecosystem. The Demandbase Agentforce Prospecting Agent is a Salesforce-native solution that embeds Demandbase’s Prescriptive Sales Dashboard insights directly into Agentforce workflows to help sellers more efficiently and effectively engage their target customers.
Key benefits include:
- Real-Time Account Prioritization for SDRs: It surfaces the highest-potential accounts using AI, directly inside Salesforce—eliminating guesswork and tool switching.
- Execution Consistency for Managers: It ensures reps are focused on the right accounts, with shared logic and visibility into performance.
- Faster Ramp for New Reps: It gives new SDRs a guided, in-flow starting point—reducing ramp time and confusion.
Amazon S3 Cloud Data Import
We’re excited to introduce the Amazon S3 Cloud data import feature, which allows you to securely upload CSV files into Demandbase-managed Amazon S3 folders. Once files are uploaded, Demandbase will automatically ingest the data and create a data import in the Database area, labeled with the drop box name and timestamp.
Key Benefits include:
- Handle large datasets with ease: Upload CSV files up to 20 GB without splitting them into smaller chunks.
- Streamlined data management: Centralize Account, Opportunity, Person, and Activity data directly from cloud storage into Demandbase.
See Push Data to Demandbase From Amazon S3
Product Updates:
Engagement per Buying Group
We’ve made an update to the Buying Group Overview chart in Demandbase One for Marketing to make it easier to understand engagement across your buying groups.
On the Buying Group Overview heatmap, the Y-axis label now reads Total Engagement. This makes it clear that the metric reflects the overall engagement value for a specific buying group.
How Engagement is Counted
Total Engagement is calculated based on the date range selected in the Buying Group Insights dashboard. Within the window:
- Unknown activity (from Demandbase): Counted when the activity aligns with the configured Keyword Set or Page Filters for the Buying Group.
- Known person activity (first-party): Counted when the individual is designated as suggested or confirmed within the Buying Group.
This enhancement provides greater accuracy and clarity in reporting engagement activity across Buying Groups.
See Understanding Buying Group Insights.
Journey Mapping Added to Buying Groups Setup
We’ve made an update to the Buying Group setup wizard to add a 3rd step for Journeys. If you have multiple journeys, you can now select the specific journey that maps to your product, allowing you to track Buying Groups by that Journey Funnel. Once mapped, the Buying Group Insights page will have a new dropdown above the Journey Stages that lets you choose the journey mapped to that Buying Group. This allows you to better analyze your buying groups by the specific Journey Funnel of that product.
See Define and Manage Buying Groups.
Bulk Action Update
The account and people table on the Buying Groups Insights page has been updated to allow for bulk action to be taken on all the rows in the table. Once all rows have been selected, the Action Agent will be able to take action on all rows selected.
See Understanding Buying Group Insights.
Industry & Geography Fields for Buying Groups Filter Agent
We’ve enhanced the Filter Agent to understand and apply Industry and Geography filters directly from natural language queries. With this enhancement, users can now segment their buying group data more intuitively, unlocking deeper and more relevant insights to drive precise targeting, faster campaign planning, and smarter sales activation.
See Filtering with the Buying Group Filter Agent.
Ads Data in Export API
Demandbase has unified the export of advertising data—covering both Demandbase Ads and third-party platforms like LinkedIn and Google—into a single, streamlined API endpoint. With this update, customers can now access campaign and creative performance data through the standard POST /job endpoint, eliminating the need for separate /campaign/job and /creative/job calls.