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: Enter a label to appear at the top of the node on the canvas. This information is also helpful for identifying nodes in the Call Details Report.
Tip: Enter a descriptive name to help you differentiate this dial node from other pixel nodes when you are troubleshooting or reviewing the reporting later. - URL: Enter the URL of the pixel to fire.
- Max Fires: Enter the maximum number of times this pixel can be fired for a call in this call flow.
- Advanced: Toggle on this switch if you want to configure the pixel. See Advanced Options later in this article.
- Authorization: Toggle on this switch if the pixel URL requires a username and password. If you toggle on this switch, fields appear where you can enter the credentials.
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 location in the 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