It makes sense. One thing to note, unfortunately, is that if a user accepts a request -but- has not already approved your application, JFBConnect can't mark the request as Read for that user. The issue is due to a bug in Facebook that's quite annoying, but left unfixed for a few months now:
developers.facebook.com/bugs/239476836116522
(Please feel free to click the "Does this repro describe your issue?" button and mention your application in that link)
Basically, Facebook changed Requests in early January (right after our first release supporting Requests) to where we can't get the user ID of the acceptor of a Request unless that user has approved the App. Since a specific request can be sent to 10 people (let's say), we need both the Request ID (which we get) and the User ID (which we may not get).
So, the 2% number is the floor of the amount of 'reads' you've gotten. Unfortunately though, there's no way to tell how many really have been read.
We have some plans for the 4.2 release to improve this situation. It won't be perfect, but will help make the counting a little more accurate. We'll be looking into it further next week, and hoping the 4.2 release will be out in mid'ish April (possibly late).
Hope what I said makes sense, but if you have other questions, let me know,
Alex
How to Optimize Facebook Requests?
