KPI Tree

Metric Definition

Net database expansion

Database Growth Rate = ((Ending Records - Starting Records) / Starting Records) x 100
Starting RecordsCount of usable records in the database at the start of the period
Ending RecordsCount of usable records at the end, after additions and removals

Track from

Metric GlossaryOperations Metrics

Database growth rate

Database growth rate is the percentage change in the number of usable records in a database over a defined period, net of additions, deletions, and decay. It tracks whether the addressable pool of contacts, accounts, or leads is expanding or shrinking. A healthy database growth rate keeps the funnel fed without letting record quality slide.

7 min read

Generate AI summary

What is database growth rate?

Database growth rate is the percentage change in the number of usable records in a database over a defined period, net of additions, deletions, and decay. If a marketing database holds 50,000 contacts at the start of a quarter and 56,000 at the end, the database growth rate is 12 per cent. It measures the net direction of the addressable pool, not just how many records were added.

The word net is what makes the metric honest. A team can add 8,000 contacts in a quarter and still post low growth if 6,000 records were suppressed, unsubscribed, or scrubbed as invalid. Database growth rate captures both sides of the ledger, so it reflects the pool you can actually reach rather than the raw volume of imports.

The metric matters because almost every downstream funnel number depends on the size and quality of the database. A growing, clean database gives campaigns more room to work and lifts lead conversion rate and pipeline. A database that looks like it is growing while quality erodes will quietly drag deliverability and conversion down, even as the headline count climbs.

Database growth rate should count usable records only. Bounced emails, suppressed contacts, duplicates, and records missing the fields you need to act on should be excluded from both the starting and ending counts. Counting dead records as growth inflates the number and hides decay that is eroding the reachable base.

How to calculate database growth rate

Database growth rate compares the count of usable records at two points in time. The arithmetic is simple, but the definition of usable does the real work: both counts must apply the same quality filter, or the rate will reflect changes in counting rules rather than real growth.

Work through the inputs in order to keep the comparison clean.

  1. 1

    Starting record count

    Count usable records at the start of the period, after removing duplicates, bounces, and suppressed contacts. This is the base the rate is measured against.

  2. 2

    Records added

    Count net new records acquired during the period through forms, imports, events, and enrichment. Deduplicate against the existing base so re-acquired contacts do not double count.

  3. 3

    Records removed

    Count records suppressed, unsubscribed, deleted, or scrubbed as invalid during the period. This is the decay that additions have to overcome.

  4. 4

    Express as a percentage

    Take the ending count, subtract the starting count, divide by the starting count, and multiply by 100. The result is the net growth rate as a comparable percentage.

Database growth rate in a metric tree

Database growth rate is a net figure with two opposing forces beneath it, which makes it well suited to a metric tree. Growth is acquisition minus decay, and acquisition itself splits across several channels with different owners and economics. A single growth number tells you the database moved, but not which lever moved it.

The decomposition below separates the channels that add records from the forces that remove them. If growth stalls, the tree shows whether inbound capture slowed, a data partner went stale, or suppression and bounces spiked, rather than leaving the cause to guesswork.

Metric tree insight

KPI Tree connects each branch to the team that influences it: inbound capture to demand generation, sourcing and enrichment to operations, and decay to the deliverability owner. When the growth rate moves, KPI Tree pushes the change to the accountable owner, and the verified impact loop checks whether a campaign genuinely grew the usable base rather than padding it with records that bounce within a month.

Database growth rate benchmarks

A healthy database growth rate depends on how mature the database is and how aggressively the team acquires contacts. Early databases grow fast off a small base, while large, established databases grow more slowly and fight harder against decay. The annualised ranges below are typical for B2B marketing databases and assume usable records are counted on both sides.

Database stageBelow parHealthyStrong
Early-stage (under 25k)Under 20 per cent20 to 50 per centOver 50 per cent
Scaling (25k to 100k)Under 10 per cent10 to 30 per centOver 30 per cent
Established (100k to 500k)Under 5 per cent5 to 15 per centOver 15 per cent
Mature (over 500k)Under 2 per cent2 to 10 per centOver 10 per cent

How to improve database growth rate

Improving database growth rate means adding usable records faster than the base decays, without trading quality for volume. The gains come from widening capture, keeping records clean at the point of entry, and slowing the rate at which contacts go stale. These four practices move it the most.

Widen high-intent capture

Add capture points where intent is highest: gated tools, calculators, and events. Records acquired with intent stay usable longer than cold list buys, so they lift net growth, not just the raw count.

Validate at the point of entry

Run email validation and deduplication as records enter the database. Catching invalid contacts before they land keeps the usable base honest and protects deliverability.

Enrich sparse records

Records missing key fields are not usable for targeting. Enrichment turns thin records into actionable ones, which raises the usable count without acquiring a single new contact.

Slow the decay rate

Re-engagement campaigns and preference centres pull contacts back before they suppress. Treating decay as a managed number, not background noise, protects the base you already paid to build.

Common mistakes when tracking database growth rate

  1. 1

    Counting raw additions as growth

    Reporting records added while ignoring suppression and bounces makes a shrinking database look like it is growing. Always measure the net change, not the gross intake.

  2. 2

    Including unusable records

    Letting bounced, duplicate, or field-incomplete records into the count inflates the base. Apply the same usable filter to both the starting and ending figures.

  3. 3

    Ignoring deduplication on import

    Re-importing existing contacts as if they were new overstates acquisition. Deduplicate against the live base so growth reflects genuinely new records.

  4. 4

    Reading growth without quality

    A high growth rate paired with rising bounce and unsubscribe rates is a warning, not a win. Always read database growth alongside the decay metrics that sit beneath it.

Related metrics

Lead conversion rate

Sales Metrics
HubSpotSalesforce

Metric Definition

Lead Conversion Rate = (Converted Leads / Total Leads) x 100

Lead conversion rate measures the percentage of leads that progress to the next meaningful stage in the sales funnel, whether that is becoming a qualified opportunity, a demo booking, or a paying customer. It is the primary indicator of how effectively your top-of-funnel activity translates into commercial outcomes.

View metric

Email open rate

Marketing Metrics
Customer.ioKlaviyoApollo

Metric Definition

Open Rate = (Emails Opened / Emails Delivered) × 100

Email open rate measures the percentage of delivered emails that are opened by recipients. It is one of the most widely tracked email marketing metrics, though recent privacy changes have made it less reliable as a standalone indicator of engagement.

View metric

Cost per acquisition

CPA

Marketing Metrics
Google Ads

Metric Definition

CPA = Total Campaign Cost / Number of Acquisitions

Cost per acquisition measures the total cost to acquire a single converting user, whether that conversion is a purchase, sign-up, or lead. CPA is the bottom-line efficiency metric for paid marketing, connecting ad spend to actual business outcomes rather than intermediate metrics like clicks or impressions.

View metric

Conversion rate

CVR

Marketing Metrics
ShopifyGoogle AdsGoogle AnalyticsPostHog

Metric Definition

Conversion Rate = (Number of Conversions / Total Visitors or Leads) × 100

Conversion rate measures the percentage of visitors, users, or leads who take a desired action, such as making a purchase, signing up for a trial, or submitting a form. It is the fundamental metric for evaluating the effectiveness of any acquisition funnel, landing page, or marketing campaign.

View metric

Why did my metric change?

Metric Definition

Use this diagnostic framework to work out what is driving swings in your database growth rate before you act on them.

View metric

Metric trees for operations teams

Metric Definition

See how database growth rate fits alongside the other operational measures an operations team tracks and owns.

View metric

Track database growth as a metric tree in KPI Tree

Decompose database growth rate into inbound capture, sourcing, and decay, with an accountable owner on every branch. When the rate moves, KPI Tree pushes the change to the right team and verifies whether a campaign genuinely grew the usable base rather than padding it with records that bounce.

Experience That Matters

Built by a team that's been in your shoes

Our team brings deep experience from leading Data, Growth and People teams at some of the fastest growing scaleups in Europe through to IPO and beyond. We've faced the same challenges you're facing now.

Checkout.com
Planet
UK Government
Travelex
BT
Sainsbury's
Goldman Sachs
Dojo
Redpin
Farfetch
Just Eat for Business