Phone Tracking of Affiliate Referrals …the RingRevenue Way

As I was consulting a client on how they can improve their affiliate program further, the question of leaks came up. In fact, if I were asked to pinpoint just one thing that always turns an affiliate away from a merchant,  without hesitation I’d say “leaks”. As explained in my Econsultancy article on the topic “a leak is a path to an untrackable action that the end user may make bypassing the route that provides for an affiliate remuneration.” A phone number prominently displayed on the merchant’s website is one of the most widely-spread leaks.

Now, while a merchant can choose to not display the phone number to affiliate-referred traffic, it is often better to keep the number up there (must research shows that it does instill consumer trust), but provide a way for affiliate referrals to be tracked even if/when a customer decides to call in.

One way is to place a string of script (which some affiliate networks make available to its merchants) next to the phone number on your website, so that when a customer calls in you can ask them if they see a “tracking code” next to the phone number. If there is one, this will tell you it’s an affiliate-referred customer, and the “tracking number” will match the ID of the affiliate who has referred them. Now, there are a couple of shortcomings of this method. In fact, it is to overcome these shortcomings that RingRevenue, for example, developed their technology.  Here’s what Rob Duva of RingRevenue has told me in our recent chat on the subject:

The process [of tracking phone orders by passing in an “affiliate ID” or “tracking code” to the advertiser landing page that would be displayed to the consumer] was flawed for 2 main reasons:

  • The consumer didn’t really have any incentive to mention the code when they called in (most of the time they don’t know why the code is there or that any affiliate is even getting compensated if they complete a purchase).
  • The merchant call center reps don’t really have any incentive to ask for the code (as it costs them more money for the transaction if they have to credit an affiliate) and in the case of lager call centers, training agents to ask for this on every call was something that wasn’t taking place.

We designed the RingRevenue platform to automatically issue unique phone numbers to individual affiliates.  The unique phone numbers essentially act as a unique affiliate ID or tracking code.  Affiliates can include these numbers in their ad placements up stream of the merchants landing page.  When a consumer calls the number the call is tracked in both their pay-per-call reporting interface as well as the merchant pay-per-call reporting interface.   If the merchant has included our “java script / web integration code” on their landing page, that script ensures that the unique affiliate phone number appears in place of the merchants main toll free number on the merchant landing page … so that the phone number the consumer calls is the unique affiliate phone number and can be tracked properly without the consumer or call center agents needing to do anything differently than they normally would.

Just to clarify, this post is in no way sponsored by RingRevenue. I just love their solution. They fully eliminate the risk of non-tracking, and at this time, I believe such solution to be the only 100% affiliate-friendly one. Every merchant who runs an affiliate program, and also takes orders over the phone, must consider it.

7 thoughts on “Phone Tracking of Affiliate Referrals …the RingRevenue Way”

  1. We utilize an internal system that can assign a phone number to an affiliate by ID and will populate when their cookie is active. We also use Ring Revenue for a solution for our network publishers. Both increased tracking and sales for our affiliates. Thanks for the great article.

  2. Hi Geno,

    This is great information – thanks so much for posting it.

    If I understand your post correctly, an affiliate manager would learn which affiliates to give phone-based sales commissions to by manually cross-referencing phone numbers stored in the merchant’s CRM with the buyers’ phone numbers as captured in Ring Revenue’s “pay-per-call reporting interface”.

    So the remaining risk to the affiliate in this scenario would be a lack of diligence on the part of the affiliate manager in doing that cross-referencing. And the other major risk would involve the buyer placing a call from a cell number or work landline number (which Ring Revenue captures), but giving a home landline number to the call centre when completing a purchase, so that RR’s interface and the merchant CRM don’t hold matching phone number data. Does that sound accurate?

    Thanks again, Shawn

    1. Hi Shawn –

      It’s actually not a manual process.

      Rather than trying to go into detail here to explain the process, check out these two short videos:

      The Advertiser’s Guide to Getting Started with Pay-Per-Call:

      The Publisher’s Guide to Getting Started with Pay-Per-Call:

      You’ll see in the videos how easy it is for an advertiser to set up their pay-per-call campaigns and how they go about determining what to pay an affiliate for a qualified call.


  3. Hey Geno,

    Hope you’ve been well. I think I saw you briefly at ASW ’13 in Vegas. Much better than ASE’12.

    I ran across this article and gave Ring Revenue a buzz. Have you seen any newcomers (Other than Mongoose Metrics) that you have heard good things about? Ideally one that might integrate with a CRM? Thank you.

    1. Jason, you were luckly then! 🙂 I was in Vegas for just about 24 hours then. Hope to, actually, shake your hand at one of these conferences.

      As far as other PPCall platforms go, there are Ring Partner, Ring2Media, ResponseTap, and a number of others out there. But, honestly, I haven’t worked with anyone but RingRevenue in the past; so cannot say/share much about these other platforms.

Leave a Comment

Your email address will not be published. Required fields are marked *