Marketo Mobile Extension for Adobe Launch
Install the Marketo Mobile SDK extension in Adobe Launch to send push notifications, in-app messages, or both.
Prerequisites
- Add an application in Marketo Admin and obtain the application Secret Key and Munchkin Id.
- Follow the installation instructions in the Adobe Launch portal.
- Optional: Set up push notifications.
iOS
Setup Swift Bridging Header
-
Go to File > New > File and select “Header File”.
-
Name the file “<ProjectName>-Bridging-Header”.
-
Go to Project > Target > Build Phases > Swift Compiler > Code Generation.
-
Add the following path to Objective-Bridging Header:
$(PODS_ROOT)/<_ProjectName_>-Bridging-Header.h
For Swift, remove the following import statement because the preceding steps add the bridging header.
import Marketo/ALMarketo
iOS Test Devices
Follow the instructions in Adding iOS Test Devices.
Handle Custom Url Type in AppDelegate
Follow the custom URL instructions.
Set up push notifications on iOS
Follow the push notification instructions. Use the class name “ALMarketo” instead of “Marketo”.
Android
Configure Permissions
Open AndroidManifest.xml and add the following permissions. Your app must request the “INTERNET” and “ACCESS_NETWORK_STATE” permissions. Skip this step if the app already requests them.
<uses‐permission android:name="android.permission.INTERNET"></uses‐permission>
<uses‐permission android:name="android.permission.ACCESS_NETWORK_STATE"></uses‐permission>
ProGuard Configuration (Optional)
If your app uses ProGuard, add the following lines to the proguard.cfg file in your project folder. This configuration excludes the Marketo SDK from obfuscation.
-dontwarn com.marketo.*
-dontnote com.marketo.*
-keep class com.marketo.**{ *; }
Android Test Devices
Follow the instructions in Android Test Devices.
Set up push notifications on Android
Follow the Android Firebase Cloud Messaging instructions. Use the class name “ALMarketo” instead of “Marketo”.
To set up user profiles, follow the user profile instructions. To set up custom actions, follow the custom action instructions. In both sets of instructions, use the class name “ALMarketo” instead of “Marketo”.