Migrating to AEPCampaign reference
This document is a reference comparison of ACPCampaign (1.x) APIs against their equivalent APIs in AEPCampaign (3.x) for an iOS mobile application implementation.
The AEPCampaign extension is implemented purely in Swift and is compatible with the AEPCore swift SDK. To ensure a smooth transition from the ACPCampaign SDK, there are no major changes on the API names or definition. For more details, follow the migration guide below for your Swift or Objective-C mobile application. If explanation beyond showing API differences is necessary, it will be captured as an info hint within that API's section.
Type | AEP (3.x) | AEP 3.x (Objective-C) | ACP (1.x) |
|---|---|---|---|
Primary Class (Module) | Campaign | AEPMobileCampaign | ACPCampaign |
AEP 3.x (Swift)
AEP 3.x (Objective-C)
ACP 1.x (Objective-C)
static var extensionVersion: String
+ (nonnull NSString*) extensionVersion;
+ (nonnull NSString*) extensionVersion;
AEP 3.x (Swift)
AEP 3.x (Objective-C)
ACP 1.x (Objective-C)
Registration occurs by passing
Campaign to the MobileCore.registerExtensions API.MobileCore.registerExtensions([Campaign.self])
Registration occurs by passing
AEPMobileCampaign to the [AEPMobileCore registerExtensions:completion:] API.[AEPMobileCore registerExtensions:@[AEPMobileCampaign.class] completion:nil];
+ (void) registerExtension;
AEP 3.x (Swift)
AEP 3.x (Objective-C)
ACP 1.x (Objective-C)
static func resetLinkageFields()
+ (void) resetLinkageFields;
+ (void) resetLinkageFields;
AEP 3.x (Swift)
AEP 3.x (Objective-C)
ACP 1.x (Objective-C)
static func setLinkageFields(_ linkageFields: [String: String])
+ (void) setLinkageFields: (nonnull NSDictionary<NSString*, NSString*>*)
+ (void) setLinkageFields: (nonnull NSDictionary<NSString*, NSString*>*) linkageFields;
Last modified 5mo ago