are credits refunded when data enrichment returns no results

Quick Answer

It depends on the platform. Clay refunds credits when an enrichment provider returns a completely empty result, but consumes credits for partial matches — even if the specific field you needed (like an email) came back blank. Apollo, Clearbit, and Lusha each have different policies, and most platforms do not automatically refund credits for partial or low-confidence results. Always check whether your platform distinguishes between a null result and a partial match before running large enrichment batches.

Frequently Asked Questions

Does Clay automatically refund credits when enrichment returns no results?
Clay does automatically refund credits when a provider returns a completely null response — meaning zero fields populated. However, if a provider returns any data at all (even just a company name or LinkedIn URL you already had), the credit is consumed and no refund is issued. This partial-match scenario is the most common source of unexpected credit drain on Clay. **What exactly counts as a 'partial result' in Clay?** A partial result is any response where at least one field in the provider's payload is non-null — even if that field is useless to you. Concrete examples: - Provider returns a company name and industry, but no email or phone → credit consumed, no refund - Provider returns a LinkedIn URL you already had in your CRM → credit consumed, no refund - Provider returns a job title but leaves email, phone, and company domain blank → credit consumed, no refund - Provider returns absolutely nothing — null across every field → credit refunded The threshold is binary from Clay's billing perspective: any data at all = charged. This means the quality or utility of the returned data is irrelevant to whether you're billed. **Why this matters more than most users realize:** If you're running enrichment on a list of 1,000 contacts and 40% return partials (common when targeting niche industries or international markets), you've consumed 400 credits for data that didn't give you what you needed. At scale, partial-result drain is often larger than null-result drain because providers frequently return *something* — just not the specific field you were after. **Workarounds to avoid being charged for useless partials:** 1. **Use Clay's conditional logic** to check whether the specific field you need (e.g., email) is populated before triggering downstream enrichment steps. If email is null in step 1, don't fire step 2. 2. **Clean your input list first.** Partial results spike when input data is poor — misspelled company names, outdated domains, or incomplete contact records cause providers to return low-confidence partials instead of clean matches. Cleansing before enrichment directly reduces partial-result rate. 3. **Sequence providers by match-rate strength for your persona.** Run your highest match-rate provider first (test this with a 200-record sample). If it returns null, then try the fallback — rather than running both in parallel and paying for two partials. 4. **Always check your enrichment logs** to distinguish between null returns and partial returns. Clay's activity log will show you exactly what each provider returned, letting you audit which providers are producing high partial rates for your specific use case. If you're consistently seeing high partial rates from a specific provider in Clay, that's a signal to remove it from your waterfall and test an alternative — not to absorb the cost as normal.
Do Clay credits roll over to the next month?
No. Clay credits reset at the beginning of each billing cycle and unused credits do not roll over on standard monthly plans. This means that credits lost to failed or partial enrichments represent a compounded cost — you've lost both the spent credit and any unused balance at month-end. If you're consistently under-utilizing your Clay credit allotment, consider downgrading your plan tier rather than carrying unused credits that expire.
What is the difference between data cleansing and data enrichment?
Data cleansing validates, corrects, and standardizes data you already possess — verifying email deliverability, removing duplicates, normalizing formatting. Data enrichment appends new information to existing records — finding emails, phone numbers, firmographics, or technographics for contacts where that data is missing. From a credit perspective, cleansing is low-risk and low-cost per record, while enrichment carries higher credit cost and match-rate risk. Best practice is always to cleanse first, then enrich, to avoid spending enrichment credits on records with bad input data.
What happens to credits if a data enrichment provider has an outage or returns bad data at scale?
This varies by platform and plan tier. On standard plans, most platforms do not automatically adjust credits for provider-side quality issues. However, if you can demonstrate that a systematic failure (outage, known data quality degradation) affected a large batch, support teams at Clay, Apollo, and others will sometimes issue manual credit adjustments. Enterprise accounts with dedicated CSMs and SLA provisions have a significantly clearer path to bulk credit adjustments. Document the batch ID, affected record count, sample outputs, and timeline, then escalate to support or your account manager with that evidence.
Which data enrichment platform is most cost-predictable for teams worried about wasted credits?
Dropcontact is generally the most cost-predictable model for teams concerned about credit waste — you are only charged when a verified email is actually returned. This makes it straightforward to forecast cost-per-record. Clay offers good null-result protection but still charges for partial matches. Apollo is the least forgiving for credit waste, as export credits are consumed based on the export action rather than data quality. For variable-volume teams, platforms with non-expiring pay-as-you-go credit bundles (like Dropcontact or Hunter.io) offer better cost control than fixed monthly credit plans.
Does a low-confidence email match consume a credit the same way a verified match does?
Yes, in nearly all platforms. A low-confidence match is still classified as a 'result' from the provider's perspective, meaning the credit is consumed whether the confidence score is 90% or 30%. The practical risk is that low-confidence emails are far more likely to bounce, which can harm your sender reputation on platforms like Instantly, Smartlead, or any sending infrastructure you use. Always apply confidence score thresholds in your enrichment workflow and run low-confidence emails through a verification tool like ZeroBounce before sending.
How can I calculate whether a data enrichment provider is actually worth the credit cost?
Track your effective cost-per-usable-record, not just the nominal cost-per-credit. Run a sample batch of 200–500 records, then divide total credits consumed by the number of records that returned the specific field you needed (e.g., a valid, deliverable email). If you spent 300 credits and got 120 usable emails, your effective cost is 2.5 credits per usable result — not 1 credit as advertised. Compare this across providers for your specific target persona and geography. This metric is the most honest measure of provider value for your particular use case.
How do I request a manual credit refund from an enrichment platform's support team?
Manual refund requests succeed or fail almost entirely based on how well you document the case before contacting support. Here's what to compile before reaching out: 1. **Batch ID or run timestamp** — The specific enrichment run in question. In Clay, this is visible in your activity log. In Apollo, it's tied to your export history. 2. **Record count affected** — Exact number of records that returned the problematic result (null, partial, or bad data). A rough estimate weakens your case. 3. **Sample outputs** — Pull 5–10 representative records showing exactly what the provider returned versus what was expected. Screenshots or CSV exports work. 4. **Timeline** — When the run occurred. If it correlates with a known provider outage (check the platform's status page), include that reference. 5. **The specific ask** — State clearly whether you want a full credit restore, partial credit, or account credit. Vague requests get vague responses. **Realistic expectations by account tier:** - *Free/starter plans*: Manual refunds are rarely issued. Support will typically point to documentation stating credits are consumed on any result. - *Standard paid plans*: You have roughly a 30–50% success rate if the issue was systematic (e.g., a provider-side outage) and you document it well. One-off partial results are almost never refunded. - *Enterprise/high-volume accounts with a CSM*: Significantly better outcomes, especially if you can frame it as a recurring quality issue affecting your ROI on the contract. For Clay specifically, the best escalation path is the Slack community first — the team is active there and can flag issues faster than a standard support ticket. For Apollo, direct your request to billing support with the export ID attached.

Sources

  1. Clay Pricing and Credits Documentation — Referenced for Clay's credit consumption model. Clay operates on a waterfall enrichment system where credits are consumed per provider query. Critically, Clay refunds credits on fully null responses but charges for partial matches — meaning a record that returns a company name but no email still triggers a full credit deduction. Clay plans start at $149/month (Starter, 2,000 credits) up to $800/month (Pro, 10,000 credits), with unused credits rolling over only on annual plans. At scale, partial-match credit loss can represent 15–30% of monthly credit budgets based on typical B2B list quality.
  2. Apollo.io Credit and Usage Policies — Referenced for Apollo's export-based credit model. Apollo charges credits at the point of contact export, not at the point of enrichment query — meaning a failed phone number lookup that still exports a record with email-only data consumes a full export credit with no automatic refund pathway. Apollo's free tier allows 10 export credits/month; paid plans begin at $49/month (Basic, 1,000 credits). Apollo does not publish an automatic refund policy for null or invalid enrichment results; credit disputes require manual support contact with no guaranteed resolution SLA.
  3. Dropcontact Pricing and Credit Model — Referenced as the primary comparison point for verified-match-only billing. Dropcontact only charges a credit when it returns a verified, GDPR-compliant result — no match means no charge, making it the most cost-predictable enrichment option for European B2B data. Dropcontact pricing is volume-based (starting around €24/month for 1,000 enrichments), with match rates publicly cited at 60–75% for European business contacts. For teams with noisy input lists, this model can reduce effective per-verified-result cost by 25–40% compared to charge-on-query platforms.
  4. Lusha Pricing and Credit Usage — Referenced for Lusha's reveal-based credit consumption model. Lusha deducts a credit the moment a contact profile is revealed — regardless of whether the specific data field requested (e.g., direct dial phone) is populated. Free plan includes 5 credits/month; Pro plans start at $29/user/month (480 credits/year). Lusha does not offer automatic refunds for invalid or undeliverable results. For high-volume outbound teams, invalid phone number reveal rates of 10–20% are common, representing direct credit waste with no recourse outside manual support escalation.
  5. ZeroBounce Email Verification — Referenced as a recommended pre-enrichment validation step to reduce downstream credit waste. ZeroBounce validates email deliverability before you run enrichment, removing addresses flagged as invalid, catch-all, or disposable. ZeroBounce pricing starts at $15 for 2,000 verifications. For teams running enrichment on cold lists, pre-validation typically removes 8–22% of records as unworkable before any enrichment credit is spent — on a 10,000-record list at $0.05/enrichment credit, that translates to $40–$110 in avoided credit waste per batch.

Get Expert GTM Answers with Maestro

Stop guessing. Maestro gives you the infrastructure, templates, and expert playbooks to execute GTM at scale.

Try Maestro Free