Zapier connects to all your favorite apps and helps organize all your third-party tools. Using Webhooks in Zapier, you can integrate Ringba with your existing technology stack.

This article contains the following sections:

• What Is Zapier?
• Create a Webhook Zap in Zapier
• Create a Tracking Pixel in Ringba to Send Data to Zapier
  • Special note about Fire Pixel On events
  • Using Tokens in the URL
  • Running a Test
• Use Zapier to Pass Ringba Data to Another Tool
• Testing It All Together

What Is Zapier?

Zapier is a web app that lets you easily make connections between apps that normally don't talk to each other. These connections are called "zaps," and they use actions and triggers to pass data between different apps. You can learn about Zapier and sign up for an account at zapier.com.

This article steps through the process of setting up a zap to send call data to Zapier, then pass it on to a third product. The steps include:

• Setting up the zap in Zapier to accept the data
• Setting up a pixel in Ringba to send the data to Zapier
• Setting up the third product (in this example, Google Sheets) to accept the data
• Setting up the zap to send the data to the third product 
• Testing the whole process

To follow along with these steps, you must have:

• a Ringba account
• a Zapier account
• an account in the third software product

Create a Webhook Zap in Zapier

First you need to create a zap in Zapier. Use these steps:

1. Log in to your Zapier account and click Create, then choose Zaps from the menu that appears.
   
   A work canvas appears.
   
2. Click Trigger, then choose Webhooks from the menu that appears.
   
   A window appears open to the Setup tab.
3. Click the Trigger event field and a list of options appears. Choose Catch Hook, and then click Continue.
   
   The window moves to the Configure tab.
4. Leave the field blank and click Continue.
   Tip: You can click the Pick off a Child Key field label for more information about this field. 
   
   The window moves to the Test tab.
5. Click Copy to copy the webhook URL. You use this URL in Ringba in the next section when you create a tracking pixel.
   

Create a Tracking Pixel in Ringba to Send Data to Zapier

Once your Zap is ready to accept data, you use the URL to set up a pixel to send the data. Use these steps:

1. Log in to your Ringba account.
2. Open the campaign you want to send data from. Scroll down to the Tracking Pixels section and click Add Pixel to create a new tracking pixel for your Zapier integration.
   
3. Complete the fields:
   • Choose Option: Click Create New. 
   • Name: Enter a name for the pixel to help you identify it later.
   • Fire Pixel On: Select the event that triggers the postback pixel to fire. 
     Tip: See the Special Note after this section for more information about Fire Pixel On events.
   • URL: Paste in the URL you copied at the end of the previous procedure. Add tokens as placeholders for the data you need to send with your pixel. 
     Tip: See the Using tokens in the URL section later in this article to help you configure tokens.
4. Click the Create button.

5. Toggle on the Advanced Options switch to show additional fields. Complete these fields:

   • HTTP Method: POST
   • Content Type: application/json

   

   You can pass additional data in your request by including custom headers and values. You can also use Tag Filters to only trigger your request when specific criteria is met.

Special note about Fire Pixel On events

In the Fire Pixel On field, you choose the event in the lifecycle of the call that triggers Ringba to send information through the pixel to Zapier. Valid options are:

• Incoming: Fire the pixel as soon as a call arrives in Ringba.
• Connected (Answered): Fire the pixel as soon as a target answers the call.
• Completed: Fire the pixel as soon as the call is complete.
• Converted: Fire the pixel only if the call converts.
  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: Fire the pixel if the call is marked as an error.
• Payout: Fire the pixel if the call was marked as having a payout to the publisher.
• Recording: Fire the pixel as soon as the recording is available to listen to. The recording usually takes a few seconds to appear after the call completes.
• Finalized: Fire the pixel when the call ends. It doesn't matter how (connected, no answer, etc.)

Since the events occur at different times, the event have different data available to them. Make sure to choose an event that happens after your call has the information you need to send through the pixel. For example, you can’t choose Incoming and expect to send call cost information because that information does not exist yet when the call first arrives in Ringba.

Using tokens in the URL

After you paste in the webhook endpoint URL from Zapier, you must add the tokens to the URL. Tokens tell Ringba to replace the placeholder with the actual data from the call. See our Most Common Tokens for ideas on data you can include.

You should add a token for each piece of information you want to include when you pass data to Zapier. Tokens use particular formatting. At the end of the URL, you add:

• ?
• the token name
• =
• [instructions on where to get token value]  

https://hooks.zapier.com/.../.../.../?Name=[CallerName]

Name is just the name of the data you're sending to Zapier. [CallerName] is a bit of instruction that tells Ringba to replace [CallerName] with the value of the CallerName tag. You must include the token name in square brackets.

Tip: If you want to add multiple tokens, just add & followed by the next token name=[token value]. Do not add more than one ? in the URL.  

Example URL

https://hooks.zapier.com/.../.../.../?DateTime=[Call:CallDateTime]&CallID=[Call:InboundCallId]

For this example, an Incoming call is the trigger event that fires the pixel. The tokens include the date/time and inbound call ID in the information that goes to Zapier.

Running a test

At this point, if you want, you can test what you have so far. Run a sample test by copying your completed URL with tokens and pasting it in your browser address bar and press enter. Go to your Zapier account and you can see that the Zapier webhook catches your data.

Use Zapier to Pass Ringba Data to Another Tool

Now that you can pass data from Ringba to Zapier, you can send that data to any other supported third-party tool. Just go back to Zapier, open the Zap you created before, and add an Action to configure the zap to send the data Zapier receives from the pixel to another tool.

If you want to try a simple exercise, use the following steps to set up Zapier to receive the data from the pixel and then send it to a Google Sheet. Before you begin, you should create a Google Sheets file to hold the data you send. Create a column header for each piece of data you want to send with your pixel.

1. Open the Zap you created previously and click Action.
   A list of tools and apps you can connect to appears.
2. Choose Google Sheets.
   
   A window appears open to the Setup tab.
   
3. Complete the fields:
   
   • Action event: Choose Create Spreadsheet Row.
   • Account: Log in to the Google Account where you want the Google Sheet to be updated.
4. Click Continue to show the Configure tab:
   
5. Complete the fields:
   • Drive: Choose the drive that contains the Google Sheets file you want to update.
   • Spreadsheet: Choose the Google Sheets file you want to update.
   • Worksheet: Choose the worksheet within the Google Sheets file you want to update. 
   • <column name>: You see each of the column names from the spreadsheet here for you to map to a parameter in the URL. If you already sent a test query from your pixel to Zapier, you should see the URL parameters to choose from when you click the + button on the right side of the field.
6. Click Test step to move to the Test tab:
   
7. You can confirm it worked by checking your spreadsheet.
   
8. When you are ready, click Publish to make your Zap live.

Testing It All Together

You can test real call data going from Ringba to Zapier and on to the third-party tool. Just call a number in your Ringba campaign where you created the pixel.

If you set up the example covered in this article, the pixel fires on Incoming, so the pixel fires as soon as your call arrives in Ringba. It sends the data to Zapier, which then sends it into the Google Sheet. You can check your spreadsheet to see your Ringba data passed through Zapier.

The following image shows what the pixel firing looks like in the Call Details Report in Ringba:

While this image shows what the data looks like in the Google Sheet.