First-party signals are the highest-confidence type — they're directly observed at your own site, app, or events. Capture web visits, content engagement, demo requests, and in-product behavior. Tighter coupling = better signal.
Web visit tracking
Identify which accounts (not which individuals — that's typically not knowable on cold web) are visiting your site, via reverse IP lookup, identity-resolution tools (Clearbit Reveal, Leadfeeder, RB2B), or your own integration. The signal: an ICP-fit account visiting your site is in research mode.
Content engagement
Whitepaper downloads, webinar registrations, and blog reading depth all become signals. Higher engagement (multiple touches over time) = a stronger signal than a single download.
Demo requests
The highest-intent first-party signal. A demo request is an explicit ask for sales engagement. Route demo requests to the right rep within minutes, with full context (account profile, prior engagement, signals).
In-product behavior
For products with free trials or freemium: in-product activity is the leading signal of buying readiness. Active users engaging with features, hitting limits, and inviting teammates all signal expansion intent. Connect your product analytics to turgo's signal stream.
Combining first-party with third-party
First-party signals are confidence-high but volume-low. Third-party signals (Bombora, G2) are volume-high but confidence-lower. Combining them: third-party signals identify the universe of accounts in research; first-party signals identify the specific accounts in active evaluation.
