How to set up call tracking numbers in Ringba

So you've decided to run call tracking through Ringba. Honestly, that's a solid choice if you're buying or selling health insurance calls. I've set up tracking numbers for Medicare Advantage campaigns, ACA funnels, and U65 offers, and Ringba handles volume and routing logic better than most platforms I've tested. But here's the thing: setup has a handful of steps people skip. Those skipped steps come back to bite you in October when AEP volume hits.

This isn't a "click five buttons and you're done" situation. It's closer to twelve buttons, and a couple involve compliance decisions you can't undo easily. Let's get into it.

Step 1: Get your Ringba account and number pool ready

First things first. You need an active Ringba account, and you need to decide whether you're buying local numbers, toll-free numbers, or both.

Local numbers typically run $1 to $2 per month per number, plus per-minute usage. Toll-free numbers cost a bit more, often $2 to $3 monthly, with per-minute rates that shift depending on your carrier routing and volume commitments. If you're running national Medicare campaigns, toll-free numbers tend to build more trust with older callers; for geo-targeted ACA or U65 campaigns, local numbers with matching area codes often perform better on answer rates.

You buy these directly inside Ringba's number inventory, or port existing numbers in from another platform. Porting takes 5 to 10 business days on average, which matters a lot if you're switching platforms mid-cycle. I've seen agencies try to port numbers into Ringba in late September, right before AEP kicks off October 15, and end up with dead numbers during their busiest testing week. Don't do that. If you're migrating, start in August at the latest.

One-line takeaway: buy or port your numbers weeks before you need them. Not days.

Step 2: Connect your traffic sources

Ringba integrates with Google Ads, Facebook Ads, and Bing Ads, and this is where dynamic number insertion (DNI) comes in. DNI swaps the phone number shown on your landing page based on which traffic source, campaign, or ad group sent the visitor. Someone who clicks a Google ad for "Medicare Advantage plans near me" sees a different tracking number than someone who clicked a Facebook ad for the same offer, even though both numbers ring through to the same call center.

Setting this up means installing the Ringba tracking snippet on your landing pages, creating separate number pools for each traffic source (or in a lot of cases, each campaign within a source), and mapping your UTM parameters so Ringba can tie call outcomes back to the specific ad, keyword, or placement that generated the call.

That last part is where a lot of agencies fall short. Sub-ID tracking sounds like a nice-to-have. It's not. If you're running Medicare, U65, and ACA campaigns side by side and you're not tagging calls down to the creative and keyword level, you're flying blind on cost-per-acquisition. You'll know your overall spend and call volume, sure, but not which specific ad variant produces calls that convert into enrollments versus calls that just burn agent time. I've watched teams spend three months optimizing the wrong keyword because they were looking at campaign-level data instead of sub-ID data. Fix this early.

Step 3: Set up call recording and consent settings (don't skip this)

Here's what most people miss, and it's not small. Health insurance calls involve protected health information, and depending on the state, you might be dealing with two-party consent laws for call recording. Ringba lets you configure recording disclosures and consent prompts, but the defaults won't automatically match every state's legal requirements.

If you're buying calls for Medicare Advantage, ACA, or U65 plans and recording those calls, which you probably are for QA and compliance, turn on recording disclosure messages that play before the call connects. Check which states require two-party consent and make sure your disclosure language covers that. Document your TCPA compliance settings too, since CMS marketing rules for Medicare specifically scrutinize how calls are recorded, routed, and disclosed.

I'm not a lawyer and this isn't legal advice. But I've seen agencies get flagged during CMS audits because their recording disclosure wasn't playing consistently across all their number pools. It's a setup detail, not a legal strategy. Still, it's one of those details Ringba makes easy to configure and easy to forget.

Routing calls to the right agents

This matters more in health insurance than almost any other vertical I've worked in, because licensing is state-specific. An agent licensed in Ohio cannot legally take a call from a resident of Texas, at least not for most Medicare and ACA products. Ringba's routing engine can integrate with your agent availability schedules so calls only route to agents licensed in the caller's state.

Skip this integration and you're relying on manual transfers, or just hoping your call center catches the mismatch. That's a compliance risk under CMS Medicare marketing rules. It's also bad for conversion, since a misrouted call usually ends in a transfer or a hang-up.

Ringba also connects with dialers and CRMs common in this space, like Convoso and Five9, so your routing logic and compliance tracking live in one connected system instead of three disconnected ones. If you're running a real operation and not a side project, get these integrations wired up before enrollment starts. Not during.

Using RTB to sell or buy calls in real time

Ringba's real-time bidding (RTB) feature is where a lot of Medicare and ACA call buying and selling actually happens. RTB lets multiple insurance agencies or carriers bid on an inbound call the moment it comes in, with routing decisions made in milliseconds based on price, availability, and licensing match. If you're on the Ringba X side of things, either buying calls or selling them, RTB setup is worth understanding deeply rather than just switching on and forgetting about.

If you're looking to buy calls for your agency, or specifically to buy health insurance calls for Medicare, ACA, or U65 campaigns, RTB is usually the fastest way to scale volume without managing dozens of individual publisher relationships yourself.

A quick word on timing

ACA Open Enrollment generally runs November 1 through January 15 in most states, though Covered California and a few other state-based marketplaces run slightly different windows. Medicare AEP runs October 15 through December 7. So September is your setup and testing month for Medicare, and October is your setup month for ACA. Test everything: every number pool, every disclosure message, every routing rule, in the weeks before these windows open. Not during.

FAQ

How long does it take to fully set up Ringba for a new campaign? Basic number setup and DNI can be done in a day or two. Full integration with dialers, CRMs, and licensed agent routing usually takes one to two weeks if you're doing it right.

Can I port my existing tracking numbers into Ringba? Yes, and it typically takes 5 to 10 business days. Plan migrations at least a month before any enrollment period.

Do I need two-party consent settings for every state? No, only for states that legally require it. But your disclosure setup should account for the strictest applicable state if you're running national campaigns.

What's the difference between DNI and sub-ID tracking? DNI swaps the visible phone number based on traffic source. Sub-ID tracking tags each call with granular data like keyword or ad creative, which you need for real cost-per-acquisition analysis.