This glossary contains definitions for terms you see when using Ringba and in the pay-per-call market. It contains useful links to additional information.
A | B | C | D | E | f | G | H | I | J | k | L | M | N | O | P | Q | R | S | T | U | V | W | x | y | z
A
account balance
The amount of credit available in your Ringba account. Ringba draws from this balance to cover incremental costs like call minutes, call transcription, and other fees.
See Billing Settings.
adjustment
Changes made to the revenue and/or payout of one or more calls after the call has already occurred. You can make call adjustments in bulk from the Reporting screen.
Also called call adjustment
admin
Admin is one of the user roles available in Ringba. Admins are the primary users of an account, with access to all features. They can invite publisher and buyer users to access reporting and limited functionality in the account.
See User Roles.
affiliate
In the pay-per-call industry, an affiliate generates and sends calls, usually in exchange for a payout. Ringba uses this term interchangeably with publisher.
See Publishers.
agent
A person who answers calls on behalf of a target or call center. Ringba tracks whether an agent was available and how quickly they answered.
API
A way to programmatically access and control nearly everything you can do in the Ringba user interface, using code you or a developer writes.
See Ringba API.
B
bid modifiers
Rules you configure during Real Time Bidding that adjust a bid amount up or down when a call meets criteria you specify, such as a tag value matching a certain state or ZIP Code.
See the section on Bid Modifiers in the Real-Time Bidding FAQ
billing
The screen where you manage your account balance, credit cards, and automatic recharge settings, and where you download transaction history and monthly statements.
See Billing Settings.
bulk tags
A file you upload that contains values your tag routing filters can use.
See Bulk Tags.
buyer
The entity that wants the call, usually a call center or broker.
See Buyers.
C
Call Details report
A table on the Reporting screen with a row for every call. You can expand any row to see the call's events, tags, recording, and other details.
See Call Details Report.
call flow
A decision tree you build on a drag-and-drop canvas of nodes to control how a call is prompted, processed, and ultimately routed to a target.
call logs
A record of the calls that occurred in your account. You can view and search call logs in the Call Details report.
See Call Details Report.
call recording
An audio recording of a call while it's connected to a target. You can enable recording per campaign, call flow, or target, and listen to recordings from the Reporting screen.
See Call Recording.
call transcription
A paid feature that converts a call recording into a text transcript you can read from the Call Details report.
See Call Transcription.
caller
The person whose phone call comes into Ringba.
campaign
The configuration that controls every aspect of the calls routed through Ringba, including tracking numbers, payout settings, call routing, URL parameters, and pixels.
See Campaigns.
cap
A limit on the number of calls (or amount of revenue) a target, target group, or campaign can receive during a period. Once the cap is reached, Ringba stops sending calls to that target until the cap resets.
charge
An amount debited to your credit card. When you pay fees, Ringba charges your credit card. When you recharge your account, Ringba adds the amount of the charge to your account balance.
See Types of Fees, Charges, and Recharges.
CID
Abbreviation for call ID, Ringba's unique identifier for each inbound call.
conversion
A call that meets the criteria you configure to be considered a successful, billable outcome — for example, connecting for a minimum duration, connecting at all, or receiving a postback from a buyer.
See Routing Plans.
custom domain
A dedicated web address, connected through your DNS provider's CNAME records, that lets publishers and buyers sign in to your white-labeled portal using your own domain name instead of Ringba's.
See White Label Custom Domain.
custom reports
Saved Reporting screen configurations (filters, date ranges, and columns) that you can access quickly from the left navigation instead of rebuilding the view each time.
See Custom Reports.
custom revenue
Configuring a campaign to record different revenue amounts depending on characteristics of the call, such as duration or caller location, typically using pixels and a webhook.
See How to Configure Custom Revenue.
custom scoring
A feature to let you score and enrich a call before putting the call up for auction.
See Custom Scoring.
D
dial node
A call flow node that routes a call to a target according to the routing plan you choose. A branch of a call flow that ends in sending the call to a target always ends in a dial node.
See Dial Node.
DID
Direct Inward Dialing. It's a number that lets a caller dial directly to recipient, such as a business. It is a standard, old-fashioned phone number that is not a SIP.
duplicate call
A call from a caller ID that has previously connected to (or converted with) a target. You can configure how Ringba routes duplicate calls at the buyer or target level.
See Duplicate Call Routing - Buyers.
E
estimated revenue per call (eRPC)
An estimate, calculated before a call converts, of how much revenue a target is likely to generate for a given call based on their previous performance. Predictive routing uses this estimate to choose the best target.
Also called estimated revenue per call (eRPC).
See Predictive Routing.
G
gather node
A call flow node that prompts the caller for input, such as a ZIP Code, and adds the caller's response to the call as a tag. The gather node can accept key presses or spoken responses from the caller.
See Gather Node.
go to node
A call flow node that sends the call back to an earlier node in the call flow, letting you loop or retry part of the flow.
See Go To Node.
H
hangup node
A call flow node that terminates (ends) the call.
See Hangup Node.
hours node
A call flow node that routes a call down a different path depending on whether it arrives during the hours of operation you configure.
See Hours Node.
I
Inbound Data Enrichment (IDE)
A feature that lets your publishers or lead-generation partners send you caller information, such as ZIP Code, name, or age, before the call arrives, so Ringba can attach it to the call as tags for routing and reporting.
insights
This feature lets you have a complete overview of your performance metrics, generate detailed reports, and view call data broken down by campaign, publisher, target, or many other dimensions.
When a person contacts you, we use the caller ID to append information we know about the person for your immediate use. We get this information from a variety of available sources. You can also pass this information on to your targets.
See Insights Overview.
Instant Caller Profile (ICP)
A paid data-enrichment feature that pulls information about a caller from a broad, regularly updated repository and adds it to the call as tags first thing, before the caller even hears the first ring.
See Instant Caller Profile by Ringba.
integrations
Integrations are connections you make between your Ringba account and a third-party software. For example, you can integrate with Google Ads to track your calls as conversions. Ringba offers integrations with many kinds of software, and you can use the API to integrate your account with additional services.
invitation
The email Ringba sends when an admin adds a new user to the account. The recipient clicks the link in the invitation to set a password and configure multi-factor authentication.
See How to Manage Invitations for Users.
intelligent voice assistance (IVA)
It’s like an IVR, but with added artificial intelligence to allow callers to provide information about themselves through speech.
interactive voice response (IVR)
Functionality that automatically interacts with callers to gather information or present menu options before a human answers the call. Ringba's Gather node and Menu node provide IVR functionality inside call flows.
J
JS node
A call flow node that lets you execute custom JavaScript. This node is included in your subscription but isn't enabled by default; contact Support to request it.
See JS Node.
L
landing page
The web page a caller visits, often containing a phone number inserted dynamically by a call tracking tag, before they call your tracking number.
See Call Tracking Tags.
M
menu node
A call flow node that presents the caller with options, such as "Press 1 for sales," and routes the call based on the key the caller presses.
See Menu Node.
multi-factor authentication (MFA)
A required extra layer of login security. After entering your password, you must also enter a code from an authenticator app on your phone to sign in.
See Multi-Factor Authentication.
N
numbers
The phone numbers in your Ringba account, including tracking numbers you display to callers and the numbers you configure for targets to receive calls.
See Numbers Overview.
number blocking
A feature that lets you block calls from specific numbers, prefixes, area codes, or country codes, either for your entire account or for a single campaign.
See Number Blocking.
number formatting
The international standard (E.164) Ringba expects for phone numbers you enter manually, consisting of a plus sign, country calling code, area code, and local number, with no other punctuation.
See Formatting.
number pools
This term refers both to a group of tracking numbers and to a JavaScript snippet that shows a different tracking number to each landing page visitor. Use this feature to let Ringba connect the visitor's browser session data to their eventual call.
See Number Pools.
number porting
The process of transferring an existing phone number into or out of your Ringba account, typically requiring a signed letter of agency and other carrier paperwork.
See Number Porting.
O
offer
Offers are a convenient way to present a campaign to your publishers. It is a public representation of the campaign that allows publishers to quickly decide if they want to send calls to a campaign and if their call traffic meets the conversion requirements.
See Offers.
P
partner
A general term for the publishers, buyers, and other outside organizations you work with in Ringba to send or receive calls.
pass through
RTB pass through lets you ping ring trees and static targets in your routing plan during the real-time bidding (RTB) ping to get information like target acceptance and revenue. This lets you set a margin between the potential publisher payout and the target revenue.
See RTB Pass Through.
payout
The amount of money you pay a publisher for calls that meet the payout criteria you configure for a campaign or publisher.
See Payouts.
ping
An API request Ringba sends to a ring tree target (or that a buyer sends to Ringba during real-time bidding) to check availability, retrieve a bid, or gather information before a call is actually connected.
pixel
A tool for sending information from Ringba to another platform, such as a CRM or ad network, when a call event you choose occurs. For example, you might instruct Ringba to fire a pixel when a call converts.
See Pixels.
pixel node
A call flow node that fires a pixel based on where the caller is in the call flow, rather than a call-level event like Completed or Converted. For example, you might set up your pixel node to fire the pixel only if the caller reaches the Voicemail node.
See Pixel Node.
play node
A call flow node that plays a recorded audio file or a text-to-speech message to the caller.
See Play Node.
predictive routing
A call routing option that uses an algorithm to route each call to the target with the best estimated revenue per call (RPC), layered with any priority bonuses you configure.
See Predictive Routing.
priority and weight
The settings that control which target receives a call in Priority (Standard) routing. A lower Priority number is tried first; Weight determines how calls are split among targets that share the same priority.
See Priority and Weight.
profile node
A call flow node that pulls data-enriched information about the caller from Instant Caller Profile (ICP) and adds it to the call as tags, before the caller hears the first ring.
See Profile Node.
publisher
The ad creator.
Q
quick reports
Links on the Manage Campaigns, Manage Publishers, and Manage Targets screens that take you directly to the Reporting screen, pre-filtered to the campaign, publisher, or target you selected.
See Quick Reports.
R
real-time bidding (RTB)
A feature that lets your publishers request a bid from your account for a call before sending it. Ringba checks target availability and applies any bid modifiers you configure to calculate the bid it returns.
See Real Time Bidding Setup Guide.
real-time bidding with pass through
A version of real-time bidding where Ringba pings your ring tree targets or static targets during the bid itself to check their acceptance and bid amount, letting you reserve a margin between what the target pays and what you bid to the publisher.
See RTB Pass Through.
recharge
Adding funds to your account balance, either manually or automatically when your balance falls below a minimum you configure.
See Types of Fees, Charges, and Recharges.
Reporting
The screen where you view, filter, and export the call, revenue, and performance data Ringba collects about your account. It includes a Reporting Panel, Timeline, Summary, and Call Details.
See Reporting.
reporting filters
Tools on the Reporting screen that let you narrow the data you see down to specific campaigns, publishers, targets, tags, or other criteria.
See Reporting Filters.
reporting tags
A name/value pair that contains metadata about your calls.
revenue
The amount of money a call generates for your account, based on the conversion and payout settings you configure for a campaign, target, or ring tree target.
revenue per call (RPC)
An estimate, calculated before a call converts, of how much revenue a target is likely to generate for a given call based on their previous performance. Predictive routing uses this estimate to choose the best target.
Also called estimated revenue per call (eRPC).
revenue recovery
A feature that reroutes a call to another eligible target if the original target ends the call too soon to convert, giving the call another chance to generate revenue.
See Revenue Recovery.
ring tree
A ring tree is a container for ring tree targets. You set up several potential targets in the ring tree and Ringba pings all the targets at the same time to retrieve the information you need to choose the best target to send the call.
ring tree target
A ring tree target is one of the targets you set up for ping-post buying. Ringba pings all the targets in a ring tree at the same time to choose the best target to send the call.
See Ring Tree Target Setup Guide.
Ringba
A platform that helps businesses buy, sell, track, and optimize inbound phone calls, showing where calls came from, routing them in real time, and measuring the outcome.
See What is Ringba?
Ringba X
Ringba's marketplace platform that connects a vetted pool of buyers and sellers of inbound calls without requiring them to set up each partner relationship individually.
router node
A call flow node that routes the call down different paths based on filters you define, letting you make branching decisions inside a call flow.
See Router Node.
routing
The process of directing a call to a target. Ringba offers three ways to route calls in a campaign: Priority (Standard), Predictive, and Call Flows.
See Routing.
routing plan
The configuration of targets, target groups, and/or ring trees that, along with their priorities and weights, determines which target(s) are eligible to receive a call and in what order.
See Routing Plans.
S
session initiation protocol (SIP)
A protocol used to make voice calls over the internet (VoIP) instead of the traditional phone network. Ringba supports SIP forwarding to targets and can include call data in the SIP headers.
See Can I send calls to a Ringba customer using SIP?
sharable tags
A product feature that sends reporting tags automatically to another Ringba account.
See Shareable Tags between Ringba Accounts.
SIP routing
SIP routing for calls means using Voice Over IP (VoIP) instead of a traditional phone number to connect directly to a target. SIP gives you faster connections, better voice quality, and the ability to pass data in the SIP header.
simuldial
Simuldial is simultaneous dialing of multiple targets. It is a feature available on target groups.
See Target Groups.
source
The thing that generated a phone call. Example sources include:
- Phone number
- Marketing campaign
- Partner
- Publisher
- Affiliate
- Other
splitter node
A call flow node that splits call traffic between two or more paths by a percentage you define, letting you run A/B tests inside a call flow.
See Splitter Node.
statement
A statement of the charges on your account. Ringba generates a downloadable monthly statement of everything you were charged for.
See Billing Settings.
subscription
A license to use Ringba.
See Platform Pricing.
summary report
A table on the Reporting screen that groups and aggregates call data into totals you can pivot by campaign, publisher, target, buyer, and more.
See Summary Report.
T
tags
Metadata about your calls. Ringba applies tags to your calls as they proceed through your campaigns to contain information like:
- SIP headers your publishers include on incoming calls
- Progress through calls flows, real-time bidding, revenue recovery, and other tools Ringba uses to manage your calls
- Annotations you add to calls after they are complete
You can use tags to configure reporting filters and route calls.
See Reporting Tags.
tag routing filters
Rules that use a call's reporting tag values to determine whether a target is eligible to receive it. For example, a tag filter can define that a target accepts calls only from a certain state or publisher.
See Tag Routing Filters.
target
The call center receiving the call.
See Targets.
target dial insights
A report under Insights that shows how many dials, no-answers, busy signals, errors, and connections each target and ring tree target had during a selected time range.
See Target Dial Insights.
target group
Target groups let you associate related targets, such as partners that have multiple call queues, campaigns, or inbound numbers.
See Target Groups.
TCPA Shield
TCPA Shield checks incoming caller IDs against a list of known TCPA plaintiffs, litigators, and settlement seekers, and blocks calls from people on the list.
theme
The colors, labels, and branding you configure for your white-labeled portal using the white label theme editor.
timeline report
A chart at the top of the Reporting screen that displays the number of calls as bars over time, which you can group by year, month, week, day, hour, or minute.
See Timeline Report.
token
A placeholder you add to a pixel URL, ring tree request, or other outbound integration that Ringba replaces with the actual data from a call tag when it fires.
See Most Common Tokens.
tracking numbers
Phone numbers you create in Ringba to track information about a caller and route the call to a destination. When someone calls a tracking number, Ringba records attribution data and forwards the call according to your routing plan.
See Tracking Numbers.
U
URL parameters
A tool for letting landing pages, business tools, or partners' systems add information about a call to the URLs they ping. Ringba receives this data and stores it as a reporting tag on the call.
See URL Parameters.
user
An account with access to your Ringba portal, such as an admin, report-access user, publisher user, or buyer user.
See Users.
user group
A group of publishers or buyers you create so you can invite a single manager to view reporting or settings for all of the entities in the group.
See User Groups.
V
voicemail node
A call flow node that lets a caller leave a recorded message and notifies account admins by email when a message is left.
See Voicemail Node.
W
webhook
A webhook is a tool to let other systems or other people send data into your Ringba account.
See Webhooks.
white label
Ringba's feature set for controlling the look and feel of the portal your publishers and buyers see, including a friendly sign-in URL, a custom theme, and (optionally) a custom domain.
white list
A list of approved IP addresses that you exclude from a restriction — for example, the Ringba server IPs you allow through your firewall so pixels, ring trees, custom scoring, and SIP calls aren't blocked.
See SIP IP Whitelisting.