You are here:
Get Started with Mobile App Events
Before events can be used to trigger the display of in-app messages, they must first be defined in Marketing Cloud Engagement and then implemented in the MobilePush SDK.
Prerequisites
Complete the following prerequisites before you begin to use mobile app events.
- As a marketing team, define the campaigns in which you plan to use mobile app events.
- Work with your mobile app development team to define the app events that are required to power these campaigns.
- Upload your CSV schema file for the mobile app events that you want to use within Journey Builder. Journey Builder isn’t intended to act as a dedicated analytics or segmentation platform. Prioritize the events that you plan to use directly within a campaign. Marketing Cloud Engagement allows a maximum of 20 defined event names per MobilePush app.
- Have your mobile development team track events with the MobilePush SDK. Use version 8.0.8 or
later of the SDK. Important The name of both the event and the attributes defined within Marketing Cloud Engagement must exactly match the name tracked by the MobilePush SDK. This naming allows Journey Builder to react to app events.
- Use your mobile app events in your Mobile App Event Entry Source and in-app messages.
Template Events
Template Events are mobile app events predefined by Salesforce. These events use a standardized naming convention understood by other Salesforce products, such as Data 360. The names used for Template Events and their Attributes can’t be changed. But you can extend the predefined events by adding attributes to them. Template Events are predefined in the MobilePush SDK, but they still require implementation.

