Every time you reveal contact information in Lusha, credits are deducted from your balance. Understanding exactly how this works β and why a single reveal can cost more than one credit β helps you track usage and avoid surprises.
How credits are deducted
Lusha charges credits based on the types of data revealed per contact, not per contact unlock. Each data point has a separate credit cost:
Data type revealed | Credits deducted |
Email address only | 1 credit |
Phone number only | 1 credit |
Email + phone (both revealed together) | Up to 6 credits |
π‘ Note: When you click Reveal, Lusha shows all available data for that contact at once. This is why a single reveal can deduct more than 1 credit β you're paying for each piece of contact data surfaced, not just one.
Why Analytics may show higher numbers than you expect
The Analytics dashboard reflects credits at the account level, across all users and all channels. A few things that can cause the number to look higher than expected:
Credits used by other users on your account are included in the total
Credits consumed via integrations (Salesforce, HubSpot, etc.) count toward the balance
Bulk reveals deduct credits for all contacts in the selection, including those for whom only partial data was found
The "This cycle" view resets on your renewal date β not the calendar month β which can make the window feel shorter than expected
What are "conversation credits"?
Conversation credits are a separate credit type available on certain plan tiers. They are used when saving contact information through specific in-platform workflows. If you see this line item in your dashboard, it counts independently from your standard prospecting credits.
If you believe there's a discrepancy in your credit count
Go to Analytics β Credit Usage and filter by user and date range.
Compare the breakdown against your known reveal activity.
If credits were deducted with no corresponding reveal activity, contact Lusha Support via the chat icon in your dashboard.
β οΈ Important: Credits cannot be refunded for reveals already made, even if the contact data was incomplete. If you regularly find data quality issues, let Lusha Support know β patterns are reviewed by the data team.