This article covers:
- What is Session Regeneration?
- How to Implement Session Regeneration
What is Session Regeneration?
Session regeneration allows you to use a criteria other than the system default of placing cookies on the user's machine as the basis for counting unique clicks, and in turn, the attribution of a click conversion.
Where to Specify Session Regeneration Criteria
Session Regeneration Type
Session Regeneration Seconds
Session regeneration duration is set to a maximum of 1 day (86400 seconds). This means that all clicks with the same information for the selected session regeneration type will be tracked by CAKE as the same click.
For example: if you select IP only and 86,400 seconds, all clicks from the same IP within one day will be counted as the same click. Duplicate clicks will be tracked both in your admin click report as well as the Affiliate Portal click report by clicking on the number of clicks in the far right column.
Session Regeneration and Mobile App Install Tracking
When you are using a custom session regen type to track conversions like this, you will need to modify your pixel as well so that we can use that value to tie the conversion back to the click.
IP Only: Unless you're using a postback, we will record the user's IP on the click and the conversion so you can remove the reqid parameter altogether with no other parameters added.
<iframe src="http://trackingurl.com/p.ashx?o=123456&t=TRANSACTION_ID" height="1" width="1" frameborder="0"></iframe>
ONLY when using a postback, since the postback calls will all be coming from your server IP and not the user's IP, you will need to pass back the user's IP in the pixel like this:
Unique Key (s2-s5): You must modify your pixel to pass the subID field that you're using as your session regeneration type. Regardless of which subID field (s2-s5) you are passing the value into, you will use the k (key) parameter in your pixel like this:
<iframe src="http://trackingurl.com/p.ashx?o=123456&k=UNIQUE_VALUE&t=TRANSACTION_ID" height="1" width="1" frameborder="0"></iframe>