Skip to main content

RedTrack

Amanda Cross
Updated

RedTrack is an ad tracking and automation tool you use to centralize your performance metrics. You can integrate your RedTrack account with your Ringba account to include your call performance in your RedTrack dashboards.

To integrate the systems, you must complete some steps in RedTrack to prepare your account to receive Ringba information. Then you are ready to configure Ringba and your landing pages to send the metrics.

Prepare Your RedTrack Account

The first step is to get your RedTrack account ready for the integrations. The steps to prepare your RedTrack account vary slightly depending on whether you're an affiliate or an advertiser. Either way, you add a custom tracking domain and configure custom conversions for RAWCall, AnsweredCall, and ConvertedCall to track the pay per call campaign.

See the Ringba and RedTrack integration guide for specific steps in preparing your RedTrack account.

You return to your RedTrack account later in this procedure, after several configuration steps in Ringba.

Configure Your Ringba Account

Configuring your Ringba account for the RedTrack integration involves the following steps:

1. Create a Number Pool 
2. Configure your Campaign to Use your Number Pool
3. Place the JavaScript Snippet on your Landing Page
4. Create a URL Parameter
5. Add the URL Parameter to your Campaign
6. Set up RedTrack clickid Transfer for No-Redirect Tracking
7. Create Pixels to Send the RedTrack S2S Postback Events
8. (optional) Pass the Conversion Payout in the Pixel
9. (optional) Use Custom Conversion Events with Tag Filters

The following sections describe how to complete these steps.

1. Create a Number Pool 

The RedTrack integration requires you to use Ringba's number pools feature. The number pools feature uses a JavaScript snippet on your landing pages to show each caller a different phone number from a pool of numbers. When the caller uses the specific number, Ringba knows which caller matches the information you gathered on your landing page.

manage_pools_screen.png

You create a number pool on the Numbers > Manage Pools screen. See the Number Pools article for step-by-step instructions.

2. Configure your Campaign to Use your Number Pool

Campaigns control every aspect of any call routed through Ringba. To configure your campaign to use numbers in the number pool you just created, you add a call tracking tag to the campaign. 

You add a call tracking tag to a campaign on the Campaigns screen. (If you need to create a new campaign, see the Campaigns article for step-by-step instructions.)

call_tracking_tags_section.png

Open your campaign and scroll down to the Call Tracking Tags section. Click the Add Call Tracking Tag button and complete the fields that appear. The procedure in the Number Pools article covers the steps for attaching a number pool to a campaign.

Important: Make sure you toggle ON the Capture User Data switch. The integration requires this setting. 

3. Place the JavaScript Snippet on your Landing Page

The JavaScript snippet from the call tracking tab replaces the default phone number on your landing page with a different number pool number for each visitor to the landing page.

In Ringba, you find the JavaScript snippet in the Call Tracking Tags section of the Campaign. Once you've added the call tracking tag, you can find the <> button in the Actions menu. Click it to make the snippet appear. Copy this snippet into your clipboard so you can later paste it into the HTML of your landing page.

install_call_tracking_tag_window.png

The procedure in the Number Pools article covers the steps for placing the JavaScript snippet on your landing page. 

Important: Make sure to paste the call tracking tag JavaScript snippet after the RedTrack Universal tracking script in the code of your landing page.

4. Create a URL Parameter

A URL parameter defines a token you plan to pass into Ringba as part of a URL. You use this URL parameter to pass the click ID as part of the RedTrack Offer URL. You can also create additional URL parameters if you want to include other kinds of information in the URL.

URL_parameters_screen.png

You create a URL parameter on the Integrations > URL Parameters screen. See the URL Parameters article for step-by-step instructions.

Important: RedTrack requires that you use the following values when you set up your click ID URL parameter:

  • URL Parameter: clickid
  • Reporting Menu Name: User
  • Report Name: clickid

Tip: You can create multiple URL parameters to include in your RedTrack Offer URL. Ringba captures all the parameters you include as tags. The following Offer URL contains additional parameters and RedTrack dynamic tokens:

https://test.offer.com?clickid={clickid}&country={country}

Creating a new URL parameter automatically creates a corresponding dynamic token:

 [tag:User:clickid]

You can use this token later for RedTrack S2S postback and to define routing logic in the Ringba by using Tag Routing Filters.

5. Add the URL Parameter to your Campaign

You add the URL parameter you just created to your campaign by opening your campaign on the Campaigns screen. Scroll to the URL Parameters section and click the Add URL Parameter button. The procedure in the URL Parameters article covers how to add a URL parameter to a campaign.

URL_parameters_campaign_section.png 

