---
schema_version: "1"
id: 62024ffaed6c850d64f26b7ad1c5256081d8eb95fabab0733060fc33cef6ab10
title: Configure a Mobile App Event Entry Source
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_jb_mobile_app_event_entry_source.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_jb_mobile_app_event_entry_source.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 70a40517494e6a180f1ea09c997daddf3f2d133281a3a41b9ce9d79ed91dc6ab
description: Use the Mobile App Event entry source in Journey Builder to listen for user behavior and admit contacts who take specific actions in your mobile app, such as installing the app or making a purchase. You can set a filter using App Event data attributes to ensure that only intended customers enter the journey. Mobile App Events aren’t stored in a data extension, but you can use Mobile App Event metadata as journey data.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Configure a Mobile App Event Entry Source

Use the Mobile App Event entry source in Journey Builder to listen for user behavior and admit contacts who take specific actions in your mobile app, such as installing the app or making a purchase. You can set a filter using App Event data attributes to ensure that only intended customers enter the journey. Mobile App Events aren’t stored in a data extension, but you can use Mobile App Event metadata as journey data.

For Journey Builder to react to App Events, the Name of the event and the attributes defined within Marketing Cloud Engagement must exactly match the name tracked by the MobilePush SDK. Pending your app and desired use cases, you can capture some events or attributes that are more descriptive than others. For example, purchase versus first purchase.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_journeys_and_automations-264-0-0-production-enus/e08cdd71-c1c1-4ae5-a5e9-8a6dad583ad4/images/icon_important.png)

Important To use this entry source, first [define your Mobile App Events](https://help.salesforce.com/s/articleView?id=mktg.mc_jb_define_mobile_app_event_schema.htm&release=264.0.0&type=5 "An app event requires a name and can optionally contain many attributes. Depending on your app and use cases, you can capture events or attributes that are more descriptive than others.") in the Mobile App Event Management screen, and then implement tracking within the MobilePush SDK.

When selecting App Events, ensure that your app is collecting events that are in line with Journey Builder best practices for API Entry events. Note the volume of the App Events that you use for Entry.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_journeys_and_automations-264-0-0-production-enus/e08cdd71-c1c1-4ae5-a5e9-8a6dad583ad4/images/icon_note.png)

Note Unlike other Entry sources, Mobile App Events aren’t saved into data extensions.

Follow these steps to configure the Mobile App Event source in Journey Builder:

1. Drag the **Mobile App Event** Entry Source onto the journey canvas.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_journeys_and_automations-264-0-0-production-enus/e08cdd71-c1c1-4ae5-a5e9-8a6dad583ad4/images/icon_note.png)
    
    Note If you want to add a Mobile App Event Exit source, click ![the Exit Criteria icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_journeys_and_automations-264-0-0-production-enus/e08cdd71-c1c1-4ae5-a5e9-8a6dad583ad4/mc_journeys_and_automations/images/mc_jb_Exit_Criteria_icon_updated.png) and then **Mobile Events Exit Criteria**.
2. Click **Select Event**.
3. Select one event from the list.
4. Set the filter event criteria.
5. To review your configuration, click **Summary**.
6. Click **Done**.
7. Configure the rest of your journey, and then click **Activate**.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_journeys_and_automations-264-0-0-production-enus/e08cdd71-c1c1-4ae5-a5e9-8a6dad583ad4/images/icon_note.png)

Note Exit or entry source can listen for up to 10 events.