Brad Mills
asked this on June 15, 2010 09:56 am
With the release of the new data permissions install method, Kontagent doesn't automatically track installs anymore.
We're wondering if this is a problem with the SDK, and if there's a fix.
Right now we disabled Kontagent detection based on the install param, and instead called the app_added kontagent function based on the state of the user in our database (if the user is not already in our db).
Does this sound like a reasonable fix? Will this still allow kontagent to track referral sources for kontagent generated ad lnks?
Comments
Hi Brad,
I'm assuming that you are still using the old Facebook SDK, but now switching to the new permission method.
As you've already alluded to, since the install=1 GET parameter is no long being sent down by facebook, it broke the way Kontagent track app installs. What you proposed sounds like a reasonable fix. Referral source tracking should also work.
The new kontagent sdk (we are still testing it) based off of the new FB php SDK with the new oauth 2.0 approach does the following.
1) It includes a kt_post_authorize.php which is intended to be your post authorized url.
2) Inside kt_post_authorize.php, it sets a facebook cookie by calling data.setCookie('kt_just_installed", 1,...);
3) Once Facebook forwards your new user back to your application, kontagent will then check to see if kt_just_installed is set by calling data.getCookies(). If so, Kontagent will consider it an install event.
4) Just as before, Kontagent will take a look at the GET parameters to fetch both the long and short tracking tags and send it along with apa messages.
5) Expire kt_just_installed.