Enrichment Budget
Cap how many enrichment credits you spend per period, and refresh your stalest contacts on a schedule within that cap.
Overview
Enrichment Budget gives enrichment the same discipline the send layer has: a spend cap. Enrichment costs credits, so you set a credit cap for the period, and a scheduled re-enrichment run refreshes your stalest contacts first, never spending past the cap. It is the credit-side parity to the per-day send budget on the dispatch queue.
The cap
Set a credit cap for the period, or leave it blank for unlimited. The panel shows your cap, the credits spent so far, and how many remain, and flags when the budget is exhausted. You can reset the period's spend when a new budget window opens. Any enrichment run, on-demand or scheduled, is gated on the remaining budget.
Scheduled re-enrichment
A weekly cron finds the contacts whose enrichment has gone stale, older than 90 days, or never enriched, and queues as many as the remaining budget allows, oldest-stale first. The preview on the panel shows exactly what a run would refresh and how many credits it would spend, and honestly reports the contacts it would skip for budget. Crucially, the run queues the work for your configured providers rather than calling them directly or fabricating enrichment, so it never invents data and never exceeds the cap.
Deterministic and honest
The selection and the budget math are deterministic: the same contacts and budget always queue the same work. Nothing is spent beyond the cap, and a contact enriched recently is left alone, so the budget goes to the data that actually needs refreshing.