---
schema_version: "1"
id: 8ed8a2da1e51ced295254228d504a176fc1a3ebb1c87c74934c52b3e686c3532
title: Troubleshoot Mobile App Events
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_mp_troubleshoot_mobile_app_events.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_mp_troubleshoot_mobile_app_events.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1774a48c96bf8ebfa8649750f16b69fdf39d3b05ec8c127d8a37cf657ed44dd5
description: Work with your app developer to troubleshoot message issues. Most issues are related to either message display or delivery.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Troubleshoot Mobile App Events

Work with your app developer to troubleshoot message issues. Most issues are related to either message display or delivery.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_mobile_studio-264-0-0-production-enus/26e7f9fa-f44c-489b-9b21-135d26904a29/images/icon_important.png)

Important The name of both the event and the attributes defined in Marketing Cloud Engagement must exactly match the name tracked by the [MobilePush SDK](https://developer.salesforce.com/docs/marketing/mobilepush/guide/overview.html). This naming allows Journey Builder to react to app events.

## Delivery Troubleshooting

_Are my messages being requested and returned?_

If you’re not sure if your messages are being requested by the MobilePush SDK and returned:

1. In Contact Builder, search for your MobilePush ContactKey or DeviceID to ensure that it’s registered with Marketing Cloud Engagement . If you can’t find the answer in Contact Builder, review your SDK implementation to ensure that it’s properly capturing and submitting this information to Engagement. Use the SDK logs to review the Sync API and confirm that messages are being delivered to the device. Intercept the API call to see the payload being returned.
2. In Journey Builder, activate an In-App Message campaign targeting your ContactKey.
3. Use the SDK logs to review the Sync API and confirm that your device is requesting In-App Messages on session start.
4. Use the SDK logs to review the Sync API and confirm that messages are being delivered to the device. Intercept the API call to see the payload being returned.

_Why isn’t the SDK requesting my messages?_

- If the SDK isn’t requesting your messages or the request is delayed, it’s possible that your app isn’t tracking sessions or initializing the SDK correctly.
- Background and then foreground the app to trigger the Sync API call.

_Why aren’t my messages being returned to the SDK?_

If your in-app messages aren’t being returned to the SDK on session start, this issue is likely related to the campaign audience defined in Engagement.

- To see if the message was successfully, sent, navigate to the History tab in Journey Builder and filter or search for your ContactKey.
- If you can’t find your ContactKey, ensure that the Contact is in the audience for your journey.
- Check the settings of the journey and whether the Contact is eligible to reenter.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_mobile_studio-264-0-0-production-enus/26e7f9fa-f44c-489b-9b21-135d26904a29/images/icon_note.png)

Note Messages are synced to the device on session start. There can be a delay as the eligible messages are delivered to the MobilePush SDK.

## Display Troubleshooting

If messages aren’t showing after you confirm that your app is successfully requesting and receiving in-app messages, there’s likely a configuration logic or app logic issue.

_Why isn’t my In-App Message appearing?_

- Ensure that the event implemented in the SDK is identical to the event defined in Marketing Cloud Engagement. If the events don’t match, the server drops them. For example, you implement the SDK to send an event named Screen View, but you register Engagement to listen for View Screen.
- Remove extra spaces from the trigger rules.
- Check for numerical mismatches between the trigger rules and the events being tracked by the SDK. For example, check for a missing or misplaced decimal point in an entry.
- Check the SDK logs to ensure that the marketer hasn’t imposed any additional trigger criteria such as message display limits or delay display within the app session.
- Failed image downloads prevent In-App Messages with images from appearing. Check that image downloads aren’t failing and that the image asset is available.
- If you’re using an SDK delegate to customize your app’s handling of In-App Messages, check your delegate to ensure that it isn’t affecting message display.