Understanding the CAKE Request ID
Section 1: What Is The Request Session ID?
The Request Session ID is a numerical value that CAKE generates and stores upon a click of a unique tracking link.
This numerical value is intended to be used with the CAKE Postback URL (S2S) for the purpose of tracking conversions or events. The Request Session ID can also be used in API's to make updates to existing conversions or events.
The Postback URL leverages the Request Session ID as opposed to a cookie like CAKE's other pixels. (iFrame, Javascript and Image)
Section 2: When Do You Use The Request Session ID?
The Request Session ID is primarily used in situations where a Postback URL (S2S) has been implemented with an advertiser. This form of CAKE pixel requires this value in most cases.
The Postback URL leverages the Request Session ID to track conversions or events in the absence of a cookie.
Postback tracking, or Server to Server tracking (S2S) is becoming more common in mobile tracking and offers that require additional security. This is a requirement with mobile app tracking in CAKE.
***Some Postback URL's will leverage a unique key (&k=) as opposed to the Request Session ID while tracking mobile app installs.***
Section 3: How Do You Use The Request Session ID?
Upon a click of a CAKE unique link, the Request Session ID will be generated and stored within CAKE.
To use this value for Postback URL tracking, however, this value must be appended to the advertiser's redirect link so that they can store this value and pass it back upon a conversion.
To pass the Request Session ID to your advertiser, use the Request Session ID token in the identified parameter within the Offer Link. See the example above.
***Click_ID is simply an example. You must communicate with your advertiser and ask them for the best parameter to pass the Request Session ID value.***
