iPath - Ads Tracking Software

Version 1.0

by N@@S



Thank you for purshasing your copy of iPath project!

iPath is an Ads Tracking System. iPath is the best way to create your own tracking software for your campaigns. Launch it in just 1 minute with ultimate features. It’s easy to install

If you have any questions that are beyond the scope of this documentation, please feel free to contact us on support@ipath.pro. Thanks so much!


When you download iPath on CodeCanyon, you get a zip folder which contains two subfolders in it:

  • The ipath folder which contains the main files that you need to upload on your server.
  • The documentation folder which contains the documentation you are actually reading.
Installing iPath is a strightforward process. It require only few basic notions of website management and no coding skills required at all. To do so, please follow these steps:
  1. Transfer the files to your server:

    First of all, once you have downloaded the zip file on CodeCanyon, just extract it where you want on your computer, then, upload the ipath folder to where you want to run your script under your hosting server (for example under "public_html" folder) and rename it whatever name you want for your project. This step require the use of a third-party FTP software. I really recommend you to download FileZilla. It is available for diffrent plateforms and easy to use.
  2. Create a Database:

    iPath require a database to store importing data. For this, you have one of two options. Either you create a new database that is specific for your iPath project, or to share an existen database with other projects but in this case you should imperatively define a unique prefix when asked for entering the database configurations in the installation wizard.
    In order to create database, You need to have previously setup database from the cPanel. Here is a good tutorial how to setup MySQL database in cPanel if you are not familiar with this.
    • Login to cPanel by accessing www.yourdomain.com/cpanel and navigate go MySQL Databases.
    • Create database first.
    • Create user and setup your password.
    • Add the user to database by selecting the database and the username.
    Make sure you have checked All privileged when adding the user to database.
  3. Run the installer wizard:

    Once done with the previous steps, all what you need to do is to visit the ipath location using your web browser to run the installer process by simply visiting your hosting folder URL (ex: http://www.yourdomain.com/) then follow the instructions on screen given by the installation wizard.
    • Step 1: Nothing to do here, we recommend to keep the default option for the installation type and just click the "start" button.
    • Step 2: You will need to pass the requirements in order to install iPath. If all the requirements are passed (green) then your elgible to install iPath, just click the "Continue" button. Otherwise, in case you failed to pass one or more of the requirements, we recommend you to contact your hosting provider asking them to enable the failed requirement on your server.
    • Step 3: Here, you have to populate the fields according to your database setup. . Also, you have to enter the "Site's URL" which is the URL under which you hosted the script. For example, if you will be installing it under a custom domain this will be like "http://www.yourcustomdomain.com/" (don't forget the last slash). Or, if your installation goes under a subdomain this field value will look like "http://myipathproject.mydomain.com/" or also like "http://www.mydomain.com/myipathproject/".
      In case you moved the placement of your script after installation and you want to modify this value, you can do so by changing the value of the variable $config['base_url'] in line #26 of the file application/config/config.php
    • Step 4: Okay! nothing weird here, just create you desired account credentials to use to login into the system. and hit "Continue" untill the "Completed" message shows up.
  4. Delete the installation folder:

    For security reasons, please make sure to delete the "install" directory inside the files folder.

How Does Affiliate Tracking Work?

Tracking is extremely important when it comes to affiliate marketing. Leads that are generated by an affiliate need to be accounted for accurately, in real-time and most importantly, through an automated process. Reliable tracking allows advertisers to assess how successfully their affiliate campaigns are performing. Two common types of tracking are cookie tracking and postback URL tracking. Deciding which one to use will depend on the nature of your affiliate program and your internal resources.

Cookies and Conversion Pixels

A tracking link used by an affiliate to promote various offers, includes a unique affiliate ID. When a visitor to a website clicks on that link, the affiliate ID is stored on their browser within a text file, known as a cookie. The cookie stays in the customer’s browser for a short period of time, such as 30 or 60 days, or until the cookie is cleared from the browser manually. This means that if the customer comes back a few days later and completes an action, the lead is still attributed to the original affiliate ID. A small piece of code known as a conversion pixel, is placed on the merchant’s page that loads up when a customer has completed the desired action. This could be a ‘thank you for purchasing’ or ‘thank you for registering your interest’ page. If a visitor clicks through an affiliate link and reaches the confirmation page, the pixel tracks this in the affiliate network as a sale or lead. It only requires a basic knowledge of html in order to set-up correctly. As an advertiser it is up to you how long you would like the cookie for your offer to last. A browser cookie is only tracked within the specific browser, so if the user opens a different browser and completes an action, it will not be tracked.

Postback Tracking

Postback URL tracking uses a server to server approach and is a very accurate method of tracking. However, it’s slightly more complicated than using cookies and therefore requires a little more technical know-how to set it up. If you are running offers on more than one affiliate network, then postback tracking is the best method to use. Postback or callback tracking as it is also known, stores information on the merchant’s server and this means that no code needs to be placed on the advertiser’s website. When a visitor clicks on the affiliate tracking link, the affiliate network adds an ID tag to the URL of the advertiser, so that when the visitor arrives on the landing page for the advertiser, their ID is updated in the URL. If a lead or action is then generated, the Merchant server sends this information back to affiliate network using the postback URL.

Getting Started

The concept of iPath is to give you, as an affiliate marketer, the aibility to track your campaigns hits and behavior in order to better analyse the results and improve the performances and thus the profits.

A campaign is associated into four main parts:
  1. An Affiliate Network
  2. An Offer
  3. A Traffic Source
  4. A Landing Pages

To illustrate the whole things, let's get over a practical example that cover the complete process to use iPath. In this example we are going to use an affiliation product from PeerFly
Suppose that we choosed the PeerFly's offer #12626 to promote as an affiliate. We also choosed AdWords as advertising network to generate targeted visitors to this offer.
In this case, our campaign will be composed from an affiliate network which is "PeerFly", a Traffic source which is "AdWords", an Offer which is the offer number #12626 in the PeerFly network (FPTraffic). Suppose that we are not going to use our custom landing page but the default offer's landing page. This is called a "direct link" landing page.
Our affiliation link generated for us is http://trkur4.com/{PublisherID}/12626
Now let's set up the whole campaign...
First, let's create a Traffic Source that we will use whenever we have AdWords as a promotion tool.
Go to "Traffic Source >> Create traffic source" menu.

You will find a question mark close to each option that need explanation, read them in case you are unconftable with any of the parameters to be given.
Here is a typical example for setting up AdWords traffic source with the whole set of tokens as provided by Google AdWords on their documentation pages. You can copy it if you plan to use AdWords as well.

After that, let's create our offer... Go to "Offers >> Create Offer" menu.

After filling up the fields with corresponding parameters, here what my offer page look like:

Once done, It is therefore the right time to actually set up the campaign through the menu option "Campaigns >> Create campaign":

The General info tab contains the most generic parameters for the campaign which should be straightforward to understand.
The second tab "Targetting settings" define the path to follow during a campaign hit. A "path" is the set of stops and destination links to point visitors to whenever they hit the campaign URL.
In our example, and as i said before, we are not going to use our custom hosted landing page, but rather, the default landing page of the offer. So that we will check the "direct link" option to let traffic redirected to the offer originnal link that we defined when we created the offer.

Then, of course, we should define which offers to associate with the present campaign from the previously created offers. Once done .. hit the "Finish" button and your campaign is ready to run. You will find the final campaign URL (the URL to promote) under the campaign manage page. Just go to "Campaigns >> manage campaign >> (choose your campaign from the list)". Then in the manage campaign page, scroll down to see the URL.


iPath project is still on its post-birth phase, we are counting on your experience and positive attitude with respect to the project idea to help us make it better for you. In case of any issue or bugs please report it with some details (and may snapshots) in the corresponding section of the iPath community page http://ipath.pro/community