Also say the person lands on the page because they clicked a post. They haven't installed the program so we record a psr with no userid and 0 on installed. Then the page redirects to have the user to accept the application, they click yes. This records an apa on post-authorization callback. We then load the page and it comes with the kt parameters and we record a psr with a userid and installed set to true.

What exactly are we supposed to be doing here?

2. Both. Send a psr first then an apa message should the user authorizes your app. The tracking tags have to match.

3. Same as 2. Send a inr first then an apa message. 

You need to send us the psr message first before forwarding your users to an app authorization page.

Does the psr message need to contain a userid or is just the tracking id ok?

I understand now.

1. Hit the page by clicking a post that has a tracking tag and post type in it.

2. The page loads and records a PSR with the tracking tag and post type with no userid

3. The app install page comes up. Click yes.

4. The user is redirected back to the page and facebook passes an installed=1 parameter. 

5. Call APA with the same tracking tag, and with the userid.)

Brandon,

Just wanted to give you a heads up that, once FB turns on the new data permission model, the installed=1 parameter will no longer be sent after the authorization step.  To get around this issue. I would suggest to set up a post-authorized url. Inside your post-authorized url, you should probably check to make sure that sig is correct before proceeding. If so, call data.setcookie to give yourself a hint that an app install has occurred. This call sets a cookie on the facebook side.  Once the user is forwarded back to the landing page, you'll need to check to set if that cookie is set. If so, you know that an install has occurred. 

Thanks for the heads up.

Safari doesn't record 3rd party cookie by default so this won't always work. This might be the best solution. It would be nice if they could leave that install param for us. :\

I understand that this is a facebook cookie, which is different so sorry about the last post. Is there ever an issue with synchronization. Can the post-auth callback be called after the page is loaded and then not receive the fb cookie data?

Hey Lih,

This is my first post :) I am in the process of implementing Kontagent tracking to our latest game (under development). I have run into a snag with the 'inr' tracking. Facebook has removed the post-authorization page (see here: http://forum.developers.facebook.net/viewtopic.php?id=71010) - so I am a little confused how to track that the invite has been clicked on.

From what I understand we track ins (invite sent) when inviting a friend, then inr (invite response) when my friend clicks on 'play now!' button in their requests page (by means of taking them to a tracking page when they click on that) and then apa (application added) when they hit the index page of the application. I'm not concerned with 'apa' (at least not yet :P) but more so with 'inr', am I doing it completely wrong?

Thanks!

Hi John,

Yes, I have already pushed the changes to handle that onto github: http://github.com/kontagent/php-sdk 

In a nutshell, Facebook appends installed=1 to the end of the original app URL after authorization.  The library will check to see if installed=1 is present in the query string. If so, it'll consider it as an application added event.

Lih 

It would be nice that the correct procedure (steps) will be in documentation. In documentaion installed=1 still is being used and is not clear when apa should be done.

Thanks