Skip to main content
TrailsparkDocs

Connecting PredictLeads

Overview

PredictLeads adds two things for accounts you already track:

  • Company details — industry, employee count, region, company type, and similar firmographic fields — for accounts where your CRM is thin or missing that information.
  • Third-party activity — public signs that an account is on the move: hiring, raising money, launching something new, expanding into a new office or market, and (optionally) adopting a technology you care about.

PredictLeads reads company websites, job boards, and news sources for those outside events. Nothing it brings in comes from your own product or CRM — it's public activity at the company itself, which is what can flag an account as worth a closer look before anyone from that company has shown up in your product at all.

Before you start

Don't have a PredictLeads account yet?

Sign up at predictleads.com/sign_up. Once you're in, your PredictLeads account shows both values you'll need to connect: your API key and your API token. A free monthly allowance is included, so you can connect and see real results before deciding whether to upgrade.

Trailspark's Connect screen for PredictLeads also has a "Don't have a PredictLeads account yet?" card with the same sign-up link, plus a Setup guide link back to this page — so you don't need to leave the Connect screen to find your way here.

Step 1: Connect

Go to Settings > Integrations, find PredictLeads in the Data enrichment section, and click Configure.

  • Connection name — a label for this connection (e.g., "PredictLeads production")
  • API key — paste the API key from your PredictLeads account.
  • API token — paste the API token from the same place. Both values come from your PredictLeads account.

Click Connect. Both values are stored securely and never shown again — to replace either one, disconnect and reconnect.

Step 2: Technologies to watch (optional)

In the Enrichment rules tab, PredictLeads has a Technologies to watch list — up to 50 technology names. When PredictLeads detects one of these newly in use at an account you track — a competitor's product, or a tool your product integrates with — Trailspark adds a labeled signal for it.

Leave the list empty to skip this check entirely, which also saves one PredictLeads request per account each time activity refreshes.

How PredictLeads activity shows up

Everything PredictLeads brings in arrives as its own clearly labeled entry, separate from anything that happened in your own product or CRM. A few examples of the label you'll see on an account's activity:

Third-party intent (PredictLeads): receives financing — raised $12M in Series A funding

Third-party intent (PredictLeads): 7 new job openings (software development 5, data analysis 2)

Third-party intent (PredictLeads): started using Snowflake

News events appear one at a time, dated to when PredictLeads found them. Job openings are combined into a single line each time PredictLeads checks — so an account with hundreds of open roles doesn't flood the account with individual entries. A technology only shows up here if you've added it to your Technologies to watch list in Step 2.

This activity supports what Trailspark already sees in your own product data. It never makes an account hot by itself, and it never triggers an evaluation on its own — it's picked up the next time the account is evaluated for its own, first-party reasons. See Third-Party Intent & Field Provenance for the full rule.

Company details from PredictLeads follow the same rule every other provider does: your CRM always wins, and PredictLeads only fills in a field your CRM leaves blank.

Spend

Every PredictLeads request spends one of your PredictLeads credits — company details and activity checks both count; Test connection doesn't. That means the Which accounts to enrich rules and Budget caps you set for PredictLeads directly control what PredictLeads costs you:

  • The first time Trailspark looks up an account, filling in company details costs 2 credits (one for company details, one for the technologies PredictLeads has detected there — this is also where your Technologies to watch list is checked, so a longer list doesn't add a separate cost on top).
  • After that, checking an account for new activity costs 2 credits per refresh (job openings + news).
  • Company details and activity checks are only requested for accounts that are actually about to be evaluated — Trailspark doesn't walk your whole account list on a timer, so quiet accounts you're not currently scoring aren't rebought.
  • Your Monthly cap and Daily cap cover company-detail lookups and activity checks alike — reaching either one pauses PredictLeads until the next period or until you raise the cap.
  • News events PredictLeads itself rates as low-confidence are skipped, so what you see stays focused on activity PredictLeads is confident actually happened.

If your PredictLeads plan's monthly request allowance runs out before your Trailspark caps do, PredictLeads itself stops answering and Trailspark shows: "PredictLeads monthly request limit reached — enrichment resumes next month or when you upgrade your PredictLeads plan." Trailspark keeps retrying on its normal schedule, so enrichment picks back up automatically once your PredictLeads allowance resets or you upgrade.

After you're connected

Once connected, the page shows "PredictLeads is connected." When PredictLeads can report your remaining balance, you'll also see "N PredictLeads credits remaining with PredictLeads" in the usage strip.

  • Test connection checks that both your API key and API token are valid. It's free — it doesn't spend a PredictLeads credit.
  • Disconnect stops all PredictLeads lookups and activity checks. Reconnect with a valid key and token to resume.

Next Steps