Skip to main content
TrailsparkDocs

Enrichment Rules & Budget Caps

Overview

Once you connect an enrichment provider, its Configure page gains an Enrichment rules tab. This is where you decide which accounts are worth enriching and, for providers that meter usage, set a budget so enrichment never runs away with your vendor spend.

Which accounts to enrich

Under Which accounts to enrich, you get the same rule builder used for ICP eligibility — the same account and product fields, just applied to a different question: not "which ICP does this account belong to," but "does this account get enriched." The guidance on the page explains the default: "Only fill in company details for accounts that match these rules. Leave empty to enrich every account with a business domain."

A couple of things happen automatically, regardless of your rules:

  • Accounts with no usable company domain — for example, one where the only email address on file is a personal one like @gmail.com — are never enriched.
  • An account that's already been enriched recently isn't re-enriched again right away; Trailspark reuses what it already has until it's due for a refresh. For PredictLeads specifically, company details are due for a refresh about every 90 days, and activity (hiring, funding, and the rest) is checked again about every 7 days by default — contact us if you need a different interval.

When to enrich

For providers that look accounts up on demand, the When to enrich section lets you choose the moment Trailspark spends credits on an account:

  • When accounts are evaluated (recommended) — Trailspark only enriches an account once it's engaged enough to be scored. This is the default, and it keeps you from spending vendor credits on accounts that never turn into anything.
  • As soon as a new account appears — Trailspark enriches a brand-new account right away, before it's been scored. Choose this if you want a new account sorted into the right ICP the moment it shows up, rather than waiting for it to be evaluated first. It does mean credits get spent sooner, including on some accounts that might not end up engaged enough to matter.

For PredictLeads, this section controls its company-detail lookups. Its activity checks (hiring, funding, and the rest) run on their own refresh schedule instead, so this choice doesn't change when those happen.

The section doesn't appear at all for a provider that syncs on a fixed schedule of its own rather than being looked up on demand, such as Reo.dev.

Enriched fields

Trailspark always makes the five standard company details — Industry, Employee Count, Region, Market Segment, and Website Domain — available everywhere, with nothing to turn on. But your provider may send back more than that: a funding stage, a headcount growth rate, or — from PredictLeads — the technologies it's detected in use at an account, or anything else specific to how you use it. The Enriched fields card is where you decide which of those extra fields Trailspark actually keeps and uses.

The card lists every extra field Trailspark has seen from your enrichment providers so far. For each one you get:

  • An editable label — the display name used everywhere the field shows up. It starts as a friendly version of the field name your provider sent (e.g. funding_stage becomes "Funding stage"), and you can rename it to whatever makes sense for your team.
  • A sample value and the number of accounts it's been seen on, so you can tell what you're turning on. A long list value, like PredictLeads' technologies, is shown as the first few entries plus a "+N more" count.
  • An Active toggle

Turn a field's toggle on and click Save fields to activate it. Once active, the field:

  • Becomes selectable in your ICP eligibility and scoring rules, labeled "(Enrichment)" so it reads apart from your own account fields
  • Is included in the account context Trailspark's AI sees when it scores that account
  • Appears as an extra row you can map on your destination's Enrichment Fields (or Account Fields) card

If no provider has sent anything beyond the standard five fields yet, the card reads: "No extra fields received yet. Fields your providers send beyond the standard company details will appear here."

Info

Turning a field off doesn't delete it. It stops appearing in rules, scoring context, and new destination pushes, but a destination mapping that already used it is kept — shown with a "No longer active" warning — so nothing is lost if you turn the field back on later.

Budget caps

Under Budget caps, you can set:

  • Monthly cap — the most credits this provider can spend in a calendar month
  • Daily cap — the most credits this provider can spend in a day

Both default to "No cap" if left blank, and the helper text under each reminds you the number is in the provider's own credits (e.g., "in Clay credits").

Info

What a cap actually counts is accounts sent to the provider per period, one per account. For Clay, what gets deducted from your own Clay credit balance per account depends on the enrichment columns in your Clay table — a single waterfall column might use one credit, but a table with several provider columns chained together can use more than one credit per row. Set your cap with that in mind if you're also watching your Clay credit balance directly.

Info

Not every provider meters every kind of usage the same way. PredictLeads is metered on every request — company-detail lookups and activity checks alike — so your Monthly cap and Daily cap cover both, and reaching either one pauses PredictLeads' company-detail lookups and its activity checks together. Reo.dev is the other case: its daily segment sync doesn't spend its own credits the way Clay's webhook does, so for Reo.dev your scope controls are the Segments picker (which segments Trailspark pulls from) and the "Which accounts sync" rules (which accounts Trailspark pushes to your Reo.dev list).

When you hit a cap

Caps are a hard pause, not a soft warning: once monthly or daily spend reaches its cap, enrichment for that provider stops. It automatically resumes at the start of the next period, or the moment you raise the cap. Accounts that would have been enriched while paused aren't lost — Trailspark picks them back up once enrichment resumes. While paused, the page shows an "Enrichment paused" banner: "Paused — enrichment resumes next period or when you raise the cap."

Usage at a glance

Above the rule builder, a usage strip shows:

  • Credits used this month — how many of the provider's credits enrichment has used so far this period
  • Remaining this month — what's left under your monthly cap, or "No monthly cap set" if you haven't set one
  • Match rate (last 30 days) — the share of enrichment lookups that found real company data, rather than coming back empty. If this drops noticeably, it's worth checking that your rules and the account identifiers behind them (domains, CRM records) still line up with what the provider expects.
  • Remaining with [provider] — your balance at the vendor itself, shown when the vendor lets Trailspark read it. PredictLeads does, so once it's connected you'll see "N PredictLeads credits remaining with PredictLeads". Clay and Reo.dev don't expose a balance today, so the line doesn't appear for them.

Saving is always preview-first

Clicking Save never applies a change immediately. Trailspark first estimates the impact and opens a "Confirm enrichment rules" dialog showing:

  • How many accounts this would enrich right now
  • An estimate of the credits that would use, in the provider's own units
  • A warning if the estimate would exceed your remaining budget — in that case, enrichment pauses at the cap rather than going over

From there, click Cancel to go back and adjust, or Save rules to confirm and apply the change.

Next Steps