@mparticle/cordova-sdk

mParticle Cordova SDK

Cordova plugin for mParticle

Installation

cordova plugin add @mparticle/cordova-sdk

Grab your mParticle key and secret from your app's dashboard and move on to the OS-specific instructions below.

iOS

Install the SDK using CocoaPods:

$ # Update your Podfile to depend on 'mParticle-Apple-SDK' version 9.2.0 or later
$ pod install

The mParticle SDK is initialized by calling the startWithOptions method within the application:didFinishLaunchingWithOptions: delegate call. Preferably the location of the initialization method call should be one of the last statements in the application:didFinishLaunchingWithOptions:. The startWithOptions method requires an options argument containing your key and secret and an initial Identity request.

Note that it is imperative for the SDK to be initialized in the application:didFinishLaunchingWithOptions: method. Other parts of the SDK rely on the UIApplicationDidBecomeActiveNotification notification to function properly. Failing to start the SDK as indicated will impair it. Also, please do not use GCD's dispatch_async to start the SDK.

Swift

import mParticle_Apple_SDK

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {

// Override point for customization after application launch.
let mParticleOptions = MParticleOptions(key: "<<<App Key Here>>>", secret: "<<<App Secret Here>>>")

//Please see the Identity page for more information on building this object
let request = MPIdentityApiRequest()
request.email = "[e-mail]"
mParticleOptions.identifyRequest = request
mParticleOptions.onIdentifyComplete = { (apiResult, error) in
    NSLog("Identify complete. userId = %@ error = %@", apiResult?.user.userId.stringValue ?? "Null User ID", error?.localizedDescription ?? "No Error Available")
}

//Start the SDK
MParticle.sharedInstance().start(with: mParticleOptions)

return true
}

Objective-C

For apps supporting iOS 8 and above, Apple recommends using the import syntax for modules or semantic import. However, if you prefer the traditional CocoaPods and static libraries delivery mechanism, that is fully supported as well.

If you are using mParticle as a framework, your import statement will be as follows:

@import mParticle_Apple_SDK;                // Apple recommended syntax, but requires "Enable Modules (C and Objective-C)" in pbxproj
#import <mParticle_Apple_SDK/mParticle.h>   // Works when modules are not enabled

Otherwise, for CocoaPods without use_frameworks!, you can use either of these statements:

#import <mParticle-Apple-SDK/mParticle.h>
#import "mParticle.h"

Next, you'll need to start the SDK:

- (BOOL)application:(UIApplication *)application
didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {

    MParticleOptions *mParticleOptions = [MParticleOptions optionsWithKey:@"REPLACE ME"
    secret:@"REPLACE ME"];

    //Please see the Identity page for more information on building this object
    MPIdentityApiRequest *request = [MPIdentityApiRequest requestWithEmptyUser];
    request.email = @"[e-mail]";
    mParticleOptions.identifyRequest = request;
    mParticleOptions.onIdentifyComplete = ^(MPIdentityApiResult * _Nullable apiResult, NSError * _Nullable error) {
        NSLog(@"Identify complete. userId = %@ error = %@", apiResult.user.userId, error);
    };

    [[MParticle sharedInstance] startWithOptions:mParticleOptions];

    return YES;
}

Routing the Rokt SDK+ through your own domain reduces the risk of ad blockers and browsers from blocking ads or data. You can configure this with MPNetworkOptions:

let networkOptions = MPNetworkOptions()
networkOptions.customBaseURL = URL(string: "https://rkt.example.com")
mParticleOptions.networkOptions = networkOptions

MPNetworkOptions *networkOptions = [MPNetworkOptions new];
networkOptions.customBaseURL = [NSURL URLWithString:@"https://rkt.example.com"];
mParticleOptions.networkOptions = networkOptions;

Please see Identity for more information on supplying an MPIdentityApiRequest object during SDK initialization.

Android

• Grab your mParticle key and secret from your workspace's dashboard and construct an MParticleOptions object.

• Call start from the onCreate method of your app's Application class. It's crucial that the SDK be started here for proper session management. If you don't already have an Application class, create it and then specify its fully-qualified name in the <application> tag of your app's AndroidManifest.xml.

package com.example.myapp;

import android.app.Application;
import com.mparticle.MParticle;

class MyApplication : Application() {
    override fun onCreate() {
        super.onCreate()
        val options: MParticleOptions = MParticleOptions.builder(this)
            .credentials("REPLACE_ME_WITH_KEY", "REPLACE_ME_WITH_SECRET")
            .logLevel(MParticle.LogLevel.VERBOSE)
            .identify(identifyRequest)
            .identifyTask(
                BaseIdentityTask()
                    .addFailureListener() { response -> }
                    .addSuccessListener { result -> }
            )
            .build()
        MParticle.start(options)
    }
}

Routing the Rokt SDK+ through your own domain reduces the risk of ad blockers and browsers from blocking ads or data. You can configure this with NetworkOptions:

import com.mparticle.networking.NetworkOptions;

