Skip to main content

Inbound Data Enrichment

Amanda Cross
Updated

Ringba’s Inbound Data Enrichment (IDE) can be used to add information about the caller so you can see it on the report and utilize it for routing logic rules. The information must be collected and relayed to Ringba before sending the call to Ringba’s publisher number.

For example; on a warm transfer, you can collect data such as zip code, age, name, health insurance or any other information that you need and this information will be sent to Ringba by sending a request and this will appear in Ringba reports as a tag. This tag can be used as a filter for your buyers and to improve your routing plans selection.

Requirements

Inbound Data Enrichment with Ringba requires:

  • Data must be pinged to Ringba in advance of the call connecting and will be stored for a maximum of 48 hours. The IDE impression lasts for 48 hours, as long as the call happens within this timeframe.

Note: If you're going to apply tag filters on a new tag that doesn’t exist already, you much create a URL parameter (see step 3 later in this article).

Example Flow

  1. Data is sent to Ringba along with the Caller ID.
  2. Call is routed to the Ringba number.
  3. Ringba combines the data we have received and tags the call in real-time.

Note: Your Publisher must already have the data before it can be passed to Ringba.

Setup Guide

Step 1

On your campaign, go to the Publisher section.

Step 2

Copy the link of inbound data enrichment URL by clicking on the icon next to the phone number. You will get something like the following:

http://display.ringba.com/enrich/PV18005551234?callerid=​<<E.164-CALLER-NUMBER>>&key1=value1&key2=value2

You will provide this URL to anyone interested in send you call data before we receive the call. The link is unique for each publisher number. Note: The "callerid" parameter is required by the system as it will be used to append the data provided through IDE to the correct call. Its format should not be changed.

Step 3

If you don’t have the tag in your report, it’s necessary to create one. Reporting Menu Name must be User and the other information is customized. If you already have this tag, you can skip this step.

Note: These are the only three steps that you need to do inside your Ringba account.

Step 4

Sending data into Ringba: Your Publishers will use the URL from the previous section to send an HTTP request with the data.

Important: Use the caller ID for the caller instead of <<E.164-CALLER-NUMBER>>

Note: We accept GET and POST methods but both have to be sent as query strings parameters meaning that it has to be send in the URL not in the request body.

The parameters Key1 and Key2 are placeholders for data you want to pass to us and we use as examples. We are using only Key1 and Key2 but it’s possible to add as many as you need.

For example, if you want to add the name and age information you will need to substitute key1 for name, value1 for the name you want to add, key2 for age and value2 for the age you want to attribute. In this example we used Postman.



The <Number> on the URL is information that appears with the copied link, the one that is the represented image on Step 2. The only fields you need to change are: caller ID, key1, value1, key2 and value2 so it can appear as the required information.

A valid URL would look something similar to this:

https://display.ringba.com/enrich/1361562116657514382?callerid=16195551234&NAME=JOHN&AGE=26

Once we have received the data, we are ready to attach it to the first call that comes in from the given caller ID. After the call comes in, it will be possible to see the information on your report. This data can also be used for routing logic or for passing to third-party tracker/server.

Inbound Data Enrichment FAQ

If you still have questions about Ringba’s Inbound Data Enrichment, contact our chat support team to get personalized support from Ringba engineers.

Related articles