Revenue Marketing
RevvyAI updates
We are improving the RevvyAI experience! Here are some recent changes:
RevvyAI is now your companion and opens on any page in Revenue Marketing and suggests prompts based on the page you’re on.
RevvyAI remembers your user preferences, such as your Predictive product category.
For Predictive users, improved “explainability” using the new explainable scores feature.
Refer to Explainable Scores.New, more in-depth predefined prompts.
RevvyAI sources answers from our 6sense Knowledge Base, therefore it replaces the Help button. Ask RevvyAI all your 6sense technical questions!
The link to open RevvyAI moved from the left navigation bar to the top right of the page.
RevvyAI opens as a panel on the right side of the page.
Value: Improved user experience, access to better explanations about Predictive models, and more in-depth answers when using RevvyAI.
KB article: RevvyAI in Revenue Marketing
Google Data Partner API migration for segment syncs
Segment Sync now supports Google's Data Manager API so Google audience syncs continue ahead of the Customer Match sunset. An in-app migration and Google account reconnect guide helps move from the existing integration. The new integration matches the current experience, and legacy and new integrations can run in parallel during transition. Audience syncs continue without interruption.
Value:
Keep syncing 6sense audiences to Google with minimal disruption during the transition.
Stay ready for Google's API transition before the Customer Match sunset.
Move at your own pace, with the legacy and new integrations running side by side.
February 17, 2027 Deadline
Any ad accounts still Pending by the deadline will be disconnected. All active syncs on those accounts will be turned off, and you will no longer be able to sync segments to them. To resume, a Google admin will need to reconnect the account.
KB articles:
DV360 support for segment syncs
You can now connect your DV360 account directly and sync 6sense segments to it as part of the new Google integration framework. DV360 access is included in the Google migration experience within Segment Sync. As part of this change, Google Ads is now named Google across the 6sense platform to reflect the broader integration. You can combine DV360 activation with 6sense tracking pixels to measure campaign impact and outcomes.
Value:
Activate 6sense segments directly in DV360 without a separate workaround.
Close the ABM reporting loop by pairing DV360 syncs with 6sense tracking pixels.
Manage Google ecosystem activation under one consistent Google integration.
KB articles:
Technology sub-category mapping added to segment filters
Segments now include Technology Category and Sub-Category filters in addition to the existing Technology Name filter. They use the same Core Data technographics hierarchy as Sales Intelligence, keeping both experiences consistent. When building a segment, you can target category, sub-category, or individual technology. The Technology Name filter remains unchanged and compatible with the new filters.
Value:
Create more precise, flexible technology-based segments.
Discover relevant technologies faster through the category hierarchy.
Use the same technology filters in Segments and Sales Intelligence.
Campaign and campaign folder filters in reports
Marketers and Ads users can now filter five additional reports by Campaign and Campaign Folder:
Website Visits
Keyword Performance
Buying Stage Movement
Buying Stage Progression
6QA Analytics
This update filters report data to accounts reached by the selected ad campaign or campaigns within a folder, extending the proven filtering logic already available in the Opportunity Trends, 6QA Trends, and Keywords Volume reports. Teams can now evaluate how specific ad investments influence account engagement, keyword resonance, funnel velocity, and pipeline creation without manual data exports or spreadsheet stitching.
Value:
Ties advertising to full-funnel outcomes: Connect ad campaigns and campaign folders directly to downstream account engagement, buying stage progression, and 6QA creation.
Flexible campaign structure slicing: Easily isolate individual campaign performance or aggregate impact across broader campaign folder initiatives to support campaign optimization and executive reporting.
Eliminates manual analysis: Removes the need to export and manually cross-reference advertising reach against account activity and progression reports.
KB article:
Advertising: AI dynamic bidding in campaigns (Open Beta)
We have added a Dynamic Bidding toggle to the budget section of campaign creation. Dynamic Bidding automatically adjusts bids so you pay closer to the actual market price for each impression.
Value:
Serve more impressions and reach more target accounts with the same budget.
No manual bid tuning required.
KB articles:
Intelligent Workflows
Unified Workflows: combined node library for Audience and Data Workflows
We’ve begun unifying Audience Workflows and Data Workflows into a single canvas, the first step toward a unified Intelligent Workflows experience. Workflows that start from a Segment, Tracked Signal, SI List, or SI Filter now share a combined node library, whichever app you build in.
In Audience Workflows, you can now enrich contacts and leads to fill buying-committee gaps alongside your campaigns. In Data Workflows, you can act on records as soon as you enrich or acquire them. Push accounts to LinkedIn, Meta, Google Ads, 6sense Display, and Salesforce Campaigns, and push people to MAP lists, CRM campaigns, sales engagement cadences, and AI Email. Remove Audience and Conditional Timer nodes add more branching options.
The redesigned workflow list lets you filter by starting node or by the actions in each workflow, and the audit log now tracks the new nodes. Your existing workflows stay where they are and keep running as they do today. The nodes and channels you see depend on your entitlements and enabled integrations.
Value:
Build more of the journey in one workflow instead of splitting work between Audience Workflows and Data Workflows.
Qualify accounts and reach them across channels from one place, or enrich records and send them straight to a campaign or sales cadence.
Find and manage workflows faster with filters for starting node and workflow actions.
KB article:
Ad channels: the Trade Desk, CTV, and contextual nodes
Audience Workflows and Data Workflows now include action nodes for The Trade Desk segment syncs, Connected TV (CTV) campaigns, and contextual campaigns. They work like the Push to LinkedIn and Push to Google Ads nodes and appear on the canvas with the other ad nodes. The Trade Desk node lets you set segment aliases, advertiser connection, sync controls, and batching and frequency, and it removes accounts that no longer meet entry criteria.
Value:
Run all your advertising through workflows instead of splitting it between orchestrated and manual channels.
Manage every supported ad channel from one place with a single, consistent workflow.
Keep every channel synced to your account intelligence as accounts enter or leave audiences.
KB article:
Gong Engage node: assign tasks by record owner
The Gong Engage node now lets you set the Assignee to the Person record owner, so each task goes to the rep who owns the record. This matches the assignee options already available on the Outreach and SalesLoft nodes. Previously, the node offered only Default Gong User or Specific Gong User, so teams needed a separate branch for each rep.
Value:
Use one Gong Engage node for your whole team instead of one branch per rep.
Have each task go to the rep who owns the record.
Skip workflow edits when reps or territories change.
KB article: People-Level Channel Action Nodes
Workflow preview: run a preview on a single node or branch
You can now run a preview on a specific node in a single branch instead of previewing the whole workflow. The preview returns counts up to the selected node and reflects the upstream logic that leads to it. Previously, you had to run a full preview to see counts for the node you were configuring.
Value:
Confirm your criteria are accurate right after a change, without waiting on a full end-to-end preview.
Iterate faster by processing only the part of the workflow you’re building.
Validate as you build rather than only before launch.
KB article: Workflows Timer Node
Workflow preview: evaluate through timer nodes
Workflow preview can now optionally evaluate through timer and wait nodes, so you can see counts for everything downstream. By default, preview still stops at timers. When you choose to evaluate through them, timer-only nodes are treated as elapsed, and timers with conditions work like decision nodes, evaluated against their conditions when the preview runs. The preview tells you timers were treated as elapsed, since counts may differ once the real wait plays out.
Value:
See downstream counts for workflows that include timers, instead of an empty preview after the timer.
Check how your logic performs end to end before you launch.
KB article: Workflows Timer Node
Push Salesforce accounts into a campaign: now supported in triggered workflows
The Push Salesforce Accounts into a Campaign node is now supported in triggered workflows. Previously, this node wasn’t available in triggered workflows. Now, accounts that enter a triggered workflow can be sent to a Salesforce campaign, just like in other workflows that support the node.
Value:
Use the Push Salesforce Accounts into a Campaign node in triggered workflows.
Keep Salesforce campaigns up to date as accounts meet your triggered workflow criteria.
Manage account-based campaign activity in one workflow instead of handling it separately.
KB article: Account-level Channel Action Nodes
Support for verified data field for export
Verified Data is now a signal in Workflows, letting you filter audiences, branch decisions, and control exports by a contact’s verification status (Yes/No). It's supported in decision nodes, purchase contact filtering, CRM, SEP, MAP, and CSV exports, and can be mapped in UMP field mapping. This uses your existing workflow nodes and export settings—no new setup needed. Previously, workflows couldn't use verification status when activating contacts.
Value:
Send only high-confidence contacts to your CRM, SEP, and outreach tools.
Branch workflows by verification status so contacts follow the correct path.
Keep low-quality data out of automated pipelines to protect downstream quality.
KB article: Data Workflows Purchase Contacts and Save to CRM or CSV Nodes
Workflow run notifications
6sense now provides additional notifications for Audience and Data Workflows. These notifications keep you informed about workflow results and help you respond quickly when an issue occurs.
Value:
Receive updates when a workflow run completes successfully.
Get notified when a workflow run fails or needs attention.
Understand the result without manually checking the workflow.
Navigate directly to the relevant workflow from the notification to investigate and resolve issues.
KB articles:
AI Email
AI Email: classification engine v2
AI Email now uses an improved intent classification model to read inbound lead replies and decide whether to send an automated response or send the reply to a person. This updates the existing AI Email reply handling and requires no setup. The new model confidently handles more replies with fewer manual reviews while maintaining high accuracy for automated replies. Reply timing and engagement status updates that depend on this decision should be more consistent.
Value:
Get faster responses to inbound lead replies because fewer replies wait for manual review.
Trust that automated responses are sent only when the reply intent is clear.
Rely on more consistent engagement status updates for any automation tied to reply status.
Open pixel tracking controls
AI Email now has a couple of controls for tracking open pixels, which enables them to comply with privacy compliance of France and Italy more effectively. Admins can set an instance wide default for whether to track email opens or not, and campaign builders can override it on any campaign before launch depending upon the audience location of those campaigns.
Value:
Customers no longer need to pause campaigns to these countries.
Customers can choose instance-wide default to be No, so as to avoid tracking by mistake while creating new campaigns.
KB articles:
Sales Intelligence
Technology sub-category mapping added to SI filters
Sales Intelligence now adds Technology Category and Sub-Category filters alongside the existing Technology Name filter. These use the same technographics hierarchy from 6sense Core Data and appear in Sales Intelligence. You can target technologies by category, sub-category, or individual name instead of selecting each technology one by one. The Technology Name filter still works as before.
Value:
Build more precise technology-based audiences at the category, sub-category, or technology level.
Save time by no longer selecting individual technologies one by one.
Get a consistent technographics experience across 6sense.
Additional Salesforce matching on the Chrome extension
The 6sense Chrome Extension now matches companies and contacts on Salesforce pages using more than the CRM ID. It reads additional Salesforce fields—company domain, company name, and contact name—and combines them with existing UDF matching. This aligns Salesforce matching with other extension surfaces so more companies and contacts show 6sense insights.
Value:
See 6sense insights for more of your Salesforce companies and contacts.
Spend less time searching manually when a record is not matched.
Trust more consistent matching across Chrome Extension experiences.
Predictive
New Model center (Open Beta)
The Model center is a new option on the left navigation bar for Predictive users. It lists top predictors and focus areas, and an account list for each supported model. This release supports the 6QA, company profile fit and company buying stage models, using the new explainable scores feature.
Models explained in this release:
6QA: Why the account is or is not qualified under your organization's 6QA rule.
Company (account) profile fit: How closely the account matches the accounts your organization has won.
Company buying stage: What research activity put the account in the buying stage.
Value: A new, improved way to understand and manage 6sense Predictive models.
KB article: Model Center Overview
Explainable scores in RevvyAI, ABM, SI, Chrome Extension, MCP, and Model center (Open Beta)
The Open Beta explainable scores feature, also called “explainability”, helps you understand why an account has its current 6QA status, company (account) profile fit and buying stage. It shows the main drivers in business language and with short written summary. You can ask follow-up questions to dig deeper.
For an overview of the new feature and where it is available in 6sense, refer to Explainable Scores.
RevvyAI explainability
In RevvyAI you can now ask questions such as:
Why accounts are designated as 6QA accounts.
How the profile fit model matches the accounts your organization has won.
What activity caused the buying stage model to move an account into its buying stage.
ABM and SI score details
In Revenue Marketing and in Sales Intelligence account pages, a Score details link opens a panel titled either “Why is [account] a qualified account?” or "Why is [account] not a qualified account?".
In the SI Chrome Extension, a new Score details link in the account page header opens a similar panel.
MCP
Just like in RevvyAI for Revenue Marketing, you can get score explanations in your own AI tools using our 6sense MCP.
Model center
The new Model center supports the 6QA, company profile fit and buying stage models, using the new explainable scores feature.
KB articles:
Platform Enablement
Data Taxonomy onboarding improvements
We’re enhancing the 6sense AI-Driven Taxonomy (AIDT) experience to improve website URL classification accuracy and coverage.
These improvements deliver more accurate mappings, automate classifications where possible, and provide smarter suggestions for customer review. Customers can also enable Taxonomy AI in AI Settings to benefit from additional AI-powered mapping, helping more URLs get intelligently classified with less manual effort.
Value:
Better mapping coverage: More website URLs accurately classified, reducing gaps and improving taxonomy completeness.
Higher-quality intent signals: More accurate classifications deliver richer, more reliable intent insights.
Less manual effort: AI-powered mapping automates more classifications, reducing the need for manual review while giving customers control when needed.
KB article: Data Taxonomy
Server-side Company Identification API
The Server-side Company Identification API maps IPv4 and IPv6 addresses to 6sense company profiles and returns firmographic data plus match details. It brings client-side identification to backend systems so data pipelines, integrations, and AI workflows can identify accounts without a browser. The API supports real-time and batch requests and uses token-scoped authentication to separate client- and server-side use. It's available via the 6sense API framework.
Value:
Identify accounts from server-side traffic, including IPv6, to improve CRM sync quality and account scoring.
See how each match was resolved so you can validate confidence.
Improve attribution and analytics accuracy by reducing data lost from anonymous traffic.
KB article: Server-side Company Identification API
Keyword Intent Data API
The Keyword Intent Data API gives you secure, programmatic access to 6sense keyword intent data. You can pull intent signals directly into your own systems for automated workflows, analytics, and machine learning. This is a new API, so it replaces the slow manual exports and limited integrations that were previously the main way to move intent data out of 6sense. Usage is metered through the unified data credits framework.
Value:
Bring intent signals into your own data pipelines without manual exports.
Power analytics, scoring, and machine learning with raw intent signals.
Activate on intent data faster by connecting it to your existing GTM systems.
KB article: Keyword Intent Data API
Adobe Destination SDK
6sense is now a native destination in the Adobe Experience Platform Destination Catalog. Customers using Adobe RTCDP and 6sense can sign in via OAuth, map Adobe fields to 6sense inputs with Adobe's field-mapping, and activate audiences. 6sense creates a segment synchronized to the Adobe audience, which is then matched in 6sense the same as a segment created through any other method, eliminating the custom middleware customers previously had to build and maintain.
Value:
Activate Adobe-built account audiences in 6sense without custom middleware.
Connect through a self-serve setup using sign-in with your existing 6sense credentials.
Use the resulting segment for any 6sense use case, including advertising, sales intelligence, reporting, and automation.
KB article: Integrate 6sense with Adobe Experience Platform
Integrations settings consolidation
CRM, MAP, and other integrations are now unified in a single Integrations Hub in Settings.
From one place you can authenticate connections, manage API limits, set data standardization(inbound data mapping), define mapping profiles( outbound mapping), and control export permission rules. Previously these were scattered across multiple settings. The new layout gives admins an end-to-end view of connections and data mapping.
The new Integrations experience will be rolled out to all customers between November 16, 2026, and January 7, 2027.
Value:
Set up and manage integration related settings in one place.
Reduce setup time and the risk of misconfiguration with a guided, unified experience.
Rely on a consistent foundation that makes future integrations easier to add and manage.
KB articles:
Pipeline delay information: Platform
A pipeline delay indicator now appears in the 6sense platform when data processing is delayed. If you see this indicator, check whether your admins have received an email from 6sense about an action needed on your end, such as expired CRM/MAP credentials or sync issues.
Value:
Know right away when a pipeline delay may affect data freshness.
Avoid contacting support to find out whether stale data is a platform issue.
KB article: Revenue Marketing Home Page
Permission check alerts
Permission check alerts are now clearer and easier to act on. Alerts no longer include taxonomy-related fields that are not visible or editable in Data Standardization settings. Each impacted CRM field now also shows the corresponding 6sense field in a separate column, so admins can understand what each alert affects and take the right next step.
Value:
Focus on permission issues that can be fixed in Data Standardization settings.
See which 6sense field is affected by each CRM permission issue.
Resolve permission issues faster with clearer, more actionable alert messaging.
KB article: Field and Object Level Permission Checks for CRM
Simulated scores on 6sense sandboxes
Customer admins can now enable simulated predictive scores for sandbox environments.
This lets users evaluate predictive workflows without requiring a full predictive model in sandboxes. The sandbox receives synthetic, deterministic scores for key predictive signals.
These scores flow through supported platform experiences like real model outputs, letting teams test segments, exports, analytics, and sales workflows in a realistic sandbox setup.
When real predictive models are enabled, simulated scores are superseded by live model output.
The feature is available only to customers with the Advanced package on their production instance.
Value:
Evaluate predictive features in the sandbox environments without waiting for a full model build.
Test score-driven use cases with realistic synthetic data.
Accelerate onboarding and confidence in predictive adoption
KB article: Create and Use 6sense Sandbox
MCP: access controls
Admins can now control who uses 6sense MCP. A new MCP permission appears when you build custom roles, so you can decide which roles have access. An MCP setting on the global AI settings card lets you turn MCP use on or off for your organization. These controls extend the role-based access and AI settings you already use.
Value:
Limit MCP access to the roles that need it.
Enable or disable MCP for your whole organization from one AI settings card.
Meet your internal security and compliance policies for AI access.
KB article: AI and MCP Settings
Multi-Factor Authentication (MFA) with Time-Based One-Time Password (TOTP)
We are introducing Time-Based One-Time Password (TOTP) as an additional Multi-Factor Authentication (MFA) option for customers who are not using SSO. Organization administrators can use the self-service configuration to switch their 6sense authentication method for their entire organization from email-based OTP to TOTP, giving them greater control over their authentication preferences.
Value:
Strengthen account security by offering an additional MFA authentication method.
Support enterprise security and compliance requirements with TOTP-based authentication.
Reduce reliance on email delivery, avoiding potential delays and delivery issues for globally distributed users.
Improve the login experience by providing users with a familiar and convenient authentication option.
KB article: Multi-Factor Authentication (MFA)
User credit allocation enhancements
Credit allocation now supports a recurring monthly setup that automatically distributes credits to eligible Sales Intelligence users. Previously, admins had to manually manage and redistribute credits as team members joined, changed roles, or left the organization. With recurring monthly allocation, credits are automatically distributed, helping ensure users have the credits they need for their day-to-day workflows.
Value:
Less administrative effort: Spend less time manually calculating and redistributing credits
Predictable credit availability: Give users a consistent credit entitlement every month.
KB article: Manage Credit Allocation for Sales Intelligence Users
Secure, time-bound access for 6sense agency partners
We’re introducing a simpler and more secure way to manage 6sense agency access to your 6sense instance. Customers can now grant 6sense agency users edit access for a specified period and select the appropriate roles, including custom roles, based on their security requirements.
Access is automatically revoked when the defined period expires, eliminating the need for manual cleanup and helping ensure 6sense agency users only have access when needed. Partners can also seamlessly navigate between customer instances without repeatedly logging in and out.
Value:
Greater control and security: Define access duration and assign roles based on your organization's security policies and least-privilege requirements.
Automatic access revocation: Eliminate manual access cleanup with time-bound permissions that expire automatically.
KB article: Grant agency partner users access to 6sense