Referral Goal Conversion checklist

Referral conversion happens when referee reaches specified goal conversion page. This could be the Thank you page of shopping cart, or post registration page  (for tracking registrations). This page must have the tracking code (with unique transaction id passed as ‘orderID’ parameter).

If conversion on goal conversion page is not getting tracked, please follow the checklist below.

Referral Goal Conversion checklist

In order to track goal conversion you must pass the associated unique orderid value in the tracking image pixel as highlighted below. The code has been explained in detail here (You must be logged into your Invitereferrals admin account to get your account specific tracking code without any XXXXXX ). The orderID value should be unique like – orderID in case of sale, emailid in case of registration etc.

Sale Event :

ir('track', {
    orderID: 'ABXHXXXXX',
    event: 'sale',
    email: 'example@gmail.com',
    fname: 'Mike',
    mobile: '9717XXXXXX',
    order_custom_val: 'platinum',
  purchaseValue:'1000'
}
  );

Register Event :

ir('track', {
    orderID: 'ABXHXXXXX',
    event: 'register',
    email: 'example@gmail.com',
    fname: 'Mike',
    mobile: '9717XXXXXX',
    order_custom_val: 'platinum',
  purchaseValue:'1000'
}
  );

Different Use Cases


A. Ecommerce Sites – Tracking referral sales

OrderID parameter – The transaction id of the the sale. The referral sale will not be tracked until this parameter is passed

Conversion page – Thank you page of the store. This is the page shown to user after success response from payment gateway.

B. Tracking referral registrations on site

OrderID parameter – Email id of the the customer in orderID parameter since it’s unique for each customer. Registration will not be tracked until this parameter is passed.

Conversion page – Post registration page of the site. This is the page shown to user after he has registered on site.

If you still face problems to track conversion, do not hesitate to write to us at alliances@tagnpin.com

3 comments