CallRail Integration

Introduction

Convert.com allows you to A/B test your website. In order to get a true analysis of how your visitors convert, you can track the calls to your tracking numbers as conversions. 

Use this article to learn how to:

  • Use Zapier to integrate CallRail with Convert
  • See your CallRail phone calls as conversions in your Convert account

Getting Started

In order to see your calls as conversions in Convert, you will need the following:

  1. A Convert account with an active experiment
  2. Your Convert project_id, customer_id, experiment_id, variation_id(s), and goal_id (see below)
  3. A Zapier account to connect CallRail with Convert

Convert Variable Names

project_id

This can be found in "Project Settings". This field combines the account ID and project ID separated by an underscore.

For example, if project_id is 1111_2222, then 1111 represent the customer_id and 2222 represents the project_id.

customer_id

customer_id as described in the previous step.

experiment_id  

Experiment ID can be found inside the Experiment report, clicking on the "Report Settings" icon.

variation_id

Each version of your A/B test has a separate Variation ID. It can be found by doing a live preview for each specific variation and picking up the number after the convert_e query parameter inside the preview URL.

For example, if the preview URL is http://staging.convert.com/?convert_action=convert_vpreview&convert_v=1002704493&convert_e=10023753, then the variation ID is 10023753.

goal_id

Goal ID can be found in "Goals Overview" by clicking on the name of the goal.

Create Phone Numbers

Create a CallRail phone number for each A/B variation. Give each number a descriptive name so you will know which experiment and variation they belong to. (Example: "Home Page - Original" and "Home Page - Long Copy")

Create a Goal

Create a new "Javascript Triggered Goal" in Convert. Give it a descriptive name, like "Phone Call".

Add Goal to Experiment

Go to your experiment and add your goal to it:

Create Zapier Trigger

Click Create a Zap and build a Zap with the following settings:

  1. Trigger: "Web Hook" (Catch Hook), Action "Zapier" (Delay Trigger).
  2. Make note of the Webhook URL in step 2.
  3. Select your own Zapier account as the account to use.
  4. Leave the filters blank.
  5. Create a name for the Delay Trigger. The name is up to you, just remember it -- you will need it shortly. Set the delay to a low value. 1 minute should be sufficient.
  6. Enable the Zap, name it, and "Make Zap Live".

Configure CallRail Webhook 

Set up your Webhook and place a test call.

  1. Click Settings at the top of the page.
    settings.png
  2. Choose the company you’d like to add a webhook.

    company_copy.png
  3. Select All Integrations from the Integrations menu on the left.
    screenshot_479.png
  4. Choose Webhooks from the list of available integrations.
    screenshot_623.png
  5. Paste the Webhook URL you gathered from step 2 in your Zapier setup above.
  6. Click Save at the bottom of the page.
    Save_copy.png
  7. Call one of your company's tracking numbers, which will trigger the webhook and populate some data you need in the next step.

Report Conversion to Convert

Click "Create a Zap" and build a Zap with the following settings. Repeat these steps for each variation in your A/B test.

  1. Trigger: "Zapier" (Delay Trigger), Action "Web Hook" (GET).
  2. Select your own Zapier account as the account to use.
  3. Filter your delayed triggers:
    1. Put the name of the Delay Trigger that you created previously here.
    2. Set up a Custom Filter for "data__trackingnum" "(text contains)" "4045551212", where "4045551212" is the tracking phone number that corresponds to one of your Convert test versions. Do not put any dashes or other special characters here -- enter only numbers.
  4. Set your GET URL.  It will look something like this: 
    http://[project_id].track.convertexperiments.com/track/?c=[customer_id]&p=[project_id]&e=[experiment_id]-[variation_id]&g=[goal_id]&ga=1, but substitute in the appropriate variables that you collected from Convert.  Leave the other settings default or empty (JSON = no, JSON key, data, auth, headers).
  5. Give your Zap a descriptive name (perhaps include the name of the test and the variation, like "Send Conversion - Home V1 (Blue)") and "Make Zap Live."
Have more questions? Submit a request

Comments