With App Events and Analytics for Account Kit, you can gather anonymized, aggregate demographic data about the people signing up for your iOS, Android and web application with Account Kit.
App Events are on by default in web.
Once you have followed these steps, your application will record Account Kit events with no further development effort on your part.
Note: You do not need to have Facebook Login enabled in order to use App Events for Account Kit.
On the client side, we collect the following events:
The events flow like so: Login impression → Login start → Login attempt → Logged In
On the server side, the following event is recorded:
You can view the breakdown of notification types that are being sent.
To see the counts for the raw client events, navigate to the Events tab under the Activity menu. It will display both the raw count as well as the number of unique users.
To see a funnel using the client events, navigate to the Funnels tab under the Activity menu. If you have already been sending client events, the Account Kit funnel should already be selectable.
You can customize the funnel to your liking by filtering with parameters or by creating new funnels with the Account Kit client events. For example, filtering the event login attempts by verification method can show how many users are verified by confirmation code vs instant verification.
To see analytics for your application, click the View Analytics link at the top of your application's dashboard in the developer portal:
In the Analytics dashboard, select Account Kit from the Facebook Platform menu:
At the top of the Account Kit dashboard is a summary of login data:
Note that the data may be broken out by channel (Android or iOS) or by login type (email or phone) using the dropdown on the right. This also goes for the New Logins graph:
You may also view a graph of daily, weekly, and monthly active user counts:
To understand your signup conversion funnel, you can view a number of events related to the Account Kit login flow. These events include confirmations sent:
Conversions (how many people enter the login flow, and how many complete it:
Finally, you may view counts of raw login events, including impressions (times an email address or phone number form was shown), opens (times a notification was acted upon), and completions (times the login flow was completed). Optionally, these events may be filtered by channel (iOS or Android) or login type (email or phone):
Aggregate demographic data for users is available, including gender, country, and language: