To size a call tracking number pool, take the visitors on your site in your busiest hour, divide by the visits one number can serve in an hour (60 divided by your average visit length in minutes), and add about 30% as a buffer. You can read both figures from Google Analytics 4, or let a pool calculator work it out.

If you use call tracking with dynamic number insertion, one question comes up during setup: how many tracking numbers should the website pool hold?

Too few and calls are credited to the wrong visitor. Too many and you pay for numbers nobody sees. This guide gives you the formula and three ways to get the answer.

What is a call tracking number pool?

A call tracking number pool is a set of phone numbers (call tracking numbers) that dynamic number insertion shares between your website visitors. Each visitor sees a number of their own and keeps it for the visit, so a call to that number can be tied to the session behind it: the source, the campaign and the pages viewed.

Why pool size matters

Every visitor you want to track needs a different number while they are on the site. The pool has to cover the visitors who are browsing at the same moment, not your monthly total.

When the pool is too small, two visitors are given the same number. If one of them calls, the software cannot tell which visit the call belongs to, and one visitor’s data may be attached to the other.

In practice, a visitor who arrived through an ad can be labeled as coming directly to your site. The ad loses the credit, and the conversions reported in your advertising platform are wrong.

How to calculate the size of your number pool

You need two figures from Google Analytics: the visitors in your busiest hour and the average session duration in minutes. Then apply this formula:

[HOURLY VISITORS / (60 / average session duration)] * 1.3

The part in brackets is how many visits one number can serve in an hour. The 1.3 adds a 30% buffer for hours that are busier than expected.

If your peak is 200 visitors and the average session lasts 3 minutes, the pool is [200/(60/3)]*1.3 = 13 tracking numbers.

Session length matters as much as traffic. With the same 200 visitors, longer visits hold each number for longer, so the pool grows:

Here is how to find the hourly visitors and the average session duration in Google Analytics 4.

Method 1: Calculate the tracking number pool in GA4 with a table

Log in to Google Analytics and follow these steps.

  1. Choose Explore from the left menu.
  2. Choose Blank from the reporting options.
  3. In the Segments field choose None.
  4. In the Dimensions field choose Date + hour.
  5. In the Metrics field choose Sessions and Average Session duration.
  6. In the Technique field choose Free form.
  7. In the Visualization field choose Table.
  8. In the Rows field choose Date + hour.
  9. In the Values field choose Sessions and Average Session Duration.

GA4 exploration settings for a free form table of sessions by date and hour

You should see the table below. Sort it by Sessions to find the busiest hour, then note that hour’s Sessions value and its Average session duration. Put the two values into the formula above.

GA4 Exploration report - sessions per hour

Method 2: Calculate the tracking number pool in GA4 with a line chart

Log in to Google Analytics and follow these steps.

  1. Choose Explore from the left menu.
  2. Choose Blank from the reporting options.
  3. In the Segments field choose None.
  4. In the Dimensions field choose Date + hour.
  5. In the Metrics field choose Sessions.
  6. In the Granularity field choose Hour.
  7. In the Values field choose Sessions.

GA4 Explorations report - filters

You should see the chart below. Find the peak: that is the Sessions value to use in the formula.

Google Analytics 4 sample chart

Method 3: Calculate the tracking number pool automatically with the pool estimator

If building Explore reports in Google Analytics 4 feels too technical, Nimbata’s pool estimator works out the pool size in a few clicks. It is the in-app Number Pool Calculator: connect Google Analytics 4 and it recommends a pool from your real traffic, or enter your peak hourly visitors and it estimates one. The video shows how:

How to avoid paying for tracking numbers you do not use

A pool that is too small misattributes calls. A pool that is too large wastes budget every month. Marketers usually end up with too many numbers for one of two reasons.

The bundle trap

Call tracking platforms often sell packages that include a fixed block of tracking numbers. The bundle looks like good value, so you activate every number in it, whether or not your traffic needs them. The result is a pool sized by the plan and not by your visitors.

Forgetting to recalculate

Website traffic changes, and the number of tracking numbers you need changes with it. Many teams size the pool once from historical data and never look at it again. When traffic drops, they keep paying for numbers no visitor ever sees.

Four ways to keep the pool lean

  1. Review the pool on a schedule. Check that the number count still matches your current traffic, and allow for seasonal peaks and quiet periods.
  2. Assign numbers with a purpose. Give tracking numbers to specific campaigns or traffic sources, not to everything by default.
  3. Use dynamic number insertion. It assigns and swaps numbers by the visitor’s referral source, keyword or other criteria you set, so you do not need a long list of static numbers.
  4. Choose usage-based pricing. Pick a platform that lets you add and remove numbers as your needs change, so you pay for what you use.

Run the formula or the pool estimator each time you review, and release the numbers you no longer need.

Takeaway

A pool sized to your busiest hour gives every visitor a number of their own, so each call keeps its source. Work it out with the formula, read the figures from a GA4 table or line chart, or let the pool estimator do it, then check again whenever your traffic changes.