MParticleOptions options = MParticleOptions.builder(this)
    .credentials("REPLACE_ME_WITH_KEY", "REPLACE_ME_WITH_SECRET")
    .networkOptions(NetworkOptions.withNetworkOptions("https://rkt.example.com"))
    .build();

import com.mparticle.networking.NetworkOptions

val options = MParticleOptions.builder(this)
    .credentials("REPLACE_ME_WITH_KEY", "REPLACE_ME_WITH_SECRET")
    .networkOptions(NetworkOptions.withNetworkOptions("https://rkt.example.com"))
    .build()

Warning: It's generally not a good idea to log events in your Application.onCreate(). Android may instantiate your Application class for a lot of reasons, in the background, while the user isn't even using their device.

Usage

Events

Logging events:

mparticle.logEvent('Test event', mparticle.EventType.Other, { 'Test key': 'Test value' })

Logging commerce events:

var product = new mparticle.Product('Test product for cart', 1234, 19.99)
var transactionAttributes = new mparticle.TransactionAttributes('Test transaction id')
var event = mparticle.CommerceEvent.createProductActionEvent(mparticle.ProductActionType.AddToCart, [product], transactionAttributes)

mparticle.logCommerceEvent(event)

var promotion = new mparticle.Promotion('Test promotion id', 'Test promotion name', 'Test creative', 'Test position')
var event = mparticle.CommerceEvent.createPromotionEvent(mparticle.PromotionActionType.View, [promotion])

mparticle.logCommerceEvent(event)

var product = new mparticle.Product('Test viewed product', 5678, 29.99)
var impression = new mparticle.Impression('Test impression list name', [product])
var event = mparticle.CommerceEvent.createImpressionEvent([impression])

mparticle.logCommerceEvent(event)

Logging screen events:

mparticle.logScreenEvent('Test screen', { 'Test key': 'Test value' })

User

Setting user attributes and tags:

Use Identify or currentUser to retrieve the userID for these calls

var user = new mparticle.User('userID');

user.setUserAttribute(mparticle.UserAttributeType.FirstName, 'Test first name');

user.setUserAttributeArray(mparticle.UserAttributeType.FirstName, ['Test value 1', 'Test value 2']);

user.setUserTag('Test value');

user.removeUserAttribute(mparticle.UserAttributeType.FirstName);

user.getUserIdentities((userIdentities) => {
    console.debug(userIdentities);
});

IdentityRequest

var request = new MParticle.IdentityRequest();

Setting user identities:

var request = new MParticle.IdentityRequest();
request.setUserIdentity('[e-mail]', MParticle.UserIdentityType.Email);

Identity

MParticle.Identity.getCurrentUser(function (userID) => {
    console.debug(userID);
});

Using static methods to update and change identity

var request = new mparticle.IdentityRequest();

var identity = new mparticle.Identity();
identity.identify(request, function (userId) => {
    console.debug(userId);
});

var request = new mparticle.IdentityRequest();
request.email = 'test email';

var identity = new mparticle.Identity();
identity.login(request, function (userId) => {
    console.debug(userId);
});

var request = new mparticle.IdentityRequest();

var identity = new mparticle.Identity();
identity.logout(request, function (userId) => {
    console.debug(userId);
});

var request = new MParticle.IdentityRequest();
request.email = 'test email 2';

var identity = new mparticle.Identity();
identity.modify(request, function (userId) => {
    console.debug(userId);
});

Rokt

Installation

Add the Rokt kit to your config.xml:

<plugin name="@mparticle/cordova-rokt-kit" spec="~> 3.0" />

Select Placements

Display a Rokt overlay placement on your confirmation or thank-you page:

var attributes = {
    'email': '[e-mail]',
    'firstname': 'Jenny',
    'lastname': 'Smith',
    'confirmationref': '54321',
    'country': 'US'
};

mparticle.Rokt.selectPlacements('YourPlacementIdentifier', attributes);

You can optionally pass a configuration object:

var config = {
    colorMode: mparticle.Rokt.ColorMode.SYSTEM,  // LIGHT, DARK, or SYSTEM
    cacheConfig: {
        cacheDurationInSeconds: 5400,
        cacheAttributes: {}
    }
};

mparticle.Rokt.selectPlacements('YourPlacementIdentifier', attributes, config);

Placement Events

Subscribe to lifecycle and engagement events for a specific placement. The callback fires every time the SDK emits an event for the given identifier — call once after deviceready and keep the subscription alive for the lifetime of your view.

mparticle.Rokt.events('YourPlacementIdentifier', function (event) {
    switch (event.event) {
        case mparticle.Rokt.EventType.PlacementInteractive:
            // placement rendered and is interactable
            break;
        case mparticle.Rokt.EventType.OfferEngagement:
        case mparticle.Rokt.EventType.PositiveEngagement:
            // user engaged with the offer
            break;
        case mparticle.Rokt.EventType.PlacementClosed:
        case mparticle.Rokt.EventType.PlacementCompleted:
        case mparticle.Rokt.EventType.PlacementFailure:
            // placement finished — show your next-page content
            break;
    }
});

