Having just implemented what seems like the correct steps for Facebook v4.beta, is there any other way to test whether publishInstall is working without uploading to the app store and starting an ad campaign on FB?
Also with Facebook v4.beta, is the following still required?
["URL types"] = { item = { ["URL Schemes"] = { ["Item 0"] = "fbXXXXXXXXXX" }, --replace XXXXXXXXXX with your Facebook App ID }, },I don’t know of a way to test published installs.
As for the URL scheme yes. It’s how FB’s app knows how to get back to your app after authenticating.
Rob
Thanks Rob,
Do you know what the facebook.publishInstall( ) call does? I’m assuming it logs installs of apps against registered apps in FB developer. So this would run every time the app in question is launched. But obviously it only logs unique installs.
The dashboard for an app in developers.facebook feature Analytics with the description:
Once you start logging events, the overview will give you a comprehensive idea of how people are using your app. You’ll be able to see data like app installs, sessions, purchases, active users, average session length and demographics.
So in development builds on devices, the facebook.publishInstall( ) call should be logging events to the FB app account - right? This would be the same as Flurry for instance which logs events on development builds.
The publishInstall() function really serves one purpose. If Facebook gives a user an opportunity to install your app through an ad or some featured placement, if the user installs and runs your app, facebook.publishInstall() will if successful register the install with Facebook. It will never run a second time once it’s successfully registered itself. Facebook uses this information to not offer that user another ad to install your app… if I understand correctly. It doesn’t have anything to do with ongoing analytics or tracking how the user is using Facebook in your app.
Rob
I don’t know of a way to test published installs.
As for the URL scheme yes. It’s how FB’s app knows how to get back to your app after authenticating.
Rob
Thanks Rob,
Do you know what the facebook.publishInstall( ) call does? I’m assuming it logs installs of apps against registered apps in FB developer. So this would run every time the app in question is launched. But obviously it only logs unique installs.
The dashboard for an app in developers.facebook feature Analytics with the description:
Once you start logging events, the overview will give you a comprehensive idea of how people are using your app. You’ll be able to see data like app installs, sessions, purchases, active users, average session length and demographics.
So in development builds on devices, the facebook.publishInstall( ) call should be logging events to the FB app account - right? This would be the same as Flurry for instance which logs events on development builds.
The publishInstall() function really serves one purpose. If Facebook gives a user an opportunity to install your app through an ad or some featured placement, if the user installs and runs your app, facebook.publishInstall() will if successful register the install with Facebook. It will never run a second time once it’s successfully registered itself. Facebook uses this information to not offer that user another ad to install your app… if I understand correctly. It doesn’t have anything to do with ongoing analytics or tracking how the user is using Facebook in your app.
Rob