The Pixel node gives you the ability to send and fire pixels based on the call flow. For example, you can use this node to fire a pixel if the dial node fails and include specific information about the caller.
- Node Name: A label that will be populated on top of the node with the selected name. This information will be available in the call reporting.
- URL: The URL of the pixel to fire.
- Max Fires: The maximum number of times this pixel can be fired.
- Advanced: Advanced Setting for the pixel. Check the section below for more info about our advanced options for pixels.
- Authorization: Basic Authorization settings for the pixel. If the URL requires any authorization to be sent in the header, you can toggle this option on and add the hardcoded value for the Username and the Password.
Advanced Options
The default Method and Content Type for pixels are "GET" and application/json, respectively, but if you want to customize it, you can select other available ones along with a request body and custom headers if needed.
Additional Information about the Pixel Node
The Pixel Node works similar to the regular Ringba Pixel. A key difference is that instead of being triggered on events like incoming, completed or converted call, the Pixel node is triggered based on the selected call flow. In this example, the pixel is being fired if the caller passes through the Voicemail node.
Learn more: To learn more about Ringba pixels, please check our knowledge base: Pixels