Bitscale’s contact enrichment waterfalls—whether for email or phone—are designed to give you broad coverage using multiple providers. However, a key feature that can significantly impact both data quality and credit usage is validation inside the waterfall. This guide explains how that works, and when you should or shouldn’t enable it.
Each waterfall is a ranked list of enrichment providers. When run, the process works as follows:
This approach ensures you only pay for the provider that successfully returns usable contact information.
When this setting is enabled inside the waterfall:
This ensures your outbound efforts rely on high-quality, deliverable contacts—at the expense of potentially more API calls and credits.
How and where you apply validation depends on your workflow and intent.
If you are in the early stages of list building—perhaps testing segments, exploring new ICPs, or using large lead pools—it is more efficient to:
This approach is cost-efficient and gives you greater control over how credits are used.
If you are working with highly targeted lists, where every lead is valuable (e.g., from an ABM campaign, warm inbound submissions, or intent-based lists), you want maximum precision. In these cases, it is better to:
This workflow reduces the chance of bad emails making it into your CRM or outreach tool, even if it uses more credits per record.
Bitscale’s enrichment stack gives you flexibility to match your outreach strategy, but getting the most out of it depends on smart configuration. Use validation settings intentionally, and don’t hesitate to reach out if you need help setting up the right waterfall for your workflow.
Bitscale’s contact enrichment waterfalls—whether for email or phone—are designed to give you broad coverage using multiple providers. However, a key feature that can significantly impact both data quality and credit usage is validation inside the waterfall. This guide explains how that works, and when you should or shouldn’t enable it.
Each waterfall is a ranked list of enrichment providers. When run, the process works as follows:
This approach ensures you only pay for the provider that successfully returns usable contact information.
When this setting is enabled inside the waterfall:
This ensures your outbound efforts rely on high-quality, deliverable contacts—at the expense of potentially more API calls and credits.
How and where you apply validation depends on your workflow and intent.
If you are in the early stages of list building—perhaps testing segments, exploring new ICPs, or using large lead pools—it is more efficient to:
This approach is cost-efficient and gives you greater control over how credits are used.
If you are working with highly targeted lists, where every lead is valuable (e.g., from an ABM campaign, warm inbound submissions, or intent-based lists), you want maximum precision. In these cases, it is better to:
This workflow reduces the chance of bad emails making it into your CRM or outreach tool, even if it uses more credits per record.
Bitscale’s enrichment stack gives you flexibility to match your outreach strategy, but getting the most out of it depends on smart configuration. Use validation settings intentionally, and don’t hesitate to reach out if you need help setting up the right waterfall for your workflow.