This article will cover:
- What Is Ringba?
- Understanding Ringba Campaigns
- Understanding Ringba's Payout Settings
- How Do I Track A Call Without A Click?
- How To Create A Ringba Tracking Pixel
- How To Apply A Ringba Tracking Pixel To A Ringba Campaign
- Ringba Tracking Pixel: The Hardcoded Method
- Ringba Tracking Pixel: The Dynamic Method
- Optional: How To Pass The Payout
What Is Ringba?
Ringba is an inbound call tracking and analytics platform for marketers, brands and pay per call.
Although Ringba does not require a publisher with payable events to be configured, that is the portion of the Ringba workflow that this article will be focused on.
As the owner of the Ringba account, or a CAKE customer sending traffic to an advertiser leveraging Ringba, this article will walk you through how to trigger conversion events in CAKE upon a payable action from Ringba.
Understanding Ringba Campaigns
A Ringba Campaign is the general set of configurations and rules that can be applied to one or multiple publishers.
For integration purposes, we recommend a 1:1 relationship between a CAKE campaign and a Ringba Campaign where there is only one publisher associated.
This recommendation is due to the configuration of the tracking pixel.
Understanding Ringba's Payout Settings
Within a Ringba Campaign lives the Default Payout Settings.
This article is focused on tracking conversions in CAKE when a payable event has occurred in Ringba.
Ringba's payout settings are located within the Campaign tab and allow users to configure one or multiple payout events. These payout events will be leveraged with Ringba's tracking pixel feature to trigger the CAKE Postback URL.
They also enable multiple CAKE events to be tracked upon different payout events in Ringba.
How Do I Track A Call Without A Click?
This article is focused on a workflow where an affiliate in CAKE has been issued a phone number from Ringba. In this scenario, the end user has called the phone number and has initiated a call.
In this scenario, there is no click. Usually, this is problematic because CAKE relies on a cookie or the Request Session ID.
Instead, Ringba will leverage CAKE's Clickless Postback URL when a payable event has been triggered.
This version of the Postback URL is unique in that it only requires you to identify the CAKE Campaign ID within the query string.
In the next section, we will discuss how to format the Clickless Postback URL with Ringba parameters and tokens.
The CAKE Clickless Postback URL is not enabled by default. Please request for this feature to be enabled through technical support or your client success manager.
How To Create A Ringba Tracking Pixel
To create a Ringba Tracking Pixel, follow these steps:
- Click the Integrations menu option
- Click Pixels
- Click Create Pixel
- Insert a name for the pixel
- Select Payout from the Fire Pixel On dropdown
- Insert the CAKE Clickless Postback URL in the URL field
The e= parameter will leverage the Event ID from the CAKE Offer.
The t= parameter is CAKE's transaction ID and allows you to receive a unique User ID, Lead ID, or in this case, a Call ID.
The campid= parameter is the CAKE Campaign ID. This value can be hardcoded or dynamically inserted using RIngba tokens.
We will discuss both methods in the following sections.
How To Apply A Ringba Tracking Pixel To A Ringba Campaign
Once you have created the tracking pixel, you will need to apply it to the associated Campaign.
To assign the tracking pixel, follow these steps:
- Click the Campaigns menu option
- Click on the Campaign
- Scroll to the bottom and find Tracking Pixels
- Click Add Pixel
- Select the pixel from the dropdown
- Click Add
Ringba Tracking Pixel: The Hardcoded Method
There are two methods for configuring the CAKE Clickless Postback URL when it comes to the CAKE Campaign ID.
You can either hardcode the Campaign ID into the tracking pixel or you can leverage a dynamic token to populate the Campaign ID upon conversion.
The hardcoded method requires that you create a unique Ringba tracking pixel per Campaign.
The alternative method requires that you create a single Ringba tracking pixel and then leverage the Tracking ID parameter within the Ringba Campaign.
To hardcode the pixel, find the ID of the Campaign in CAKE and place it into the Campaign ID parameter on the Clickless Postback URL.
Ringba Tracking Pixel: The Dynamic Method
The dynamic method of creating a Ringba Tracking Pixel leverages the Tracking ID parameter within the Ringba Campaign.
Once you have created a new Campaign in Ringba, assign the CAKE Camapaign ID to the Tracking ID parameter.
The Tracking ID value will be dynamically inserted into the Campaign ID parameter on the tracking pixel leveraging a Ringba token; [tag:Campaign:TrackingID]
Optional: How To Pass The Payout
If calls from Ringba are going to be paid at a dynamic price, instead of a static CPA, you will want to pass the payout on the tracking pixel. This payout will become revenue in CAKE for this campaign.
To pass the Ringba payout on the tracking pixel, append p=[Call:ConversionAmount]