This article will cover the following:
- What is Session Regeneration?
- How to implement Session Regeneration in CAKE
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, what click a conversion is attributed to.
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 tracking mobile app installs, session regeneration is one tool you can use since cookies are not shared between a mobile browser and the App Store. When a user goes through the App Store, the ability to track the request ID that CAKE usually requires with cookie-less tracking is lost.
However, there are common data points that can be tracked between the click and the app launch, such as IP and/or User Agent, that can identify the traffic source that generated the install conversion.
When using certain Session Regeneration Types to track install conversions, modifications will need to be made to the conversion pixel so that we can use the data points to tie the conversion back to the click.
IP Only: CAKE will record the user's IP on the click but since the conversion pixel will be called server side, the pixel also needs to contain the user's IP so that we can match on it and tie the pixel fire back to the click.
Also, since the Request Session ID cannot be passed into the App Stores, the r= parameter on the postback url will not be used, thus can be removed.
Unique Key (s2-s5): If one of these Session Regeneration types are selected, the conversion pixel must be modified to pass back the subID field that is being used as the session regeneration type. Regardless of which subID field (s2-s5) the unique key is being passed into, the k (key) parameter will be appended to the pixel, as shown below:
*For more information on Mobile App Tracking, please visit the related article linked here