Prior to writing any code to integrate app events, we recommend spending a little time thinking about the key events you want to log within your app and what parameters associated with those events you will want to collect. This document will serve as a starting point for developers and marketers to help determine what events and parameters should be logged with app events.
A typical area of confusion for developers encountering app events for the first time is the difference between events and parameters.
For instance, Achieved Level is an event and Level 3 and Score are two parameters that can be associated with that event.
The maximum number of different event names is 1,000. Note: Events can’t be removed and no new event types will be logged once this cap is hit. Read more about event limits in the FAQ.
When you use the FB SDK for App Events, our business terms require that you have an appropriate legal basis to collect and process users' information. Under GDPR and other EU data protection regulations, you are required to obtain end user consent before sending data via our SDK. Thus, you need to ensure that your SDK implementation meets these consent requirements.
Please see our GDPR Compliance guide for more information.
We've created some recipes for different types of apps in order to make it easier for you to see how you can use app events in your app.
It is important to note that these guides should be used as a starting point for your app and should be customized. Each of the example apps provides a screen by screen breakdown of the different events and parameters that can be collected. At the end of each section there is a table listing the recommended events and parameters for each app. And, if required, you can create your own events and parameters.