Configure a mobile application using Adobe Experience Platform SDK

To send In-App messages or push notifications using the Mobile SDK V5, the mobile app has to be set up in Adobe Experience Platform Launch and configured in Adobe Campaign.

The videos below demonstrates the required steps to configure a mobile app in Experience Platform Launch:


In this video, will show how to set up a mobile app that is instrumented with a PSTK such that you can use this app for sending push and in-app messages in Adobe Campaign Standard. So in order to set up the mobile app, we’ll start by activating the mobile property in Adobe Launch. As you can see on my screen, I’m currently on the homepage of Adobe Launch.

Click on New Property to get started.

We give it a name and be sure to select the platform as Mobile. We can leave the other options default and click Save.

Let’s search for the mobile property that I just created.

And once you’re able to locate the mobile property that you’ve created, navigate to the Extensions tab. You’ll find two extensions installed by default. Mobile Core and Profile. These extensions are required for the appropriate functioning of the mobile app. But, you do not need any configuration here; so we’ll leave them as it is and navigate to the Catalog to install Adobe Campaign Standard extension.

So I went ahead and installed the Adobe Campaign extension. This extension will require some configuration, starting with the Endpoints of your campaign instances. You can specify up to three different instance names here for Development stage and Production. So, let us go ahead and provide the Endpoints for your Campaign instances.

And let’s just say this is “mcias_” stage and this what is Production. And “MCIAS” stands for Marketing Cloud In-App Messaging Service. Then will ensure that we select the correct MCIAS region. This region is typically the region of the data center where your Adobe Campaign Standard instance is hosted. So the options that are available to you are North America, EMEA, Asia, and Custom. Custom is typically used by developers for testing et cetera. In production, you will require one of these three regions. So for me, I will leave it at North America and click Save.

Now at this time, I can navigate to my Campaign instance and I should see the mobile app property.

Okay, let’s search for the… So, I found the mobile app that I just created and I access that mobile app. At this time, you can either go ahead and start configuring the app. You can start defining the mobile app events that you require for your in-app message triggers and upload Push Certificates here. Or, if you want to come in and finish the configuration data, you can just go ahead and click Save.

Both OK and Go to Launch will help finish the configuration in Campaign, with the difference that Go to Launch will take you to Launch as well. So for now, will just go ahead and click OK and let’s come back to Launch. I did a refresh this session.

Now I go back into my Campaign extension again to verify that this handshake between Launch and Campaign was successful. The way to check that, is that, you will see this message here which says, “pkey: successfully configured.” That is our indication that your Campaign extension has been installed successfully and the mobile property is available to you in Campaign. But you do have some more configuration to carry out in Launch before your mobile app is all set. So the next thing that will have to do here is define some Data Elements that you will require to create Rules.

The three basic Data Elements that we recommend that you define are “MCID”, “CampaignServer” and “pkey”.

You’ll have the need to refer to these Data Elements as you define your Rules, so it’s better that you have these configured.

Now, we are done with the Data Elements definition and at this time, let’s navigate to the Rules tab to start defining some rules. PII Postbacks; this is a postback rule that allows you to start collecting mobile profile attributes from the mobile device. So let’s go ahead and create this Rule. Call it “CollectPII” which will be triggered on Collect PII Event and the Action that we want to take when this Event triggers is to Send PII to Campaign Server.

And I’m going to make sure that I have the correct Data Elements being referenced in the URL here.

So that’s the CampaignServer. “Pkey”.

And finally, the Experience Cloud ID.

So we’re all set with this URL and then add Post Body. So I’ll just take an example Post Body which is basically sending a bunch of data. And then finally, Content Type which is “json”.

We are done defining the Rule for collecting PII data from mobile SDK. Now let us go ahead and define one more Rule for In-App Tracking Postback. So let’s just call this rule, “In-App Click Tracking” under Events.

I should select In-App Click Tracking from Adobe Campaign Standard extension. And then, we define the Actions. Will use a Send Postback to this URL.

And, make sure that you have the right Data Elements being referenced here.

Select CampaignServer.



And that’s it. We don’t require any Post Body for this and the Content Type will still be “json”.

Once you’re done with all of your configuration in Launch, you need to ensure that you publish these changes. Make sure we have our Adapter set up.

So click to Publishing, and New Library.

Wrap it to an appropriate environment. Add all Changed Resources.

Make sure that all the changes that you’ve made are captured. And then go ahead and click on Save & Build for Development.

That’s it! You’re all set for utilizing your app in Adobe Campaign for sending out Push and all in-app messaging. Thanks for watching.


See Configuring your application in Launch for the detailed documentation and the code templates used in the video.

On this page