Adobe Campaign Classic

Configure Campaign Classic extension in the Data Collection UI

  1. 1.
    In the Data Collection UI, click the Extensions tab.
  2. 2.
    On the Catalog tab, locate the Adobe Campaign Classic extension, and click Install.
  3. 3.
    Type in the settings for your extension.
  4. 4.
    Click Save.
  5. 5.
    Complete the publishing process to update the SDK configuration.
    For more information about publishing, see the publishing overview.

Configure Campaign Classic extension

Configuring the Campaign Classic extension
You can retrieve your Campaign Classic registration or tracking endpoint URLs in the Campaign Classic interface under the Tools > Advanced > Deployment wizard menu. The endpoint for push notifications is usually the same as the URL that is used for web forms and surveys.

Registration endpoints

Type the registration endpoint URL(s) for your Campaign Classic instances. You can specify up to three unique endpoints for your development, staging, and production environments.
For this extension, the registration endpoint URLs should be entered without a prefixing https://.

Tracking endpoints

Type the tracking endpoint URL(s) for your Campaign Classic instances. Like the registration URLs, you can specify up to three unique endpoints for your development, staging, and production environments.
For this extension, the tracking endpoint URLs should be entered without a prefixing https://.

Integration key (iOS)

You can specify up to three unique iOS integration keys for your development, staging, and production environments. iOS integration keys are generated after creating a service that contains iOS applications using the Campaign Classic client console. For more information on where to find the integration key, see the tutorial on configuring the mobile application in Adobe Campaign.

Integration key (Android)

You can specify up to three unique Android integration keys for your development, staging, and production environments. Android integration keys are generated after creating a service that contains Android applications using the Campaign Classic client console. For more information on where to find the integration key, see the tutorial on configuring the mobile application in Adobe Campaign.

Request timeout

The request timeout is the amount of time, in seconds, to wait for a response from the registration or tracking endpoint before timing out. The SDK default timeout value is 30 seconds.

Add Campaign Classic to your app

Android
iOS
Java
  1. 1.
    Add the Campaign Classic extension to your project using the app's Gradle file.
    1
    implementation 'com.adobe.marketing.mobile:campaignclassic:1.+'
    Copied!
  2. 2.
    Import the Campaign Classic and Lifecycle extensions in your application's main activity.
    1
    import com.adobe.marketing.mobile.CampaignClassic;
    2
    import com.adobe.marketing.mobile.Lifecycle;
    Copied!
  1. 1.
    Add the Campaign Classic and Mobile Core libraries to your project.
    You can add the following pods to your Podfile:
    1
    pod 'ACPCampaignClassic'
    2
    pod 'ACPLifecycle'
    3
    pod 'ACPCore'
    Copied!
    or you can manually include the Mobile Core and Campaign Classic libraries found in Github.
  2. 2.
    In the Xcode project, import the Mobile Core and Campaign Classic extensions:
Objective-C
1
#import "ACPCore.h"
2
#import "ACPCampaignClassic.h"
3
#import "ACPLifecycle.h"
Copied!
Swift
1
import ACPCore
2
import ACPCampaignClassic
3
import ACPLifecycle
Copied!

Register Campaign Classic with Mobile Core

Android
iOS
In your app's OnCreate method, register the Campaign Classic and Lifecycle extensions:
1
public class CampaignClassicTestApp extends Application {
2
3
@Override
4
public void onCreate() {
5
super.onCreate();
6
MobileCore.setApplication(this);
7
MobileCore.setLogLevel(LoggingMode.VERBOSE);
8
9
try {
10
CampaignClassic.registerExtension();
11
Lifecycle.registerExtension();
12
MobileCore.start(null);
13
} catch (Exception e) {
14
Log.e("CampaignClassicTestApp", e.getMessage());
15
}
16
17
}
18
}
Copied!
In your app's application:didFinishLaunchingWithOptions: method, register the Campaign Classic and Lifecycle extensions:
Swift
1
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
2
ACPCampaignClassic.registerExtension();
3
ACPLifecycle.registerExtension();
4
// Override point for customization after application launch.
5
return true;
6
}
Copied!
Objective-C
1
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
2
[ACPCampaignClassic registerExtension];
3
[ACPLifecycle registerExtension];
4
// Override point for customization after application launch.
5
return YES;
6
}
Copied!

Configuration keys

To update SDK configuration programmatically, use the following information to change your Campaign Classic configuration values. For more information, see the Configuration API reference.
Key
Required
Description
Data Type
build.environment
Yes
Specifies which environment to use (prod, dev, or staging) when sending registration and tracking information. It is also used to specify which mobile app integration key to use.
String
campaignclassic.timeout
No
Specifies the amount of time to wait for a response from the Campaign Classic registration or tracking server.
Integer
__dev__campaignclassic.marketingServer
No
Sets the development environment marketing server, which receives registration requests.
String
__dev__campaignclassic.trackingServer
No
Sets the development environment tracking server, which receives tracking requests.
String
__dev__campaignclassic.ios.integrationKey
No
Sets the development environment iOS mobile app integration key, which links the app to an iOS application campaign in Campaign Classic.
String
__dev__campaignclassic.android.integrationKey
No
Sets the development environment Android mobile app integration key, which links the app to an Android application campaign in Campaign Classic.
String
__stage__campaignclassic.marketingServer
No
Sets the staging environment marketing server, which receives registration requests.
String
__stage__campaignclassic.trackingServer
No
Sets the staging environment tracking server, which receives tracking requests.
String
__stage__campaignclassic.ios.integrationKey
No
Sets the staging environment iOS mobile app integration key, which links the app to an iOS application campaign in Campaign Classic.
String
__stage__campaignclassic.android.integrationKey
No
Sets the staging environment Android mobile app integration key, which links the app to an Android application campaign in Campaign Classic.
String
campaignclassic.marketingServer
Yes
Sets the production environment marketing server, which receives registration requests.
String
campaignclassic.trackingServer
Yes
Sets the production environment tracking server, which receives tracking requests.
String
campaignclassic.ios.integrationKey
Yes
Sets the production environment iOS mobile app integration key, which links the app to an iOS application campaign in Campaign Classic.
String
campaignclassic.android.integrationKey
Yes
Sets the production environment Android mobile app integration key, which links the app to an Android application campaign in Campaign Classic.
String
Last modified 28d ago