Track Facebook Request profile

It sounds as if the user you are sending a request to has not authenticated on your website yet. Basically, when Facebook sends a request, it returns an ID that is tied to your application and if the user has not approved the application, we will not be able to discern the user's Facebook ID.

I just tried on my test site to send a request to both a user who has authenticated for my application and one who hasn't. The profile link for the user who had authenticated on my site brought me to the profile page that loaded correctly. The profile link for the user who had not authenticated on my site brought me to the same page that you are seeing, as expected.

Sorry if this is not the answer you're looking for but I hope it explains the behavior. Facebook behaves this way for privacy reasons and there is nothing we can do to get around this.

-Melissa

I don't think that's necessary. Users that have not authenticated on your site will still receive the request. This can drawn them back to your site that way, gaining you more traffic/reach, which is definitely a good thing. However, I don't know if you're using the request for a more private feature of your website, so the choice is up to you on how to implement requests (whether to make this available on the front-end of your site or not).

If you are using the feature on the front-end for any users to send the requests out, I don't even know if there is a way to limit it to just users of your site in the Facebook widget that is launched. Facebook handles the list of available users that is populated in the widget.

-Melissa