Each event delivered to your callback is an object with an event discriminator string plus event-specific fields. Cross-platform event types:

Event	Fields	Notes
ShowLoadingIndicator	—	About to call the Rokt backend.
HideLoadingIndicator	—	Backend responded (success or failure).
InitComplete	success	SDK finished initialization.
PlacementReady	placementId	Placement ready but not yet rendered.
PlacementInteractive	placementId	Rendered and ready for user interaction.
PlacementClosed	placementId	User dismissed the placement.
PlacementCompleted	placementId	No more offers to display.
PlacementFailure	placementId (nullable)	Could not be displayed.
OfferEngagement	placementId	User engaged with an offer.
PositiveEngagement	placementId	User accepted an offer.
FirstPositiveEngagement	placementId	First positive engagement in the session.
OpenUrl	placementId, url	Passthrough link requested.
CartItemInstantPurchase	placementId, cartItemId, catalogItemId, currency, description, linkedProductId, totalPrice, quantity, unitPrice	Shoppable Ads purchase completed.

The following event types are iOS only (no Android equivalent in the underlying SDK):

Event	Fields
EmbeddedSizeChanged	placementId, updatedHeight
CartItemInstantPurchaseInitiated	placementId, cartItemId, catalogItemId
CartItemInstantPurchaseFailure	placementId, cartItemId, catalogItemId, error
InstantPurchaseDismissal	placementId
CartItemDevicePay	placementId, cartItemId, catalogItemId, paymentProvider

Shoppable Ads

Shoppable Ads enable post-purchase upsell offers with instant checkout (Apple Pay, AfterPay/Clearpay, PayPal via Stripe). Currently supported on iOS only — selectShoppableAds is a logged no-op on Android, matching the React Native and Flutter wrappers.

1. Add the payment extension kit

<plugin name="@mparticle/cordova-rokt-payment-extension" spec="~> 3.0" />

This contributes the RoktPaymentExtension CocoaPod (~> 2.0) to your iOS target. There is no Android artefact.

2. Register the payment extension from your AppDelegate

RoktPaymentExtension is a pure-Swift class whose failable initialiser isn't @objc-exported, so ObjC AppDelegates need a small Swift shim. See example/platform_overrides/ios/RoktPaymentSetup.swift for the working example:

import Foundation
import RoktPaymentExtension
import mParticle_Apple_SDK_ObjC

@objc public class RoktPaymentSetup: NSObject {
    @objc public static func registerPaymentExtension(merchantId: String) {
        if let paymentExt = RoktPaymentExtension(applePayMerchantId: merchantId) {
            MParticle.sharedInstance().rokt.register(paymentExt)
        }
    }
}

Then call from your AppDelegate after startWithOptions::

#import "YourApp-Swift.h"

[RoktPaymentSetup registerPaymentExtensionWithMerchantId:@"merchant.com.yourapp.rokt"];

The Rokt kit on mParticle Apple SDK 9.2 reads stripePublishableKey from kit configuration in the mParticle dashboard and forwards it to Rokt as stripeKey at registration time — the host only supplies the Apple Pay merchant identifier above.

3. Display Shoppable Ads

var attributes = {
    'email': '[e-mail]',
    'firstname': 'Jenny',
    'lastname': 'Smith',
    'confirmationref': 'ORD-8829-XK2',
    'amount': '52.25',
    'currency': 'USD',
    'paymenttype': 'visa',
    'shippingaddress1': '123 Main St',
    'shippingcity': 'Brooklyn',
    'shippingstate': 'NY',
    'shippingzipcode': '11201',
    'shippingcountry': 'US'
};

mparticle.Rokt.selectShoppableAds('YourPlacementIdentifier', attributes);

4. Handle redirect-based payment callbacks (AfterPay, PayPal)

For payment methods that bounce out to a web flow and return via a custom URL scheme, forward the callback into Rokt:

// iOS — AppDelegate's application:openURL:options:
- (BOOL)application:(UIApplication *)application
            openURL:(NSURL *)url
            options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options {
    if ([[MParticle sharedInstance].rokt handleURLCallback:url]) {
        return YES;
    }
    // fall through to your existing URL routing…
    return NO;
}

Or from JS (when the host has already received the URL and just wants to hand it off):

mparticle.Rokt.handleURLCallback(urlString, function (handled) {
    if (!handled) {
        // route the URL via your own deep-link handler
    }
});

handleURLCallback is iOS-only; the Android bridge logs a warning and resolves to false.

5. Session continuity with WebViews (optional)

If you have a WebView leg of the same flow and want it to share the Rokt session:

mparticle.Rokt.getSessionId(function (sessionId) {
    // pass sessionId into your WebView URL / postMessage
});

// or, when starting a native flow with a session from elsewhere:
mparticle.Rokt.setSessionId('your-session-id');

License

Apache 2.0