How to Track Mobile App Campaigns (CPI)

CAKE has two methods of tracking In App Advertising, by use of the UDID Parameter or Session Regeneration.

The processes below will walk you through the scenario where the consumer is in an application and clicks on an advertisement.

In App Advertising allows an Affiliate to extract a unique value from the consumer's phone, the value itself will depend on the user's type of device. One example of a Unique Device Identifier is the IDFA.

The unique device ID should be passed in the UDID parameter of the CAKE Unique Link as displayed above.

*For information on the best ID to use in this UDID field please see our Best Practices documentation here.

The UDID can be passed onto the query string by using the #udid# token in the Offer link or Creative Offer link within CAKE. This token can also be found under the Setup maintab > Show Tokens card.

Finally, CAKE will look to match the UDID value passed on the click to the UDID value received later on the postback url, that will record the conversion/install.

An alternate method of tracking mobile application installs is the use of the Session Regeneration tool found on the Offer card > Attribution tab.

Session Regeneration Seconds: This is the "window of opportunity" where a Conversion/Install can be tracked. This "window" is from the moment a consumer clicks the CAKE Unique Link to the time the Application is first opened on their device where the Conversion/Install Postback is sent to CAKE. Today, the maximum time CAKE will track this installation is 86,400 seconds, or 24 hours based off of IP Session Regeneration or 30 days for Sub ID Session Regeneration types.

Session Regeneration Type: This defines the unique tracking key that will be used on the Unique Link and the Postback URL.

• IP Only: Selecting IP Only will limit CAKE to track application installs based on the IP of the click and the IP passed on the Postback URL.
• IP + User Agent: CAKE must match the IP Address and the User Agent of the click to the Postback URL. Note: This type is not recommended as the User Agent in the mobile browser is not the same as the User Agent from the App.
• IP + Device:
• IP + Device/User-Agent:
• IP + Sub ID: CAKE must match the IP Address of the click and on the Postback URL. In addition, a unique tracking key must be passed in on Sub ID 2, 3, 4, or 5 and must be passed back into CAKE in the UDID parameter of the Postback URL.
• Sub ID only: CAKE ignores the IP Address of the consumer's phone and only looks at a unique tracking key being passed in on the click in either the Sub ID 2, 3, 4 or 5 parameter and then returned on the Postback URL in the UDID parameter.
• Sub ID 5 Only Fallback to IP Only: CAKE will attempt to track a Conversion based on a unique tracking key being passed in on the s5 parameter of the Unique Link. If CAKE is UNABLE to track based on s5 value, it will attempt to match the IP Address of the click with the IP Address passed in the IP parameter of the Postback URL. Note: This type is highly recommended for mobile app tracking.
• Sub ID 5 Only Fallback to IP + Device: CAKE will attempt to track a Conversion based on a unique tracking key being passed in on the s5 parameter of the Unique Link. If CAKE is UNABLE to track based on s5 value, it will attempt to match the IP Address and the Device of the click with the IP Address passed in the IP parameter of the Postback URL and the Device.
• Sub ID 5 Only Fallback to IP + Device Fallback to IP Only: The most permissive tracking type, CAKE checks first for a match against values in the s5 and UDID parameters passed, if it can't match it checks for a match against the IP plus the Device and if that fails to match it checks purely against IP.