You use tracking pixels to send information from Ringba to another platform or service. The application triggers the pixel and sends the data you configure it to send. For example, you might want to send call data from Ringba to a CRM or an ad network like Google Ads or Facebook Ads.
You choose which event triggers the tracking pixel. When that event occurs, Ringba "fires the pixel.
In other words, it dynamically generates the information you specified in your configuration and sends it to the URL as URL parameters.
Note: Ringba supports both HTTP and HTTPS postback pixels.
This article contains the following sections:
Create a Tracking Pixel
Use the following step to create a tracking pixel:
- Navigate to Integrations > Pixels in the left navigation panel.
Note: You can also complete these steps within a campaign. See Campaigns. - Click the Create Pixel button. A form appears to configure the pixel.
- Complete the fields in the form:
- Name: Enter a name for the pixel. You use this name to identify the pixel later, such as when you add it to your campaign.
- Fire Pixel On: Choose the event that triggers the pixel. See Options for Pixel Fire On later in this article for more information about your choices.
- URL: Enter the URL to which you want Ringba to send the pixel data.
-
Advanced Options: Toggle this switch on to see addition fields to configure the pixel.
- HTTP Method: (Optional) Choose the HTTP method this pixel should use. You can choose GET, POST, PUT, or PATCH.
- Headers: (Optional): Enter the parameter name ("key") and the parameter value ("value") you want the pixel to send. Use the Token button to choose a call tag for the value field. Click the Add button. Repeat for each parameter you want to include.
- Authentication: (Optional) If the pixel requires a dynamic token, choose which authentication to use.
- Add Filter button: (Optional) Click this button to define a limit of which this pixel should fire based on a tag value. If you click this button
- Click the Create button to create and save the Tracking Pixel. If you click this button, a tool appears where you can define one or more rules. For more information on how to use this tool, see Tag Routing Filters.
Options for Pixel Fired On
You can choose any of the following options for the Pixel Fired On field:
- Incoming: The pixel is fired as soon as the call appears in the the Ringba platform.
- Connected (answered): The pixel is fired when the call is answered by a target.
- Completed: The pixel is fired as soon as the call is finished after connecting to a target.
-
Converted: The pixel is fired only if the call is converted.
Note: Payout may occur after conversion, in which case payout information is not yet available to pixels that use this option. If you need to send payout information, choose the Payout option instead. - Error: The pixel is fired if the call was marked as an error.
- Payout: The pixel is fired if the call was marked to have a payout to a publisher
- Finalized: The pixel is fired when the call ends. It doesn’t matter how (picked up, no answer, etc.)
- Recording: The pixel is fired when the recording is available to listen to. The recording usually takes a few seconds to appear after the call completes.
Add a Tracking Pixel to a Campaign
To add a tracking pixel to a campaign:
- Navigate to Campaigns and open the campaign where you want to add the pixel.
- Scroll to the Tracking Pixels section and click Add Pixel.
- Select the tracking pixel you want to add and click Add.
Pixels FAQ and Troubleshooting
How can I make my pixels more readable?
Try adding a description for your tokens. For example, you can put “RingbaCallId=” before adding the Call Id token. This way, when the pixel is fired, we know what each piece of information means. Another suggestion is to separate multiple tokens using & to make your pixel more readable. See the example in the following graphic:
Note: To send the parameters with the URL using the GET method, you must add a question mark ("?") between the endpoint URL and the parameters.
How can I verify my pixel fired correctly?
You can find the outcome of your pixel firing on the Call Details report on the Reporting screen. Use these steps:
- On the Call Details report, find a call that used the pixel you want to verify and click the down arrow on the left side of the row to expand it.
- Scroll to the Pixel Fire event and check the Response Status Code value, as in the image below:
If the value is a code in the 200s (such as 200, 201, 202, etc.), the pixel fired successfully. Any other value indicates an error occurred.
Note: If the pixel failed due to tag validation failing, you don't see a Response Status Code, but the Failed value explains which tag failed validation.
Why isn't my tracking pixel firing?
If you made the call and the pixel is not showing on your end, you should always first check if the Pixel Fire event shows on your Call Log under the events tag (please keep in mind the pixel fire is queued to be processed and might be registered on the logs after a while the call has completed). If it’s not there, the most probable cause is that the pixel has not been added to the campaign.
The tracking pixel fired but why does it show Fail Reason: Bad Request?
If this happens, you should check the documentation of the platform you are sending the information to. The request is not being accepted by the server as it probably doesn't follow the specifications. If the request Body has an array, make sure to implement the array with double brackets ("[[ ]]"); single brackets ("[ ]") in Ringba means you are opening a macro.
Is it necessary to whitelist any IP addresses when using pixels?
Our recommendation is to whitelist the IPs described in this link Pixels, Ring trees and Custom Scoring IP whitelist
Is it possible to increase the pixel timeout settings?
No, the pixel timeout cannot be customized. It is set to 10 seconds for all accounts.
What should I do if I need help with pixels?
If you have any questions or need additional help, please reach out to our support team via chat or email at support@ringba.com.