Tips for Using HasOffers Affiliate Management System with TSL Ping Tree

TSL Ping Tree > How To

HasOffers from is a fairly popular affiliate management and tracking system used by our customers. Following are some tips for using it with TSL Ping Tree.

Base Configuration

We recommend changing the following system settings from their default values.

Company > Customize Application > Tracking > Transaction ID Value

The default way that HasOffers produces session tracking identifiers – which it calls Transaction IDs – is to use a combination of IP Address, Date, and Offer ID to produce a Globally Unique Identifier such as 1010aabccb68bb1e8a76a04e27dc9a.

We recommend changing this setting so that it uses a Random Number at least while you are first getting your account established. Otherwise you will run into two problems. One is that IP Addresses can be shared by real visitors to your websites within a single day. Another is that you yourself will invariably be trying to test end-to-end tracking for a given affiliate and/or offer and once you get assigned an ID for your IP Address / Date / Offer combination you are stuck with it for the day. Having a new random number assigned for each clean request for a new ID – where you clear cookies from your browser before the next test – will allow you to produce additional sessions from the same IP Address on the same Date to the same Offer. Tracking cookies from HasOffer, our system, and any 3rd party system from your affiliate should keep things straight for production visits.

Company > Customize Application > Tracking > Enforce Conversion Referrals

We recommend you disable this option. When enabled it requires all conversion transactions that occur within an image, HTML, or JavaScript -based tracking pixel from within a visitor’s browser to be accompanied by an HTTP referrer URL. Most browsers will report a referrer however not all techniques for firing pixels, including some of the techniques used by TSL Ping Tree, will always do so. In addition, browsers and proxy servers can be made to strip out referrer URLs for the sake of privacy.

Company > Customize Application > Domain > Email Domain

Enable the Custom SMTP server and then complete all of the fields. Test that the email can be delivered to your own email address by using the ad hoc email feature in HasOffers located at the bottom of the form. You also might want to use various tools for checking whether your email looks like spam by sending from the HasOffers ad hoc email tool located at Company > Mail Room to the spam scoring service. One such free service can be accessed via email address

Setting Up An Offer for a Front Site

  1. We recommend that you create a one-to-one map between a HasOffers Offer and a TSL Ping Tree Promotion. You should set up the HasOffers Offer first and get an Offer ID from that system. If you like you can use that very same ID in your TSL Ping Tree account for the corresponding Promotion provided that you have not yet used it.
  2. For Conversion Tracking use the HTTPS iFrame Pixel if you have SSL (which we recommend). With this option then the corresponding Promotion Pixel in TSL Ping Tree will be as follows:  

    1. <iframe src="https://YOUR_HASOFFERS_HOST_NAME/SL2?adv_sub=${sp.Click ID}&amount=${sa.Revenue This Transaction}&transaction_id=${sp.Sub ID 1}" scrolling="no" frameborder="0" width="1" height="1"></iframe>

    Everything except for YOUR_HASOFFERS_HOST_NAME is to be entered literally, as-is, within your Promotion’s configuration in TSL Ping Tree.

  3. For the default Offer URL use our ClickThru URL: 


    YOURDOMAIN is from TSL Ping Tree. Replace it with the value that we assigned to you.

    SITEID is the domain name of your offer website where visitors are directed. Leave off the “https://www” part.

    PROMOTIONID is the corresponding Promotion ID in TSL Ping Tree.

    The remaining values in curly braces are to be left as-is.

  4. For Preview URL you should pick a landing page on your offer website. The domain should match the one used for the SITEID setting. If you happen to be split testing your traffic from within TSL Ping Tree and you are testing across multiple domains then just use the most popular or heavily weighted one.

  5. There are several options in HasOffers for determining payout rules. They must be made to match the settings in your TSL Ping Tree Promotion. Our terminology differs. Here’s how ours map to HasOffers.

    Pay Per Accept - pay X per accepted form submission to ping tree PT

    Select Cost Per Conversion (CPA) in HasOffers with the same amount, X, in each system.

    Pay Per Click - pay X per click

    Select Cost Per Click (CPC) in HasOffers with the same amount, X, in each system.

    Pay Per Submit - pay X per form submission to ping tree PT

    Select Cost Per Conversion (CPA) in HasOffers with the same amount, X, in each system.

    Pay On Bucket Tip - pay X when at least Y revenue is booked against the click

    Select Cost Per Conversion (CPA) in HasOffers with the same amount, X, in each system.

    Pay On Revenue Share - pay X% of the revenue booked real-time from ping tree PT

    Select Cost Per Sale (CPS) in HasOffers with the same percentage, X, in each system.

  6. For revenue we recommend using what HasOffers calls Revenue Per Sale (RPS) set to 100%.

  7. Placing custom tracking pixels for affiliates is tricky in any system. In HasOffers there are tools that affiliates themselves can use to place and test pixels. We recommend you give each affiliate his own login and you have them use these tools to place their custom pixels. You can also do this for them via the HasOffers Affiliates > Conversion Pixels / URLs screen. Important: If you configured your offer to only use SSL then the URLs in the pixels that you place must also use SSL. Otherwise you will get a cryptic error message from HasOffers.

    The basic strategy for testing a pixel involves using a test link that will be provided to you by your affiliate. Ideally you will follow this link from within a browser where you can clear all cookies before testing and where you have relaxed all of the privacy options that the browser may provide. Click on the test link given to you by the affiliate. If your offer and promotion are properly configured then you will wind up on one of the landing pages on your offer website.

    To fake a conversion you need to either render a page on your offer website with the conversion tracking pixel in it, or, if you have relaxed the HTTP referrer requirement as we recommended you can fake it by just using its core URL in your browser’s address bar, i.e. 

    1. https://YOUR_HASOFFERS_HOST_NAME/SL2?adv_sub=${sp.Click ID}&amount=${sa.Revenue This Transaction}&transaction_id=${sp.Sub ID 1}

    To get the necessary Click ID and the Sub ID 1 values you use your TSL Ping Tree account and our Reporting > Click Search screen. Search for the click that matches your test link. You can narrow your search by using your own IP address. If you do not know it visit something like in another browser window. Drill down into the details of the matching click to get the Click ID – not the Click UID – and the SubId1 values.

    For revenue you can just make up a number. This will report a conversion which you should later reject in HasOffers so that you do not accidentally pay it later.