Advanced Guide: Ringba to CallGrid RTB with Confirmation Step

Hey! This is an advanced guide for setting up a Ringba to CallGrid RTB integration.

Step 1: Follow the Standard Setup

First, you need to start by following the original guide linked here: https://callgrid.com/knowledge-base/posting-bids-from-ringba-to-callgrid-using-rtb

Set up your RingTree Target exactly as described in that guide. Once the standard mapping is complete, proceed to the steps below to configure the differences.

Step 2: Understanding the Difference

To set up this confirmation, we are changing how CallGrid interacts with Ringba. Instead of acting as a "ping-only" setup, CallGrid will now act as a "ping/post" specifically for this Grid ID.

Step 3: Enable the Confirmation Step & Parse the Bid ID

After you run the initial test request (using the +15551234567 test phone number) from the normal guide, you need to enable the confirmation features:

1. Scroll down to the bottom of the page and toggle ON the Confirmation Request step.
2. Toggle ON the Bid ID Required setting.
3. Click the Bid ID Parsing drop-down and select id.
   

Step 4: Map the Dynamic SIP Address

Next, we need to temporarily hardcode an example bid ID to run a test and map the SIP address.

1. In the URL field under the Confirmation Request section, enter the test URL containing an example bid ID (e.g., https://bid.callgrid.com/api/bid/confirmation/cmbidlwefnn09342t3nklnelkr).
2. Click the Run Request button.
3. Once the response loads, click the Dynamic Number/SIP Parsing drop-down and select dynamicSipAddress.

Step 5: Replace with the Ringba Macro

Now that the mapping is complete, we need to swap out the hardcoded test ID with a dynamic macro so Ringba passes the correct ID on every live call.

1. Change the URL by replacing the example bid ID with the Ringba [bid-id] macro.
2. Your final URL should look like this: https://bid.callgrid.com/api/bid/confirmation/[bid-id].

Once that's done, you can go ahead and save your RingTree Target. You should be all set!