Adobe Campaign Standard (Beta)

Last updated 4 days ago

Before you install or configure the Adobe Campaign Standard beta extension, we recommend that you read the Getting Started section and in Configuring a mobile application using Adobe Experience Platform SDKs.

This extension is considered beta functionality and is available only in Launch's Integration environment. For more information, see Configuring a mobile application using Adobe Experience Platform SDKs or contact your beta program manager.

Configure Campaign Standard Extension in Launch

  1. In Launch's Integration environment, click the Extensions tab.

  2. On the Catalog tab, locate the Adobe Campaign Standard extension and click Install.

  3. Provide extension settings (see Configure Campaign Standard Extension).

  4. Click Save.

  5. Follow the publishing process to update SDK configuration

Configure Campaign Standard Extension

ACS Endpoints

Trying to find your ACS endpoint URLs? Contact your beta manager.

Provide endpoint URL(s) for your Adobe Campaign Standard instances. You may specify up to three unique endpoints for your development, staging, and production environments.

For this beta extension, these endpoints URLs should be entered in without a prefixing http:// or https://.


A unique, auto-generated identifier for a mobile app configured in Adobe Campaign Standard. After you've configured this extension in Launch, you will need to configure your Launch mobile property in Adobe Campaign Standard. When the configuration in Campaign is successful, pKeys will be automatically generated, per Campaign Standard instance, and configured in Launch Campaign extension for successful validation.

Need help connecting your Launch mobile property with your Campaign Standard mobile app? For more information, see Configuring a mobile application using Adobe Experience Platform SDKs.

MCIAS Endpoint

Trying to find your MCIAS endpoint URL? Contact your beta manager.

Provide your in-app messaging service URL endpoint. The SDK retrieves all in-app messaging rules and definition payloads from this endpoint.

For this beta extension, the MCIAS endpoint URL should be provided with a prefixinghttp:// or https:// and must end with a forward slash. For example,

Request Timeout

Time in seconds to wait for a response from the in-app messaging service, before timing out. The SDK default timeout value is 5 seconds.

Add Campaign Standard to your app

This beta extension is currently available only for iOS development.


This beta Campaign Standard extension requires Mobile Core and Profile beta extensions. If you are using other versions of Mobile Core and Profile libraries, use the beta version instead, as the instructions below indicate.

Add the Campaign Standard, Mobile Core, and Profile beta libraries to your project. You'll need to add the following pods to your Podfile:

pod 'ACPCoreBeta', '1.0.2beta'
pod 'ACPCampaignBeta', '1.0.2beta'
pod 'ACPUserProfileBeta', '1.0.1beta'

or you can manually include the Mobile Core, Campaign Standard, and Profile beta extensions found in Github.

In Xcode, import the Mobile Core beta, Campaign Standard beta, and Profile extensions:


#import <ACPCore_iOS/ACPCore_iOS.h>
#import <ACPCampaign_iOS/ACPCampaign_iOS.h>
#import <ACPIdentity_iOS/ACPIdentity_iOS.h>
#import <ACPSignal_iOS/ACPSignal_iOS.h>
#import <ACPLifecycle_iOS/ACPLifecycle_iOS.h>
#import <ACPUserProfile_iOS/ACPUserProfile.h>


import ACPCore_iOS
import ACPCampaign_iOS
import ACPIdentity_iOS
import ACPLifecycle_iOS
import ACPSignal_iOS
import ACPUserProfile_iOS

Register Campaign Standard with Mobile Core


In your app'sapplication:didFinishLaunchingWithOptions: method, register the Campaign Standard extension:


- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
[ACPCampaign registerExtension];
[ACPIdentity registerExtension];
[ACPLifecycle registerExtension];
[ACPSignal registerExtension];
[ACPUserProfile registerExtension];
// Override point for customization after application launch.
return YES;


func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
// Override point for customization after application launch.
return true;

Set up push messaging

After you follow Apple's instructions to get your app ready to handle push notifications, you will need to set the push token using the setPushIdentifier API:





+ (void) setPushIdentifier: (nullable NSData*) deviceToken;


- (void) application:(UIApplication *)application didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken {
// Set the deviceToken that the APNS has assigned to the device
[ACPCore setPushIdentifier:deviceToken];



Tracking for push and in-app messaging

For more information about setting up tracking postbacks for push and in-app messaging, contact your beta program manager for more detail on creating rules for in-app messaging tracking postback and creating rules for push notifications tracking postback.

For more information, go to Configuring your application in Launch and search for Create rules for push notifications tracking postback and Create rules for In-App tracking postback .

Deleting mobile properties in Launch

Deleting your property in Launch may cause disruption to any recurring push and in-app messaging activities.

If you delete your mobile property in Launch, you might review your mobile property status in Campaign Standard and ensure that the property displays an updated status of Deleted in Launch. You may choose to remove the corresponding mobile app in Campaign Standard by clicking the Remove from ACS button. For more information, see Configuring a mobile application using Adobe Experience Platform SDKs.

Deleting your mobile property in Launch does not automatically delete your Campaign Standard mobile app.