This Ruby on Rails web application shows how you can use Twilio to track the effectiveness of different marketing channels.
This application has three main features:
- It purchases phone numbers from Twilio to use in different marketing campaigns (like a billboard or a bus advertisement)
- It forwards incoming calls for those phone numbers to a salesperson
- It displays charts showing data about the phone numbers and the calls they receive
In this tutorial, we'll point out the key bits of code that make this application work. Check out the project README on GitHub to see how to run the code yourself.
Call tracking requires us to search for and buy phone numbers on demand, associating a specific phone number with a lead source. This utility class uses the twilio-ruby helper library to search for phone numbers by area code and return a list of numbers that are available for purchase.
Now let's see how we will display these numbers for the user to purchase them and enable their campaigns.
We display a form to the user on the app's home page which allows them to search for a new phone number by area code. At controller level we use the
TwilioClient we created earlier to actually search for numbers. This will render the view that contains a list of numbers they can choose to buy.
We've seen how we can display available phone numbers for purchase with the help of the Twilio C# helper library. Now let's look at how we can buy an available phone number.
purchase_phone_number method takes a phone number as its sole parameter and uses our Twilio API client to purchase the available phone number our user chooses.
If you don't know where you can get this application SID, don't panic, the next step will show you how.
Once we search for and buy a Twilio number, we need to associate it with a lead source in our database. This is the core of a call tracking application. Any phone calls to our new Twilio number will be attributed to this source.
So far our method for creating a Lead Source and associating a Twilio phone number with it is pretty straightforward. Now let's have a closer look at our Lead Source model which will store this information.
LeadSource model associates a Twilio number to a named lead source (like "Wall Street Journal Ad" or "Dancing guy with sign"). It also tracks a phone number to which we'd like all the calls redirected, like your sales or support help line.
As the application will be collecting leads and associating them to each LeadSource or campaign, it is necessary to have a Lead model as well to keep track of each
Lead as it comes in and associate it to the
The backend part of the code which creates a
LeadSource as well as a Twilio Number is complete. The next part of the application will be the webhooks that will handle incoming calls and forward them to the appropriate sales team member. Let's us see the way these webhooks are built.
Whenever a customer calls one of our Twilio numbers, Twilio will send a POST request to the URL associated with this action (should be
We use the incoming call data to create a new
Lead for a
LeadSource, then return TwiML that connects our caller with the
forwarding_number of our
Once we have forwarded calls and created leads, we will have a lot of incoming calls that will create leads, and that will be data for us but we need to transform that data into information in order to get benefits from it. So, let's see how we get statistics from these sources on the next step.
One useful statistic we can get from our data is how many calls each
LeadSource has received. We use the Active Record Query Interface to make a list containing each
LeadSource and a count of its
That's it! Our Ruby on Rails application is now ready to purchase new phone numbers, forward incoming calls, and record some statistics for our business.
If you're a Ruby on Rails developer working with Twilio, you might also enjoy these tutorials:
Put a button on your web page that connects visitors to live support or sales people via telephone.
Connect your callers to an IVR (interactive voice response), allowing them to make selections about how their call should be routed.
Thanks for checking this tutorial out! If you have any feedback to share with us please contact us on Twitter, we'd love to hear it.