Flutter allows developers to use a single code base to deploy to multiple platforms. Now, with the mParticle Flutter Plugin, you can leverage a single API to deploy your data to hundreds of integrations from your iOS, Android, and Web apps.
See the table below to see what features are currently supported
Method | Android | iOS | Web | Notes |
---|---|---|---|---|
Custom Events | X | X | X | |
Page Views | X | X | X | |
Identity | X | X | X | |
eCommerce | X | X | X | |
Consent | X | X | X |
flutter pub add mparticle_flutter_sdk
Specifying this dependency adds a line like the following to your package's pubspec.yaml
:
dependencies:
mparticle_flutter_sdk: ^0.0.1
import 'package:mparticle_flutter_sdk/mparticle_flutter_sdk.dart'
Now that you have the mParticle Dart plugin, install mParticle on your native/web platforms. Be sure to include an API Key and Secret where required or you will see errors in your logs when launching your app.
To install mParticle on an Android platform:
build.gradle
:dependencies {
implementation 'com.mparticle:android-core:5+'
// Required for gathering Android Advertising ID (see below)
implementation 'com.google.android.gms:play-services-ads-identifier:16.0.0'
// Recommended to query the Google Play install referrer
implementation 'com.android.installreferrer:installreferrer:1.0'
}
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;
public class MyApplication extends Application {
@Override
public void onCreate() {
super.onCreate();
MParticleOptions options = MParticleOptions.builder(this)
.credentials("REPLACE ME WITH KEY","REPLACE ME WITH SECRET")
.setLogLevel(MParticle.LogLevel.VERBOSE)
.identify(identifyRequest)
.identifyTask(
new BaseIdentityTask()
.addFailureListener(this)
.addSuccessListener(this)
)
.attributionListener(this)
.build();
MParticle.start(options);
}
}
import com.mparticle.MParticle
import com.mparticle.MParticleOptions
class ExampleApplication : Application() {
override fun onCreate() {
super.onCreate()
val options = MParticleOptions.builder(this)
.credentials("REPLACE ME WITH KEY", "REPLACE ME WITH SECRET")
.build()
MParticle.start(options)
}
}
Warning: Don't log events in your
Application.onCreate()
. Android may instantiate yourApplication
class for a lot of reasons, in the background, while the user isn't even using their device. For more help, see the Android set up docs.
Configuring iOS:
To install mParticle on an iOS platform:
Copy your mParticle key and secret** from your app's dashboard.
Install the SDK using CocoaPods:
$ # Update your Podfile to depend on 'mParticle-Apple-SDK' version 8.5.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 you must initialize the SDK in the
application:didFinishLaunchingWithOptions:
method. Other parts of the SDK rely on theUIApplicationDidBecomeActiveNotification
notification to function properly. Failing to start the SDK as indicated will impair it. Also, please do not use GCD'sdispatch_async
to start the SDK. For more help, see the full iOS set up docs.
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 = "email@example.com"
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")
}
mParticleOptions.onAttributionComplete = { (attributionResult, error) in
NSLog("Attribution Complete. attributionResults = %@", attributionResult?.linkInfo ?? "Null attributionResults")
}
//Start the SDK
MParticle.sharedInstance().start(with: mParticleOptions)
return true
}
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 = @"email@example.com";
mParticleOptions.identifyRequest = request;
mParticleOptions.onIdentifyComplete = ^(MPIdentityApiResult * _Nullable apiResult, NSError * _Nullable error) {
NSLog(@"Identify complete. userId = %@ error = %@", apiResult.user.userId, error);
};
mParticleOptions.onAttributionComplete(MPAttributionResult * _Nullable attributionResult, NSError * _Nullable error) {
NSLog(@"Attribution Complete. attributionResults = %@", attributionResult.linkInfo)
}
[[MParticle sharedInstance] startWithOptions:mParticleOptions];
return YES;
}
See Identity for more information on supplying an MPIdentityApiRequest
object during SDK initialization.
Add the mParticle snippet to your web/index.html
file as high as possible on the page within the
<script type="text/javascript">
//configure the SDK
window.mParticle = {
config: {
isDevelopmentMode: true,
identifyRequest: {
userIdentities: {
email: 'email@example.com',
customerid: '123456',
},
},
identityCallback: (response) {
console.log(response);
},
dataPlan: {
planId: 'my_plan_id',
planVersion: 2
}
},
};
//load the SDK
(
function(t){window.mParticle=window.mParticle||{};window.mParticle.EventType={Unknown:0,Navigation:1,Location:2,Search:3,Transaction:4,UserContent:5,UserPreference:6,Social:7,Other:8};window.mParticle.eCommerce={Cart:{}};window.mParticle.Identity={};window.mParticle.config=window.mParticle.config||{};window.mParticle.config.rq=[];window.mParticle.config.snippetVersion=2.3;window.mParticle.ready=function(t){window.mParticle.config.rq.push(t)};var e=["endSession","logError","logBaseEvent","logEvent","logForm","logLink","logPageView","setSessionAttribute","setAppName","setAppVersion","setOptOut","setPosition","startNewSession","startTrackingLocation","stopTrackingLocation"];var o=["setCurrencyCode","logCheckout"];var i=["identify","login","logout","modify"];e.forEach(function(t){window.mParticle[t]=n(t)});o.forEach(function(t){window.mParticle.eCommerce[t]=n(t,"eCommerce")});i.forEach(function(t){window.mParticle.Identity[t]=n(t,"Identity")});function n(e,o){return function(){if(o){e=o+"."+e}var t=Array.prototype.slice.call(arguments);t.unshift(e);window.mParticle.config.rq.push(t)}}var dpId,dpV,config=window.mParticle.config,env=config.isDevelopmentMode?1:0,dbUrl="?env="+env,dataPlan=window.mParticle.config.dataPlan;dataPlan&&(dpId=dataPlan.planId,dpV=dataPlan.planVersion,dpId&&(dpV&&(dpV<1||dpV>1e3)&&(dpV=null),dbUrl+="&plan_id="+dpId+(dpV?"&plan_version="+dpV:"")));var mp=document.createElement("script");mp.type="text/javascript";mp.async=true;mp.src=("https:"==document.location.protocol?"https://jssdkcdns":"http://jssdkcdn")+".mparticle.com/js/v2/"+t+"/mparticle.js" + dbUrl;var c=document.getElementsByTagName("script")[0];c.parentNode.insertBefore(mp,c)}
)("REPLACE WITH API KEY");
</script>
For more help, see the full Web set up docs.
Each of our Dart methods is mapped to an underlying mParticle SDK at the platform level. Note that per Dart's [documentation](https://flutter.dev/docs/development/platform-integration/platform-channels#architecture, calling into platform specific code is asynchronous to ensure the user interface remains responsive. In your code, you can swap usage between async
and then
in accordance to your app's requirements.
For a full description of all classes, methods, and properties, see the mParticle Flutter SDK API Reference.
Importing the module:
import 'package:mparticle_flutter_sdk/mparticle_flutter_sdk.dart';
You must first call getInstance
on MparticleFlutterSdk
before each method is called. This ensures the underlying mParticle SDK has been initialized. Per Flutter's plugin documentation, messages between the Dart plugin and underlying platforms must be passed asynchronously to ensure the user interface remains responsive. Therefore, to ensure code is performant to your team's requirements, you may refactor instances of await
with then
and vice versa in the examples below.
MparticleFlutterSdk? mpInstance = await MparticleFlutterSdk.getInstance();
To log events, import mParticle EventTypes
and MPEvent
to write proper event logging calls:
import 'package:mparticle_flutter_sdk/events/event_type.dart';
import 'package:mparticle_flutter_sdk/events/mp_event.dart';
MPEvent event = MPEvent(
eventName: 'Test event logged',
eventType: EventType.Navigation)
..customAttributes = { 'key1': 'value1' }
..customFlags = { 'flag1': 'value1' };
mpInstance?.logEvent(event);
If you have a high-volume event that you would like to forward to client side kits but exclude from uploading to mParticle, set a boolean flag per event.
import 'package:mparticle_flutter_sdk/events/event_type.dart';
import 'package:mparticle_flutter_sdk/events/mp_event.dart';
MPEvent event = MPEvent(
eventName: 'Test event logged',
eventType: EventType.Navigation)
..customAttributes = {'key1': 'value1'}
..customFlags = {'flag1': 'flagValue1'}
..shouldUploadEvent = false;
mpInstance?.logEvent(event);
By default, all events upload to the mParticle server unless explicitly set not to. This is also available on Commerce Events when calling logCommerceEvent
. Support for logScreenEvent
will be coming in the future.
To log screen events, import mParticle ScreenEvent
:
import 'package:mparticle_flutter_sdk/events/screen_event.dart';
ScreenEvent screenEvent =
ScreenEvent(eventName: 'Screen event logged')
..customAttributes = {'key1': 'value1'}
..customFlags = {'flag1': 'flagValue1'};
mpInstance?.logScreenEvent(screenEvent);
To log product commerce events, import CommerceEvent
, Product
and ProductActionType
(optionally TransactionAttributes
)
import 'package:mparticle_flutter_sdk/events/commerce_event.dart';
import 'package:mparticle_flutter_sdk/events/product.dart';
import 'package:mparticle_flutter_sdk/events/product_action_type.dart';
import 'package:mparticle_flutter_sdk/events/transaction_attributes.dart';
final Product product1 = Product(name: 'Orange', sku: '123abc', price: 2.4);
final Product product2 = Product(
name: 'Apple',
sku: '456abc',
price: 4.1,
quantity: 2,
variant: 'variant',
category: 'category',
brand: 'brand',
position: 1,
couponCode: 'couponCode',
attributes: {'key1': 'value1'});
final TransactionAttributes transactionAttributes =
TransactionAttributes(
transactionId: '123456',
affiliation: 'affiliation',
couponCode: '12412342',
shipping: 1.34,
tax: 43.23,
revenue: 242.23);
CommerceEvent commerceEvent = CommerceEvent.withProduct(
productActionType: ProductActionType.Purchase,
product: product1)
..products.add(product2)
..transactionAttributes = transactionAttributes
..currency = 'US'
..screenName = 'One Click Purchase'
..customAttributes = {"foo": "bar", "fuzz": "baz"}
..customFlags = {
"flag1": "val1",
"flag2": ["val2", "val3"]
};
mpInstance?.logCommerceEvent(commerceEvent);
To log promotion commerce events, import CommerceEvent
, Promotion
and PromotionActionType
:
import 'package:mparticle_flutter_sdk/events/commerce_event.dart';
import 'package:mparticle_flutter_sdk/events/promotion.dart';
import 'package:mparticle_flutter_sdk/events/promotion_action_type.dart';
final Promotion promotion1 = Promotion(
promotionId: '12312',
creative: 'Jennifer Slater',
name: 'BOGO Bonanza',
position: 'top');
final Promotion promotion2 = Promotion(
promotionId: '15632',
creative: 'Gregor Roman',
name: 'Eco Living',
position: 'mid');
CommerceEvent commerceEvent = CommerceEvent.withPromotion(
promotionActionType: PromotionActionType.View,
promotion: promotion1)
..promotions.add(promotion2)
..currency = 'US'
..screenName = 'PromotionScreen'
..customAttributes = {"foo": "bar", "fuzz": "baz"}
..customFlags = {
"flag1": "val1",
"flag2": ["val2", "val3"]
};
mpInstance?.logCommerceEvent(commerceEvent);
To log impression commerce events, import CommerceEvent
, Impression
and Product
import 'package:mparticle_flutter_sdk/events/commerce_event.dart';
import 'package:mparticle_flutter_sdk/events/impression.dart';
import 'package:mparticle_flutter_sdk/events/product.dart';
final Product product1 = Product(
name: 'Orange', sku: '123abc', price: 2.4, quantity: 1);
final Product product2 = Product(
name: 'Apple',
sku: '456abc',
price: 4.1,
quantity: 2,
variant: 'variant',
category: 'category',
brand: 'brand',
position: 1,
couponCode: 'couponCode',
attributes: {'key1': 'value1'});
final Impression impression1 = Impression(
impressionListName: 'produce',
products: [product1, product2]);
final Impression impression2 = Impression(
impressionListName: 'citrus', products: [product1]);
CommerceEvent commerceEvent =
CommerceEvent.withImpression(impression: impression1)
..impressions.add(impression2)
..currency = 'US'
..screenName = 'ImpressionScreen'
..customAttributes = {"foo": "bar", "fuzz": "baz"}
..customFlags = {
"flag1": "val1",
"flag2": ["val2", "val3"]
};
mpInstance?.logCommerceEvent(commerceEvent);
Get the current user in order to apply and remove attributes, tags, etc.
var user = await mpInstance?.getCurrentUser();
User Attributes:
user?.setUserAttribute(key: 'points', value: '1');
user?.setUserAttributeArray(
key: 'arrayOfStrings', value: ['a', 'b', 'c']);
user?.setUserTag(tag: 'tag1');
user?.getUserAttributes();
user?.removeUserAttribute(key: 'points');
user?.getUserIdentities().then((identities) {
print(identities); // Map<IdentityType, String>
});
IDSync is mParticle’s identity framework, enabling our customers to create a unified view of the customer. To read more about IDSync, see here.
All IDSync calls require an Identity Request
.
import 'package:mparticle_flutter_sdk/identity/identity_type.dart';
var identityRequest = MparticleFlutterSdk.identityRequest;
identityRequest
.setIdentity(
identityType: IdentityType.CustomerId,
value: 'customerid')
.setIdentity(
identityType: IdentityType.Email,
value: 'email@gmail.com');
After an IdentityRequest is passed to one of the following IDSync methods - identify
, login
, logout
, or modify
.
Import the SuccessResponse
and FailureResponse
classes to write proper callbacks for Identity methods. For brevity, we included an example of full error handling in only the identify
example below, but this error handling can be used for any of the Identity calls.
The following is a full Identify example with error and success handling. You can adapt the following example with login
, modify
, and logout
.
import 'package:mparticle_flutter_sdk/identity/identity_api_result.dart';
import 'package:mparticle_flutter_sdk/identity/identity_api_error_response.dart';
var identityRequest = MparticleFlutterSdk.identityRequest;
mpInstance?.identity
.identify(identityRequest: identityRequest)
.then(
(IdentityApiResult successResponse) =>
print("Success Response: $successResponse"),
onError: (error) {
var failureResponse = error as IdentityAPIErrorResponse;
print("Failure Response: $failureResponse");
// It is possible for either a client error or a server error to occur during identity calls.
// First check for the client side error, then you can check the http code for the server error.
// More details can be found in the platform specific IDSync error handling:
// iOS - https://docs.mparticle.com/developers/sdk/ios/idsync/#error-handling
// Web - https://docs.mparticle.com/developers/sdk/web/idsync/#error-handling
// Android - https://docs.mparticle.com/developers/sdk/android/idsync/#idsync-status-codes
if (failureResponse.clientErrorCode != null) {
switch (failureResponse.clientErrorCode) {
case IdentityClientErrorCodes.RequestInProgress:
// there is an Identity request in progress, wait for it to complete before attempting another
case IdentityClientErrorCodes.ClientSideTimeout:
case IdentityClientErrorCodes.ClientNoConnection:
// retry the IDSync request
case IdentityClientErrorCodes.SSLError:
// SSL configuration issue.
case IdentityClientErrorCodes.OptOut:
// The user has opted out of data collection
case IdentityClientErrorCodes.Unknown:
//
case IdentityClientErrorCodes.ActiveSession:
case IdentityClientErrorCodes.ValidationIssue:
// A web error that should never arise due to Dart's stronger typing
case IdentityClientErrorCodes.NativeIdentityRequest:
default:
print(failureResponse.clientErrorCode);
}
}
int? httpCode = failureResponse.httpCode;
if (httpCode != null && httpCode >= 400) {
switch (httpCode) {
case 400:
case 401:
case 429:
case 529:
default:
failureResponse.errors.forEach(
(error) => print('${error.code}\n${error.message}'));
}
}
}
);
Partial example - you can adapt the identify example above with login, modify, and logout.
var identityRequest = MparticleFlutterSdk.identityRequest;
identityRequest
.setIdentity(
identityType: IdentityType.CustomerId,
value: 'customerid2')
.setIdentity(
identityType: IdentityType.Email,
value: 'email2@gmail.com');
mpInstance?.identity.login(identityRequest: identityRequest).then(
(IdentityApiResult successResponse) =>
print("Success Response: $successResponse"),
onError: (error) {
var failureResponse = error as IdentityAPIErrorResponse;
print("Failure Response: $failureResponse");
});
Partial example - you can adapt the identify
example above with login
, modify
, and logout
.
var identityRequest = MparticleFlutterSdk.identityRequest;
identityRequest
.setIdentity(
identityType: IdentityType.CustomerId,
value: 'customerid3')
.setIdentity(
identityType: IdentityType.Email,
value: 'email3@gmail.com');
mpInstance?.identity
.modify(identityRequest: identityRequest)
.then(
(IdentityApiResult successResponse) =>
print("Success Response: $successResponse"),
onError: (error) {
var failureResponse = error as IdentityAPIErrorResponse;
print("Failure Response: $failureResponse");
}
);
Partial example - you can adapt the identify
example above with login
, modify
, and logout
.
var identityRequest = MparticleFlutterSdk.identityRequest;
// depending on your identity strategy, you may have identities added to your identityRequestk
mpInstance?.identity
.logout(identityRequest: identityRequest)
.then(
(IdentityApiResult successResponse) =>
print("Success Response: $successResponse"),
onError: (error) {
var failureResponse = error as IdentityAPIErrorResponse;
print("Failure Response: $failureResponse");
}
);
This is a feature to transition data from "anonymous" users to "known" users. To learn more about user aliasing, see here.
mpInstance?.identity
.login(identityRequest: identityRequest)
.then((IdentityApiResult successResponse) {
String? previousMPID =
successResponse.previousUser?.getMPID();
if (previousMPID != null) {
var userAliasRequest = AliasRequest(
sourceMpid: previousMPID,
destinationMpid: successResponse.user.getMPID());
mpInstance?.identity
.aliasUsers(aliasRequest: userAliasRequest);
}
}
);
To learn more about Consent on mParticle, see here;
GDPR Consent requires a user to add it do:
var user = await mpInstance?.getCurrentUser();
To set a GDPR Consent State:
Consent gdprConsent = Consent(
consented: false,
document: 'document test',
hardwareId: 'hardwareID',
location: 'loction test',
timestamp: DateTime.now().millisecondsSinceEpoch);
user?.addGDPRConsentState(consent: gdprConsent, purpose: 'test');
To get a GDPR Consent State:
Map<String, Consent>? gdprConsent = await user?.getGDPRConsentState(); // String is the purpose set above
To set a CCPA Consent State:
Consent ccpaConsent = Consent(
consented: false,
document: 'document test',
hardwareId: 'hardwareID',
location: 'loction test',
timestamp: DateTime.now().millisecondsSinceEpoch);
user?.addCCPAConsentState(consent: ccpaConsent);
To get a CCPA Consent State:
Consent? ccpaConsent = await user?.getCCPAConsentState();
A few methods are currently supported only on iOS/Android SDKs:
Get the SDK's opt out status
var isOptedOut = await mpInstance?.getOptOut;
mpInstance?.setOptOut(optOutBoolean: !isOptedOut!);
Check if a kit is active
import 'package:mparticle_flutter_sdk/kits/kits.dart';
mpInstance?.isKitActive(kit: Kits['Braze']!).then((isActive) {
print(isActive);
});
Push Registration
The method mpInstance.logPushRegistration()
accepts two parameters. For Android, provide both pushToken
and senderId
. For iOS, provide the push token in the first parameter, and simply pass null
for the second parameter
mpInstance?.logPushRegistration(pushToken: 'pushToken123', senderId: 'senderId123');
mpInstance?.logPushRegistration(pushToken: 'pushToken123', senderId: null);
Set App Tracking Transparency (ATT) Status
For iOS, you can set a user's ATT status as follows: import 'package:mparticle_flutter_sdk/apple/authorization_status.dart';
mpInstance?.setATTStatus(
attStatus: MPATTAuthorizationStatus.Authorized,
timestampInMillis: DateTime.now().millisecondsSinceEpoch);
Apache 2.0