---
title: "Set Up Mapp Engage for Push & In-App Notifications"
slug: "mapp-intelligence-ios-sdk-v5-engage-setup-push-in-app-notifications"
updated: 2026-04-30T12:17:45Z
published: 2026-04-30T12:17:45Z
canonical: "docs.mapp.com/mapp-intelligence-ios-sdk-v5-engage-setup-push-in-app-notifications"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Up Mapp Engage for Push & In-App Notifications

To track push and in-app notifications in your iOS app, you need to install the **Mapp Engage SDK** alongside the Mapp Intelligence SDK and configure your app's `AppConfig.plist` with the credentials of your Mapp Engage system.

Before you start, complete the [Quickstart](/v1/docs/mapp-intelligence-ios-sdk-v5-quickstart) so the Mapp Intelligence SDK is initialized.

> [!NOTE]
> Mapp Engage and Mapp Intelligence are separate SDKs. This page covers only the configuration that the Engage SDK needs in order for the Intelligence SDK to track push / in-app interactions. For Engage SDK installation itself, see the Mapp Engage iOS SDK documentation.

---

## Step 1 — Add the AppConfig.plist file

Add an `AppConfig.plist` file to your iOS app target. The Engage SDK reads this file at startup. The required keys are:

| Key | Description |
| --- | --- |
| `jamie_url` | The Jamie URL used to cache and deliver in-app messages. |
| `sdk_key` | The SDK key generated in *Mapp Engage > Administration > Channels*. Each app (iOS Dev, iOS Prod, Android Dev, Android Prod) has its own key. |
| `app_id` | The app ID from *Mapp Engage > Administration > Channels*. Different per environment. |
| `dmc_system_id` | The ID of your Mapp Engage system. Provided by your Mapp Cloud account or project manager. |
| `is_eu` | `true` when your Mapp Engage tenant runs in the EU region; `false` otherwise. |
| `open_landing_page_inside_app` | Whether landing pages should open inside the app or in the system browser. |
| `apx_open_url_internal` | Whether deep links from messages should open inside the app context. |

---

## Example AppConfig.plist

```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>inapp</key>
    <dict>
        <key>custom_fields</key>
        <array>
            <string>customString</string>
            <string>customNumber</string>
            <string>customDate</string>
        </array>
        <key>media_timeout</key>
        <integer>5</integer>
    </dict>
    <key>sdk</key>
    <dict>
        <key>app_id</key>
        <string>300654</string>
        <key>dmc_system_id</key>
        <integer>33</integer>
        <key>sdk_key</key>
        <string>17e29fc44dc61d.27429076</string>
        <key>is_eu</key>
        <true/>
        <key>open_landing_page_inside_app</key>
        <false/>
        <key>jamie_url</key>
        <string>jamie-test.shortest-route.com</string>
        <key>apx_open_url_internal</key>
        <string>YES</string>
    </dict>
</dict>
</plist>
```

> [!WARNING]
> Replace the example values (`app_id`, `sdk_key`, `dmc_system_id`, `jamie_url`) with the values your Mapp Cloud account / project manager provides for your specific environment.

---

## Next step

Once the Engage SDK is installed and `AppConfig.plist` is in place, continue with [Track Push & In-App Notifications](/v1/docs/mapp-intelligence-ios-sdk-v5-engage-track-push-in-app-notifications).

---

## Related

- [Quickstart](/v1/docs/mapp-intelligence-ios-sdk-v5-quickstart)
- [Track Push & In-App Notifications](/v1/docs/mapp-intelligence-ios-sdk-v5-engage-track-push-in-app-notifications)
- [User Matching](/v1/docs/mapp-intelligence-ios-sdk-v5-user-matching)