adobe-campaign-standard-beta.md

Adobe Campaign Standard (Beta)

{% hint style="warning" %} This extension is considered beta functionality and is available only in Launch's Integration environment. For more information, see Campaign Standard's user guide or contact your beta program manager. {% endhint %}

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 Analytics Extension)
4. Click Save.
5. Follow the publishing process to update SDK configuration

Configure Campaign Standard Extension

ACS Endpoints

{% hint style="info" %} Trying to find your ACS endpoint URLs? Contact your beta program manager. {% endhint %}

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.

{% hint style="warning" %} For this beta extension, these endpoints URLs should be entered in without a prefixing http:// or https://. {% endhint %}

pKey

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 connect your Launch mobile property with an Adobe Campaign Standard mobile app. When the connection is made, pKeys will be automatically generated, per Campaign Standard instance, and configured here for successful validation.

{% hint style="info" %} Need help connecting your Launch mobile property with your Campaign Standard mobile app? See Campaign Standard user guide for more information. {% endhint %}

MCIAS Endpoint

{% hint style="info" %} Trying to find your MCIAS endpoint URL? Contact your beta program manager. {% endhint %}

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

{% hint style="warning" %} For this beta extension, the MCIAS endpoint URL should be provided with a prefixinghttp:// or https://. {% endhint %}

Request Timeout

Time in seconds to wait for a response from the in-app messaging service, before timing out.

Add Campaign Standard to your app

{% hint style="warning" %} This beta extension is currently available only for iOS development. {% endhint %}

{% tabs %} {% tab title="iOS" %} {% hint style="warning" %} 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. {% endhint %}

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 'ACPCampaignBeta'
pod 'ACPCoreBeta'
pod 'ACPUserProfileBeta'

or you may 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:

Objective-C

#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>

Swift

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

{% endtab %} {% endtabs %}

Register Campaign Standard with Mobile Core

{% tabs %} {% tab title="iOS" %} In your app'sapplication:didFinishLaunchingWithOptions: method, register the Campaign Standard extension:

Objective-C

- (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;
}

Swift

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

{% endtab %} {% endtabs %}

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:

{% tabs %} {% tab title="iOS" %}

setPushIdentifier

Objective-C

Syntax

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

Example

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

Swift

ACPCore.setPushIdentifier(deviceToken)

{% endtab %} {% endtabs %}

Tracking for push and in-app messaging

For more information about setting up tracking postbacks for push and in-app messaging, see the Campaign Standard user guide.

Deleting mobile properties in Launch

{% hint style="danger" %} Deleting your property in Launch may cause disruption to any recurring push and in-app messaging activities. {% endhint %}

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 selecting the Remove from ACS button. See the ACS user guide for more information.

{% hint style="warning" %} Deleting your mobile property in Launch does not automatically delete your Campaign Standard mobile app. {% endhint %}