Community Forums/Get help with Kontagent/REST API

Answered

Why are Invite Sent recipient UIDs mandatory?

David Rauschenbach
asked this on December 10, 2010 11:00 am

I don't understand why the docs and test server say that a recipient of the Invite Sent message type is mandatory. An invite is almost certainly sent to a user who does not yet have a user id.

The docs acknowledge this in the Invite Click response, which has to occur after a click on a sent invite.

 

Comments

User photo
Frédérique DOUMIC
OUAT Entertainment

If there's no need recipeint UIDs, we could implement latest Requests Dialog method expecting a real alternative in Kontagent API.

February 17, 2011 12:10 pm
User photo
Andy Hin
Kontagent

Hi,

Invite sent messages are intended to be sent to us when a Facebook user invites another friend to your app (using the requests dialog). After they select their friends, facebook will provide you with a list of the recipients the user selected - this is what goes in the recipients field.

February 25, 2011 05:47 pm
User photo
Dion Paragas
INENSU

Hi,

The new Requests Dialog actually returns a list of request_ids. Is this what should be placed in the recipients field or do the request ids have to be requested using the Graph API to obtain the Facebook UIDs in order to track [ins]?

 

http://developers.facebook.com/docs/reference/dialogs/requests/

March 09, 2011 11:13 am
User photo
Sammi Song
desgames.com

use open graph api to get recipient facebook user id.

/request_id

parse object and get recipient id by obj->to->id.

March 09, 2011 12:49 pm
User photo
David Rauschenbach
resiliant software

If an app has both a Facebook and MySpace facade, then my user ID's will be internal user ID's, not Facebook IDs. And invited users won't have user ID's until they visit the app for the first time. Until then, there should only be an invitation.

March 09, 2011 12:55 pm
User photo
Andy Hin
Kontagent

Hi guys,

As Sammi mentioned, you can make a call to Facebook to exchange the request_id to get the recipient id. This will work. However, I believe you can also just send us the request_id instead of the recipient UID - this will save you an extra request.

Let me double check with our developers on this and I will update this thread to confirm.

David- if you are tracking your own internal invites (not related to Facebook invites) then you should look into EVT messages. This will provide the functionality you need and does not require a 'r' parameter. See: http://developers.kontagent.com/getting-started/instrumenting-your-application/kontagent-rest-api/events

[wand@db3 ~]$ zcat /store/raw/remote/2011/03/08/*/ktraw_cbb8503204c24d9a86c4d7a19ec150c0* | /opt/analytics/etl/bin/extract-messages -t cpu | grep "lc=US" | raw-params -p s | sort -n | uniq | wc -l
25708
March 09, 2011 12:56 pm
User photo
Andy Hin
Kontagent

I've confirmed with our developer that you can just pass us the request_id and avoid the extra request to Facebook to get recipient UID.

March 09, 2011 05:08 pm