Understanding how to create campaigns in Ringba is essential to your success. The campaign wizard is designed to walk you through setting up any type of campaign while only showing more advanced features when they are activated.
Before we dive into the wizard, it’s important to understand that to route or accept a call in Ringba you will need to create a campaign. Regardless of your use case, you will always want to create a campaign for each vertical, type of partnership, compliance requirement or other factors that may be important when pulling reports on your data.
The reporting interface has powerful sort options and grouping by campaign is one way to view your data in the most applicable way. If you have questions about how reporting words, it may be beneficial to review the Reporting Guide before setting up your first campaign. Seeing the data can be helpful in fully understand how or why you may configure a campaign a certain way.
The campaign wizard is broken down into 6 sections:
- General Information
- Call Routing
- URL Tags
- Tracking Pixels
This portion of the campaign wizard is for the basic campaign options and has 5 choices:
This is the name of your campaign that will show up throughout the interface in reporting, lists, the dashboard and other areas.
Tracking ID – Optional
If you need a reference code, hash, or ID attached to this campaign for webhooks, pixels or API calls, you can add it here for reference with any integration.
For example, in the United States we have a few popular formats:
The Ringba tag will replace each ‘n’ with the appropriate number in the phone number so the first example may look like: (212) 332-2323.
Should you prefer to display the number in local number format, you can leave off the country code and Ringba will automatically adjust so only the local number is shown regardless of the country your campaign is in.
Sometimes the same caller will repeatedly call a number causing a ‘duplicate’ call. Configuring how these calls are answered can help you increase your yield by sending callers to different targets causing multiple conversions, or streamline your customer service by sending callers back to the same targets that may have sold them something.
“Route normally” – send the caller to the correct target based on your routing rules set up later in the campaign wizard.
“Route to original” – send the caller to the target that received their call the first time the caller dialed the number.
“Route to different” – send the caller to a different target than the first time they called assuming there is one available.
Ringba can record your calls for quality assurance reviews, providing records to clients in the event of a dispute, agent training opportunities, and other uses. These recording can also be made available to publishers by adjusting their account permissions when they require it.
Enabling the first switch turns on recording.
“Wait for Answer” – turn on recording only when the call is answered, making it faster for QA.
“Trim Silence” – trim the silence at the beginning of a call also making it faster for QA.
Ringba allows you to create detailed routing plans for your calls to maximize your profit margins and reduce abandons. You can either add a single target, or a target group to your campaigns. A “target” is the receiving number of a call, and a “target group” is a group of phone numbers that are controlled by the same restrictions.
A target group may be a call center that has numerous inbound queues. Adding all of the inbound numbers to the same group allows you to apply concurrency settings and caps that apply across all of the numbers.
You would want to use target groups when working with a call center that takes calls from you on multiple campaigns or products, allowing you to prevent flooding their center with unanswered calls reducing abandons and waste.
Note: Ringba can make and receive both traditional phone network calls and VOIP calls with SIP.
To add a target to your routing plan, click the arrow icon: . An overlay will appear with options allowing you to configure the priority and conversion settings for the target.
Note: You can add a new target inside the campaign wizard, or through the targets menu, but it is not covered in this guide. Learn how to add targets and target groups.
Priority & Weight
Priority and Weight determine the order in which ringba will route calls if there are multiple eligible call centers. The weight is useful when dealing with large campaigns that have a large list of targets and groups. Weight allows for granular adjustment when adding targets without having to reorder them all.
“Call Length” – trigger a conversion when the call is at least a specific length of time.
“Call Successfully Connected” – trigger a conversion when a call is connected to a target.
“Webhook” – trigger a conversion when the target reports back a successful conversion.
The value of a conversion is the revenue you receive when a conversion happens. For instance if a partner paid you $10 for every call, you would configure the conversion value to be $10
The payout value is the amount of money you will pay to your publisher for every qualified conversion. For instance if you paid a publisher $7 for every call, you would configure the payout value to be $7.
This setting controls how you’d like Ringba to handle duplicate conversions and whether to credit your publishers for them:
“No Duplicates” – will not trigger conversion pixels or credit your publisher.
“Allow Duplicates” – trigger conversion pixels and will credit your publisher
Allow After” – only trigger conversion events after a specific amount of time has passed. Example: you will only count a conversion from the same caller once every 30 days.
Once you’ve added all of your targets and groups to the campaign, you can adjust the priority and weight inside the routing plan table anytime in the future by viewing a campaign.
Using URL Tags with your campaigns allows you to pass information directly into Ringba for reporting and integration with other software platforms. An example of information you may want to pass into Ringba would be an “affiliate ID” or “keyword”.
Passing specific information into Ringba about your users gives you the ability to sort and group by this data in the reporting interface. The more detailed the information passed into our system, the more detailed and flexible our reporting system becomes.
If you have not created the required URL Tag, click the “New” button. An overlay will appear with two options, the “Name” and “Category” of your tag.
The name is the exact case sensitive text phase associated with the data you wish to pass into the system.
For example, if the URL to your landing page is: http://www.website.com/?keyword=word the URL Tag name to capture the data should be “keyword”. Remember, URL Tag names are caSe SensiTive.
If you would like to send information to another platform or service, you will want to add a conversion pixel that gets triggered when a call becomes a qualified conversion. Ringba will “fire” the pixel and pass whatever information you need into the third party by activating your pixel URL and dynamically inserting whatever data you choose.
Note: Ringba supports both http and https postback pixels.
There 3 options where configuring your pixels:
1. “Fire On” is the event that will cause the pixel to trigger.
Answered – Fire when a call is answered by a target.
Incoming – Fire immediately when a user dials your number.
Completed – Fire when a call is completed and the caller hangs up.
Converted – Fire when a call has converted.
2. “Base URL” is the static URL portion of your pixel without a ‘?’.
3. “URL Tag” is the URL string or variable name that you want data passed to.
In the following URL “keyword” is a URL Tag:
Webhooks are endpoints that allow you to send data back to Ringba for performance based routing and enhanced reporting. After generating a webhook, you can pass Ringba back data using the Call Token assigned to every call routed from our system with SIP.
Ringba passes a unique token in every SIP header that you can capture and send back via your webhook to pass revenue data into our reporting.
There are 3 options for your webhook that have to be configured.
- “Call Token” is the variable where the webhook accepts the unique identifier for the call being reported.
- “Revenue Token” is the variable for passing in the revenue generated from this call.
- “Fire Pixels” when included in the webhook will cause Ringba to fire the pixels associated with the call being reported.
When configuring the webhook in your system, make sure to replace the variables in [brackets] with the dynamic information you would like to pass back into our reporting.
Call Token: “callid” = [callUUID] – Unique call ID
Revenue Token : “revenue” = [conversionAmount] – The revenue generated from the call.
Fire Pixels: “fire=true” – The configured conversion flag.
The final step of the wizard is for configuring your number selection. Campaigns can either have a single number, or a “number pool”. Number pools are groups of numbers that are rotated and assigned to users that visit your landing pages for a specific period of time, allowing Ringba to attribute calls to users behavior. If your campaign is for billboards, TV, or other offline advertising, you do not need a number pool.
Note: Campaigns can only be configured for one country.
After selecting the campaigns country, you will be presented with options specific to what types of numbers are currently available in our system. For instance, only certain countries have toll-free numbers available. Numbers assigned to a campaign can be local DID or toll-free, but never a mix.
Non-pool campaigns have the following options:
“Country” specifies the country you want phone numbers in for this campaign.
“Toll Free” is visible when the country you selected has toll free numbers available. When enabled Ringba will only allocate toll free numbers to your campaign.
“Area Code” specifies the desired area code for the numbers you are adding.
“Contains” lets you search for numbers that include any pattern of numbers you’d like. For example, entering ‘222’ will return only numbers that contain ‘222’
Number pool campaigns have the following additional options:
“Name” will be used to identify your number pool around the site. We suggest short names.
“Number Lock” is the amount of time in seconds a number is locked to a user.
“Idle Limit” is the amount of time in seconds a number is held for a user when they leave the browser open and are idle.
“Pool Size” is the number of phone numbers you’d like Ringba to allocate to your new pool. You can add more numbers to your pool later by editing the pool.