Skip to main content
RingPools serve unique promo numbers to each landing page visitor, capturing individual attribution data before routing the call to your destination.
Whenever someone visits one of your landing pages, Invoca replaces the phone number on your page with a promo number served specifically for that visitor. Those promo numbers are pulled from your RingPool — an Invoca feature that acts as a container for your promo numbers. Here’s how RingPools work:
  • When a visitor lands on your page, the Invoca Tag swaps any phone numbers on that page with a promo number from your RingPool. For a limited time, only that visitor sees their assigned number.
  • Any marketing attribution data from that visitor’s session, including Marketing Data, is captured and associated with that unique number.
  • When the visitor dials the promo number, the call routes to the destination number originally shown on your landing page, along with the caller’s attribution data.
When you deploy Invoca on your landing pages, your account automatically replaces destination phone numbers with promo numbers from your RingPool, matching toll-free and local numbers to the correct NPA or area code.
Matching local numbers is bound by area code availability. If Invoca can’t serve a promo number in your detected destination’s area code, it allocates a number from the same rate center — or, if none are available there, from the next closest rate center in the same state.
Older Invoca accounts may still use campaign-based RingPools instead, which are discrete RingPools tied to individual campaigns — see “Managing campaign-based RingPools” below.

​
Managing the size of your RingPools

The number of promo numbers in your account affects billing, so it’s worth keeping an eye on your RingPool sizes. When creating a new RingPool, you can enable RingPool Auto-Scaling to automatically manage the number of promo numbers based on your web traffic.

​
Managing campaign-based RingPools

In older accounts, RingPools are tied to a specific campaign and don’t automatically match destination numbers to a similar area code — you assign them a local or toll-free number type manually. We recommend using Tag-based RingPools if you’re just starting out, but if you need to create or edit a campaign-based RingPool:
  1. Log in to your Invoca account, click Campaigns, then select Manage Campaigns.
  2. Select the campaign for your RingPool, or create a new campaign.
  3. Click the RingPools tab, then click Add New RingPool.
  4. Fill out the following, then click Next:
    • Name: we recommend matching your campaign name for easy management.
    • RingPool ID: only needed if managing RingPools via the Network Integration API — otherwise leave it blank.
    • Number session lifetime: the minimum time Invoca stores attribution for a given RingPool number. We recommend 5 minutes for efficient number use.
    • Max pool size: how many concurrent unique visitors you want to track (minimum 2) — this may grow or shrink automatically depending on your RingPool management settings.
    • Number type: toll-free (starting with 8XX) or local (starting with a local area code).
  5. Check the Marketing Data Parameters Captured window to confirm it matches the attribution data you want to collect. If not, create or edit fields in your Marketing Data dictionary first. Click Save & Next, then Done.
To change these settings later, repeat step 1, click the RingPools tab, then click Edit in the Actions column.

​
FAQ

What if there are more visitors on my landing page than numbers in my RingPool? If you’ve set up an overflow number, additional visitors see that number instead of a unique one — it still routes calls accurately for basic tracking, but can’t capture personalized attribution. Without an overflow number, additional visitors see your original destination number, with no tracking or personalized attribution at all until your RingPool grows or a previous session ends. How long is my caller’s attribution data associated with a phone number? At minimum, for the duration set in your “number session lifetime” setting. After that, it holds until another visitor needs a unique number — or up to 72 hours if the number is never reassigned. What if a visitor writes down the number and calls back the next day? If that number hasn’t been reassigned to another visitor since, Invoca still associates the original visitor’s attributes with the call. Otherwise, the call is associated with whoever most recently received that number — though this mix-up is rare. When a promo number is removed from my account, can it be reassigned to a different customer? Eventually, yes. After removal — manually or through RingPool scaling down — the number is quarantined to make sure it’s no longer receiving calls for your business, then returned to Invoca’s available pool once cleared. In theory this could mean a customer calling back an old number reaches a different business entirely, but this is exceedingly rare in practice. Can I access my RingPools programmatically (via API)? Yes — see the RingPool API and Bulk RingPool API documentation for details.

​
Where to go next

Last modified on September 25, 2026