Skip to content
HEED Data Supply
Credit economics • HEED INSIGHTS

Apollo Credits: Measure Usable Yield, Not Export Volume

The CSV row count is the easiest number to report—and often the least useful.

01 / Credit economics

What does an Apollo export actually cost in credits?

An export and a credit charge are different events. Apollo documents that exporting saved contacts itself does not use credits, while saving net-new contacts with verified emails consumes credits. Reconcile the actual usage log with the resulting file before calculating yield; never assume every exported row represents a new charge.

Apollo also notes that exporting saved records does not automatically refresh them. Treat a downloaded file as a snapshot with its own evidence dates, not a new verification event. A large export can contain records acquired in earlier periods, and charges can come from features outside that export.

For an audit, freeze the date range, feature and cohort. Link charged events to records where possible, record unmatched events separately, and avoid distributing all account credits across one convenient CSV. If phone, enrichment or other feature charges use different units, report those in separate columns.

Sources: Apollo: export contacts to CSV

02 / Credit economics

How do you calculate usable records per charged credit?

Count unique records that meet the current brief and pass your review, then divide by credits actually charged for that cohort. Keep each exclusion visible and apply them sequentially to avoid double counting. This measures acquisition efficiency, not permission to send, inbox placement, response rate or sales performance.

Hypothetical example: an account is charged 1,000 relevant credits for a defined acquisition cohort. The linked file contains 1,000 rows. Remove 120 duplicates first, then 80 additional rows outside the brief, then 50 additional rows missing a required field. The resulting 750 usable rows yield 0.75 usable rows per charged credit.

The inverse is 1,000 / 750 = 1.333 credits per usable row. These are invented audit inputs, not Apollo performance data. If excluded categories overlap, assigning one primary reason in a fixed order prevents counting the same row twice. Keep uncertainty separate rather than forcing it into accepted or rejected.

Illustrative sequential cohort audit, not observed vendor results
StageRemoved at this stageRows remaining
Linked acquired cohort—1,000
Duplicate review120880
Audience-fit review80800
Required-field review50750

Sources: Apollo: export contacts to CSV

03 / Credit economics

When should a team compare a managed research batch?

Compare a managed batch when internal filtering and repair work dominate the acquisition process, or when the team only needs a narrow deliverable. Use the same acceptance rules for both workflows. A better credit yield is useful, but it does not eliminate the cost of staff time or unused capacity.

Suppose the hypothetical cohort required ten review hours at $60 per hour. That adds $600 / 750 = $0.80 of labor per usable row before allocating the subscription. Now compare that workflow with a written research brief, delivery review and import. Include all those tasks; outsourcing does not make review disappear.

Write the target, exclusion rules and required fields before requesting either option. HEED’s B2B research page describes the deliverable; use it to define a comparable batch rather than treating a checked email as a guaranteed buyer. Keep the comparison dated, because product rules and your workflow can change.

  • Reconcile charge events before assigning cost to a downloaded file.
  • Keep old saved records separate from newly acquired records.
  • Report review labor and useful output alongside credits consumed.

Sources: HEED B2B research scope

Define a B2B research briefSpecify the audience, required fields and exclusions before choosing a batch.

QUESTIONS

Common questions

Does downloading an old Apollo CSV reverify the contacts?

Apollo’s export documentation says export does not automatically re-enrich saved contacts. Use the available record evidence and dates; do not treat download time as a fresh check.

Is 75% the expected usable yield?

No. It is a hypothetical example. Your yield depends on the audience, required fields, duplicates and review method. Measure it on a defined cohort before making a purchase decision.

Sources

  1. Apollo: export contacts to CSV
  2. HEED B2B research scope
KEEP READING