Factors.ai releases Intent Upload API 2.0 for custom account signals
Factors.ai released Intent Upload API 2.0 on July 21, 2026. The company says customers can push any account signal into Factors by API, where it appears as a named event usable across segments, alerts, agents and reports.
On July 21, 2026, Factors.ai released version 2.0 of its Intent Upload API. The update lets customers send account-level signals from outside sources into Factors. The release notes give web research, social intent and custom events as examples. Signals sent through the API appear as named events on an account's journey, and the company says they can be used in segments, alerts, Scout routines, agents and reports like other Factors data. Each request can include up to 10,000 new accounts.
The details
- Release date: July 21, 2026, under Platform.
- Accepted signals include web research, social intent and custom events, per the entry.
- Uploaded signals appear as named events on the account journey.
- Signals work across segments, alerts, routines, agents and reports.
- Each request supports up to 10,000 new accounts.
Context
In July 2026 GTM Tech News covered Factors.ai bringing account timelines and agents into Salesforce and HubSpot, and adding Scout Routines and an AI planner. Intent Upload API 2.0 sits alongside those releases as a way to bring third-party and custom signals into the same account journeys those features use. Earlier in 2026 the company added Bombora research intent topics to its segment builder.
Not disclosed
- Pricing or credit costs for API uploads
- Rate limits beyond the per-request account cap
- Migration steps for users of the earlier API version
- Vendor
Factors.ai- Category
- Measurement & Attribution
- Announcement type
- Feature update
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.