Since you added the call tracking tag to the campaign, Ringba automatically captures the clickid and other data included in the URL parameters. You can find this data for your calls on the Reporting screen. In the Call Details section of the screen, click to expand the call whose tags you want to review and click the Tags tab.

redtrack_call_details_tags_tab.png

6. Set up RedTrack clickid Transfer for No-Redirect Tracking

Copy the script below and paste it into the <body> element of your landing page:

<script>
(window._rgba_tags = (window._rgba_tags || [])).push({ type: "User", track_attempted: "yes" });
  var intervalId = setInterval(() => {
  if (window.rtkClickID != undefined) {
    (window._rgba_tags = (window._rgba_tags || [])).push({ type: "User", clickid: window.rtkClickID });
    console.log("Just ran the rtkClickID script to add Ringba tags: ", window.rtkClickID);
    clearInterval(intervalId);
    } else {
    console.log("rtkcid not defined yet");
    }
}, 500);
</script>

7. Create Pixels to Send the RedTrack S2S Postback Events

A tracking pixel is a feature in Ringba to send tag information to another platform or service, such as RedTrack. You create pixels on the Integrations > Pixels screen. 

pixels_screen.png

As part of the configuration, you enter the RedTrack postback URL in the URL field. The following is an example of a RedTrack postback URL:

https://test.offer.com/postback?clickid=[tag:User:clickid]&sum=[Call:ConversionPayout]&type=Lead

Important: Make sure to set the Fire Pixel On field to Incoming and include the clickid token, a payout token, and the type (Conversion or Lead) in the postback URL. 

You must inlucde the clickid, a payout token, and the type at a minimum, but you can add other dynamic parameters that you want to record in RedTrack. See the following article for full lists:

See the Pixels article for step-by-step instructions to create a pixel and add it to your campaign.

The pixel fires the RedTrack postback URL to send conversion data to RedTrack only if the following criteria are met:

  • RedTrack’s clickid is recorded
  • Ringba Pixel contains clickid=[tag:User:clickid]
  • Ringba Pixel contains RedTrack conversion type=Conversion or type=Lead

For the correct RedTrack-Ringba tracking, it is essential to add the clickid token. That being said, RedTrack also supports many other dynamic parameters such as sum for conversion payout, type for conversions type you would like to record in Redtrack, etc. See the full list here.
Ringba supports many additional dynamic tokens as well. Here is the list of tokens available on Ringba.

You can see the results of the pixel on the Reporting screen. In the Call Details section of the screen, click to expand the call, then scroll down to the Pixel Fire event.

8. (optional) Pass the Conversion Payout in the Pixel

Ringba offers two token options for the conversion payout:

  • [Call:ConversionPayout] contains the payout a publisher is credited for each conversion.
  • [Call:ConversionAmount] contains the revenue of the conversion.

RedTrack's sum parameter can match with a hardcoded value for the conversion, such as sum=10. If you hardcode the value, each postback-reported conversion is recorded in RedTrack with 10 revenue.

If you need the pixel to send the conversion revenue (ConversionAmount token), change the value in the Fire Pixel On field to Converted. Once the conversion occurs, the pixel fire and reports the Conversion revenue to RedTrack.

In other scenarios, the pixel still fires, but the actual conversion revenue does not replace the [Call:ConversionAmount] token. In this case, you can enter the required value manually with the sum parameter as described above.

See the Call Flows article for instructions on setting up your pixel as part of a call flow to pass the conversion payout.

9. (optional) Use Custom Conversion Events with Tag Filters

If you toggle on the Advanced Options switch when you configure your pixel, you can configure it to use custom conversion events. Pixels also support tag filters in your request to add more control over when the pixel fires.

When configuring a Ringba Pixel:

1. After you toggle on the Advanced Options switch, choose GET in the HTTP Method field.

2. Under Tag Filters, you can specify how and when to fire the pixel

For example, you could set a tag filter for the pixel to fire only when the Call Length is greater than 45 seconds.

When you configure your pixel this way, Ringba's tracking tag captures the RedTrack clickid from the Offer URL when a visitor clicks through your RedTrack campaign funnel. You can find the value on the Reporting screen. Once the call converts (or other action that triggers S2S postback happens), the pixel fires, sending the conversion details to RedTrack.

RedTrack Integration FAQ and Troubleshooting

After setup, my clickid still wasn't captured. What can I do?

Sometimes the relative positions of the scripts on your landing page can cause the clickid not to be recorded. To fix this, try moving the call tracking script (from step 3 in this article) from the landing page's <head> element to the <body> element, after you RedTrack script.

What should I do if I need help with the RedTrack integration?

If you have any questions or need additional help, please reach out to our support team via chat or email at support@ringba.com

Related articles