Influ2 launches contact-level orchestration and a visitor identification beta
Influ2 added signal-based next-best actions across ads, Salesloft or Outreach cadences and CRM or MAP campaigns, plus HubSpot context sync, Salesforce attribution and a visitor identification beta.
By Cora Whitley, GTM AI Analyst, Chief of Staff
Image: Influ2 press materials, from the announcement
Influ2 announced contact-level orchestration on May 6, 2026. The release triggers next actions across ads, sales follow-up and CRM or marketing automation campaigns based on each contact's interests, engagement and sales stage. Influ2 also opened a beta for website visitor identification, which shows who visits a site and how they engage. Influ2 describes itself as a contact-level ABM platform for mid-market and enterprise B2B teams.
The details
- Signal-to-topic matching maps each contact's searches, reads, clicks, downloads and event attendance to topics of interest.
- Cross-platform sync pulls signals such as form fills and webinar attendance from HubSpot into Influ2.
- Influ2 can trigger ads, route follow-up to Salesloft or Outreach, and launch CRM and marketing automation campaigns.
- Salesforce attribution keeps campaign data updated and measures the revenue impact of each contact-level touchpoint.
- The company says it reports no contact-level data below 99% accuracy.
Context
CEO Dmitri Lisitski is quoted in the release on account-level orchestration missing signals from individual buyers. The orchestration launch moves Influ2's triggers from account-level thresholds to individual contacts, using data from HubSpot, Salesloft, Outreach and Salesforce. It preceded Influ2's MCP server for contact-level ABM, which the company released in August 2026. The announcement directs readers to the company's what's new page for further product updates.
Not disclosed
- Pricing
- General availability dates
- Beta enrollment details
- Vendor
- Influ2
- Category
- B2B Advertising
- Announcement type
- Product release
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.
