Firehose Java SDK

What is mParticle Firehose?

mParticle aims to allow our customers to send their data wherever they want it to go, and we integrate with many services across the mobile-app ecosystem in order to achieve that. mParticle Firehose is an API that lets anybody become one of our integration partners. We support two basic types of Firehose integration:

  • Leveraging Amazon AWS’s Lambda platform, mParticle can send your “lambda function” data as it comes into our system so that your function can then forward it along to your own API.
  • mParticle can forward data to an HTTP endpoint you provide. This gives you the freedom to set up your integration however you like, leveraging your existing architecture.

The Firehose Java SDK can be used for either integration type.

Java SDK Javadocs

Check out the javadocs here

Including this Library

Java Version

Releases of this library are compiled using JDK 1.8 - any project using this library must also be compiled using JDK 1.8.


mParticle deploys the Java SDK to Maven Central as the com.mparticle:java-sdk artifact:

dependencies {
    compile (

Publish to a local Maven repo

Rather than using Maven Central, you can also publish the library to your local Maven server by cloning this repo and invoking the following:

./gradlew publishToMavenLocal


You can clone this project and build the jar manually to include in your project’s classpath:

./gradlew assemble

We also make the latest jar binaries available in the releases section of this repository.

Getting Started

In order to create a Lambda function compatible with mParticle Firehose you’ll be creating a Lambda function just like any other, and then using the Java library in this repository to parse and facilitate communication in between mParticle and your function.

mParticle has created a sample project to get you started quicker, but it may also be useful to read an overview on AWS Lambda here:

Cloning the Sample Project

In order to get started quicker, you can clone the sample project located here:

How the sample project works

The sample project takes care of the basics of creating a lambda function for you. Most importantly it includes a class that implements the RequestStreamHandler interface of the Amazon AWS lambda SDK. When data is received by the RequestStreamHandler, it’s deserialized by the mParticle Java SDK into POJOs to be used by you, as in the following snippet:

 * Sample AWS Lambda Endpoint
public class SampleLambdaEndpoint implements RequestStreamHandler {

    MessageSerializer serializer = new MessageSerializer(); //mParticle class for deserialization

    public void handleRequest(InputStream input, OutputStream output, Context context) throws IOException {
        SampleExtension processor = new SampleExtension(); //you will implement this class in a later step
        Message request = serializer.deserialize(input, Message.class);
        Message response = processor.processMessage(request); //request is processed by you here
        serializer.serialize(output, response);

Implementing MessageProcessor

In the example above, incoming data is deserialized to a Message object, and passed in to SampleExtension. SampleExtension is any class that extends the mParticle Java SDK’s MessageProcessor - which you will implement. This will serve as the entry point to all of your logic and ultimately, the 3rd-party service to which you’re integrating.

Message Processor


The base MessageProcessor implementation is responsible for parsing incoming Message objects. MessageProcessor contains several abstract and empty method implementations responsible for processing Message objects which you will override and implement. Currently, the types of messages are:

  1. Module Registration Request and Response
  2. Event Processing Request and Response
  3. Audience Membership Subscription Request and Response
  4. Audience Subscription Request and Response
  5. DSR Processing Request and Response

To get started creating your MessageProcessor, if you’re using the sample project, open and edit Otherwise, create a class that extends com.mparticle.sdk.MessageProcessor.

All response messages must contain an id element, which contains a guid, and can be the same id sent in the request.

Module Registration

To process the module registration message, override the processRegistrationRequest method in your MessageProcessor. From this method you must return a ModuleRegistrationResponse describing what your integration can do and what it requires to contact your service, such as an API key.

The details of the registration response are outlined below. For a full example of a response object, see the registration response example.

1. Creating your ModuleRegistrationResponse and Describing your Service

mParticle users will see the result of your module registration response in our Integrations directory. You should set a human-readable title for your service (such as your company’s name), as well as a short description of your company including a link to your company’s website with optional tracking parameters. Your description must be less than 230 characters.

This information will be also shown on the mParticle documentation and marketing sites.

Override the processRegistrationRequest method in your MessageProcessor and add the following code, customized for your service:

ModuleRegistrationResponse response = new ModuleRegistrationResponse("My Company Name", "1.0");
response.setDescription("<a href=\"\" target=\"_blank\">My Company</a> empowers brands to meaningfully engage their customers by leveraging data insights. With My Company's help, brands can personalize and cultivate their customer experience.\"");

2. Permissions

Device, User, and Partner Identities

All users and data in the mParticle platform are associated with a set of device IDs (such as an Apple IDFA), a set of user IDs (such as Email), and a set of partner-specific IDs. Event data and audience data received by your integration will always be associated with a user, but your integration must register for permission to receive each ID.

If you mark any of these IDs as required, only users and their associated data that contain at least 1 of these IDs will be sent to your integration.

You can also easily configure that mParticle hash each of these identities in the outgoing payload, using the encoding field. Supported encoding types: RAW, MD5, SHA1, and SHA256, and all hashed values are lowercased before hashing.

Partner Identities

Partner IDs are unique identifiers associated with a user, but specific to a partner system. They can be ingested by mParticle via Partner Feed or S2S, and can be sent to downstream connections associated with the given partner (including a Firehose integration). In order for this to occur, the Partner’s unique identity type name needs to be pre-registered with mParticle, which can be accomplished by simply adding a permission for it.

Currently, only a single Partner ID permission can be registered. Similarly, the name cannot be changed or removed once registered.

The naming convention for these identities is as follows: PartnerName_IdentityName. An example for mParticle could be: mParticle_mpid

Cookie Sync IDs are special Partner IDs that pertain to individual users, and are associated with mParticle Cookie Sync Integrations. If your organization has both a Cookie Sync and Firehose integration with mParticle, you can also configure your Firehose integration’s incoming traffic to include this ID — just as you would for a general Partner ID.

In order to register a Cookie Sync ID, add a Partner ID permission with "type": "$cookie_sync_id"

Device Application Stamp

Device Application Stamp is a UUIDv4-formatted string generated by mParticle for each device.


mParticle ID

The mParticle ID is a unique identifier for a user profile in mParticle.


Location, IP Address and User Agent Header

All mParticle event data can also be associated with location information, and your Firehose integration requires special permissions to access it. Depending on the app and how it has used the mParticle SDK, location information may originate from the device sensors or may be determined, to varying degrees of accuracy, by using reverse IP lookup. If your service needs access to location, you must request access by setting the following:


Data can be sent into the mParticle platform via one of our native or web SDKs, as well as our Events APIs, and will have an associated IP address and HTTP user agent header of the originating client. If your service needs access to the IP address, you must request access by setting the following:

permissions.setAllowAccessIpAddress(true); permissions.setAllowAccessHttpUserAgent(true);

See the example below or the javadocs for more information on populating the Permissions object in your ModuleRegistrationResponse response.

Device Information

mParticle data can contain information about the device being used, including device name, OS Version, and carrier information. By default, this information will not be forwarded to your integration. You can request access to device information with the following:


For a full list of possible device information, see our JSON reference. Note that even if you don’t set this permission, the Device Identities you registered for above will still be forwarded.

User Attributes

mParticle data can include a dictionary of custom user attributes containing information about the user. By default, this information will not be forwarded to your integration. You can request access to user attributes with the following:


This permission is also required to receive User Attribute Change events.

Audience User Attributes

mParticle can include user attributes with audience membership change messages as well as event data. You can request access to audience user attributes with the following:


mParticle allows clients to record consent for data collection from their users. By default, this information will not be forwarded to your integration. You can request access to the user’s consent state by setting:


If enabled, the current consent state will be forwarded for users at the time of the event.

To learn more about the consent state object, reference the following:

Eventless Batches

mParticle allows batches that do not contain any events or system notifications. By default, these batches will not be forwarded to your integration. You can request access to these eventless batches by setting:


Platform Fields

mParticle data can include information about the platform that generated the events with each EventProcessingRequest.

  • AccountId
  • AccountName
  • WorkspaceId
  • InputName (OS or PartnerFeedName)
  • AppName
  • AppVersion
  • DataplanId
  • DataplanName
  • DataplanVersion

By default, the above platform fields will not be forwarded to your integration. You can request access to them by setting:


3. Supported Runtimes

You need to select which platforms you want your integration to receive data from. mParticle’s Firehose forwarder allows you to receive data from the following platforms:

  • IOS
  • ROKU
  • TVOS
  • XBOX

See the example below or the javadocs for more information on populating the Permissions object in your ModuleRegistrationResponse response.

iOS App Tracking Transparency Policy

There are two fields in IosRuntimeEnvironment and TVOSRuntimeEnvironment to support App Tracking Transparency policy. Learn more about Apple’s App Tracking Transparency in our iOS 14 Guide.:

Field Type Description
AttAuthorizationStatus Enum: AttAuthorizationStatus Contains the assigned ATT Authorization status value.
AttTimestampUnixtimeMs long Contains the timestamp of when the authorization status was given.

4. Account Settings

Once we enable your Firehose integration, all mParticle customers will have access to enable it for their account. To allow your integration to correctly identify which customer your data belongs to, and how it should be processed, mParticle enables you to create custom settings for the customer to provide when they set up the account. For example, if your service uses an API Key for authentication:

  1. Your integration must include an account setting representing the API Key (marking it as required and confidential) in the ModuleRegistrationResponse.
  2. When customers configure your integration through mParticle, they will see the API Key setting in a dialogue, and will need to enter their API Key in order to enable the integration.


  3. Once enabled, mParticle will send data to your integration, including the value of the API Key associated with that customer.
  4. Your integration can then use that API Key to make authenticated calls to your API or service.

Settings need to be registered individually for Event, Audience and DSR-based integrations. Each setting will appear in the mParticle UI (unless marked as not-visible), and must contain the following:

  1. ID - you will use this in step 4 above to extract the setting value.
  2. Name - A short, human-readable name which will be shown in the mParticle platform
  3. Description - A description of the setting in the context of your service. This is used as the tooltip in the mParticle platform and so should be kept relatively short. Please refrain from including markdown or external links in these descriptions.
  4. Data Type - The data type of the setting.
  5. Required flag - if true, mutual customers will be required to enter a value for this setting to configure the integration
  6. Confidential flag - if true, the value entered will be masked in the mParticle UI once set

See the following code snippet, the full example below, or the Javadocs for more on the various types of settings and properties of settings.

List<Setting> eventSettings = new ArrayList<>();
Setting apiKey = new TextSetting("apiKey", "API Key")
    .setDescription("Your API Key issued by <insert company here>.");

List<Setting> audienceSettings = new ArrayList<>();

List<Setting> dsrSettings = new ArrayList<>();

5. Authentication Options

Authentication can be set for your Event Registration and/or Audience Registration. DSR Registration does not currently support authentication setup. These settings allow customers to add authentication when configuring your integration in mParticle. Currently, we support OAuth2 authentication, which gets the Access Token and forwards it in requests to your integration. While OAuth2 is a standard protocol, its implementation can differ by identity provider so some parameters may be optional. Depending on the OAuth2 provider, you must include the relevant parameters.

Field Name Required Description
Type Required The authentication type (only OAuth 2.0 is supported). The allowed values are:
  • OAUTH2
Authorization URL Required The Authorization URL initiates the authorization process, authenticating the user with the identity provider.
Refresh URL Optional If the access token has an expiration time the Refresh URL will be used to get a new token.
Token URL Required The Token URL will be used to get the access token after the identity provider returns the Auth Code.
Grant Type Optional The Grant Type specifies the way mParticle gets an access token. The allowed values are:
Default Expires In Optional If the access token expires, this indicates the lifetime (in seconds) of the Access Token.
Client ID Required The Client ID is the public identifier for your application in the identity provider.
Access Token Type Optional The allowed values are:
  • BEARER The Bearer Token is a security scheme to send the token with the following structure Authorization: Bearer <token>.
  • CUSTOM_HEADER The Custom Header type will use a custom HTTP Header to send the access token. The name of the header needs to be specified in the Custom Header Name property.
Custom Header Name Optional If Access Token Type is set to CUSTOM_HEADER you need to specify the name of the Custom Header in which the identity provider can expect the Access Token.
Param Client ID Name Optional The OAuth2 Standard protocol refers to Client ID as client_id. If your identity provider uses a different name for communications you need to specify that name.
Param Secret Name Optional The OAuth2 Standard protocol refers to Client Secret as client_secret. If your identity provider uses a different name for communications you need to specify that name.
Scopes Optional The list of scopes in which your application may access a user’s account.
Name: Name of the scope
Description: Description of the scope

6. Event Registration

If you’re writing an integration that can handle event and analytics data, you’ll specify that your service supports certain types of events in your ModuleRegistrationResponse. This means you will only receive data when those events occur. The possible event types are:

  • Application State Transition
  • Attribution
  • Custom Event
  • Error
  • Impression
  • Privacy Setting Change
  • Product Action
  • Promotion Action
  • Push Message Receipt
  • Push Subscription
  • Screen View
  • Session Start
  • Session End
  • User Attribute Change
  • User Identity Change

Note that to receive User Attribute Change events, you must also register the Allow User Attributes permission. Similarly, for User Identity Change events, you will only receive events for the identities you have set permissions to receive.

See here for brief descriptions of each event type.

System Notification Types

System Notifications are used to communicate changes to a user. Currently, the available System Notifications are:

Note that System Notifications related to Consent States describe changes to the consent state. As such, they each contain both the old and the new consent states. These notifications are different from the actual Consent State object.

Max Data Age

This setting lets mParticle know if historical events can be sent to your integration. The default is 24 hours, however if your platform can receive and process older data, you can set this to a higher value, or to -1 to process all data.

EventProcessingRegistration eventProcessingRegistration = new EventProcessingRegistration();

7. Push Messaging Provider ID

If you have registered for Push Message Receipt events, you must provide the Provider ID key used in the payload of your platform’s Push messages. This ensures that you only receive events related to Push messages from your platform. Work with mParticle to ensure you are providing the correct Provider ID.


8. Audience Registration

Audience Registration will allow your integration to receive Audience Subscription and Membership messages. During registration, your integration needs to specify the settings required to map and send audience data from mParticle to your service:

  1. Account Settings are required, user-modifiable settings for your integration.
  2. Audience Subscription Settings are optional, audience-specific settings such as an audience ID from your service. These settings can be set manually by the user or can be set programatically.
  • To allow users to set and modify a subscription setting value, mark the subscription setting as visible. The user will be prompted to enter a value when connecting an audience, and you will see this value in your audience subscription requests and audience membership change requests.
  • To set a subscription setting value programmatically, mark a subscription setting as not visible. You will set the value after a user connects an audience as part of your audience subscription response. Subsequent membership change requests will contain the returned value.

Audience Subscription Settings can be included in your module registration response as shown here.

More information about AudienceProcessingRegistration

Bulk Configuration

These settings allow you to enable bulk forwarding, which is supported by audience integrations. The following are the two settings that you can configure:

  1. Bulk Forward Wait For Messages: This setting determines the number of messages that mParticle will wait to see before forwarding them to the integration. Please note that this is not the exact number of messages that mParticle will send, since there could be a greater number of messages collected at the moment this validation is executed on mParticle side.
  2. Bulk Forward Wait In Minutes: This setting determines the amount of time (in minutes) that mParticle will wait before trying to forward messages.

It is important to note that these settings are not dependent on each other, so you can set one or the other, or both. If one of the settings is not set, mParticle will use a default value for that specific setting. For Bulk Forward Wait For Messages, the default value is 2000 messages, and for Bulk Forward Wait In Minutes, the default value is 12 hours (720 minutes).

More information about BulkConfiguration

9. DSR Registration

DSR Registration will allow the integration to receive Data Subject Request (DSR) erasure requests. In order for Firehose partners to opt-in to DSR support, a DSR Processing Registration should be specified with the following information:

  1. Account Settings should be specified with any required setting information that will be needed to complete the DSR API request.
  2. Permission should have at least 1 DSR Supported Identity Types. For more information on DSR Supported Identity Types, go here.
  3. Domain should be defined in DsrRegistration, It is used to make Callback requests. For more information on Callbacks, go here.
  4. The DSR Processing Request Type is required. Currently, the only supported request type is Erasure.

Sample Registration

Refer to the sample project or the simple example below, which shows how to subscribe for Event Processing, Audience and DSR Processing:

   public ModuleRegistrationResponse processRegistrationRequest(ModuleRegistrationRequest request) {
      // Set the permissions, including the identities that this service can have access to
      Permissions permissions = new Permissions();
            new DeviceIdentityPermission(DeviceIdentity.Type.IOS_ADVERTISING_ID, Identity.Encoding.RAW, true),
            new DeviceIdentityPermission(DeviceIdentity.Type.GOOGLE_ADVERTISING_ID, Identity.Encoding.RAW, true)
            new UserIdentityPermission(UserIdentity.Type.EMAIL, Identity.Encoding.RAW),
            new UserIdentityPermission(UserIdentity.Type.CUSTOMER, Identity.Encoding.RAW)
            new PartnerIdentityPermission("[partner name]_[id name]", Identity.Encoding.RAW, false)

      // The extension needs to define the settings it needs in order to connect to its respective service(s).
      // You can use different settings for Event Processing, Audience Processing or DSR Processing, but in this case
      // we'll just use the same object, specifying that only an API key is required for each.
      List<Setting> settings = Arrays.asList(
         new TextSetting("apiKey", "API Key")
         .setDescription("Your API key issued by <insert company here>.")

      // Specify the supported event types. You should override the parent MessageProcessor methods
      // that correlate to each of these event types.
      List<Event.Type> supportedEventTypes = Arrays.asList(

      // This extension only supports event data coming from Android and iOS devices
      List<RuntimeEnvironment.Type> environments = Arrays.asList(

      // Set the Event Registration by using all of the above
      EventProcessingRegistration eventRegistration = new EventProcessingRegistration();
      OAuth2Authentication eventAuthentication = new OAuth2Authentication();

         .setAuthorizationUrl("Authorization URL")
         .setRefreshUrl("Refresh URL")
         .setTokenUrl("Token URL")
         .setClientId("Client ID")
         .setCustomHeaderName("Custom Header Name")
         .setParamClientIdName("Param Client ID Name")
         .setParamSecretName("Param Secret Name")
         .setScopes(new ScopeDetail[]{new ScopeDetail()
               .setName("Scope Name")
               .setDescription("Scope Description")


      // Set the audience subscription settings
      List<Setting> subscriptionSettings = Arrays.asList(
         new IntegerSetting(SETTING_MAILING_LIST_ID, "Mailing List ID"),
         new IntegerSetting(SETTING_INTERNAL_LIST_ID, "Internal ID")

      // Set up Audience Registration.
      AudienceProcessingRegistration audienceRegistration = new AudienceProcessingRegistration();
      OAuth2Authentication audienceAuthentication = new OAuth2Authentication();

         .setAuthorizationUrl("Authorization URL")
         .setRefreshUrl("Refresh URL")
         .setTokenUrl("Token URL")
         .setClientId("Client ID")
         .setCustomHeaderName("Custom Header Name")
         .setParamClientIdName("Param Client ID Name")
         .setParamSecretName("Param Secret Name")
         .setScopes(new ScopeDetail[]{new ScopeDetail()
               .setName("Scope Name")
               .setDescription("Scope Description")

      // Segmentation/Audience registration and processing is treated separately from Event processing.
      // Audience integrations are configured separately in the mParticle UI.
      // Customers can configure a different set of account-level settings (such as API key here), and
      // Segment-level settings (Mailing List ID here).

      // Specify the supported DSR request types.
      List<DsrProcessingRequest.Type> supportedDsrTypes = Arrays.asList(DsrProcessingRequest.Type.Erasure);

      // Set up DSR Registration
      DsrProcessingRegistration dsrRegistration = new DsrProcessingRegistration();

      // Set the response
      ModuleRegistrationResponse response = new ModuleRegistrationResponse("Your Company Name", "1.0");
         .setDescription("A description of your <a href=''>company</a> and services. Inline HTML markup is permitted.")
      return response;


Once you have completed the implementation of your registration, you must send the result to mParticle for verification. See testing for more information.

Event Processing

mParticle customers send batches of events to the mParticle platform via the mParticle SDKs (iOS, Android, Javascript, etc), direct Events data or feeds. mParticle can forward these event batches to your integration. The base MessageProcessor implementation is designed to handle these incoming batches of events, and appropriately iterate over each different event, providing you with convenient hooks in which to handle each distinct event type.

In order to process these events, you’ll override (in your MessageProcessor subclass) the appropriate method given the event types that you registered for during module registration.

Event Object

Each event hook method is given an object that contains the event itself as well as information about the user, device, and application that fired the event.

See here for more on the Event object from which all other events inherit.

Event Methods

The following table shows the correlation between each type and overridable method:

Event Type Method
APPLICATION_STATE_TRANSITION MessageProcessor#processApplicationStateTransitionEvent
ATTRIBUTION MessageProcessor#processAttributionEvent
CUSTOM_EVENT MessageProcessor#processCustomEvent
ERROR MessageProcessor#processErrorEvent
IMPRESSION MessageProcessor#processImpressionEvent
PRIVACY_SETTING_CHANGE MessageProcessor#processPrivacySettingChangeEvent
PRODUCT_ACTION MessageProcessor#processProductActionEvent
PROMOTION_ACTION MessageProcessor#processPromotionActionEvent
PUSH_MESSAGE_RECEIPT MessageProcessor#processPushMessageReceiptEvent
PUSH_SUBSCRIPTION MessageProcessor#processPushSubscriptionEvent
SCREEN_VIEW MessageProcessor#processScreenViewEvent
SESSION_END MessageProcessor#processSessionEndEvent
SESSION_START MessageProcessor#processSessionStartEvent
USER_ATTRIBUTE_CHANGE MessageProcessor#processUserAttributeChangeEvent
USER_IDENTITY_CHANGE MessageProcessor#processUserIdentityChangeEvent

Verification Requests

To ensure a continuous connection with your integration, mParticle will periodically send event processing requests, even if there are no new events to send. Your integration must be able to accept an empty events array and return a standard event processing response.

Custom Flags

Custom flags will be sent to your integration when available for supported event types when the custom flag key prefix matches your integration’s module name. For more information, see the Custom Flags JSON reference.

Audience Processing

Audience Subscription Event

The audience subscription event tells your integration when a new audience has been created, removed, and/or updated in the mParticle platform. The response allows you to set additional subscription settings that will be stored together with the subscription and sent back with audience membership changes. All subscription settings must be declared during module registration.

See here for more info on the AudienceSubscriptionRequest object that you’ll be given to parse the event.

Audience Membership Change Event

The audience membership change event tells your integration whenever users are added or removed from a given audience. If you have set permissions.setAllowAudienceUserAttributeSharing(true), each audience will also include any user attributes the customer has shared.

See here for more info on the AudienceMembershipChangeRequest object that you’ll be given to parse the event.

Verification Requests

To ensure a continuous connection with your integration, mParticle will periodically send audience membership change requests, even if there are no new changes in audience membership. Your integration must be able to accept an empty audience membership change request (a request with no “user_profiles” fields, as shown below) and return a standard audience membership change response. If a user’s configuration should be faulted due to a non-transient error (an expired API token, for example), you can set suspend_subscription to true in the response. This will stop mParticle from sending requests until the user resumes the configuration.

    "account_id": 123456,
      "Example String Setting" : "Example Setting Value"

DSR Processing

mParticle supports the forwarding of Data Subject Requests (DSRs) for deletion of user data downstream, complying with both the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA). Note, once a request is forwarded downstream, mParticle is not liable for data deletion for any configured partners. Results will be explicitly indicated in our UI. To learn more about mParticle’s DSR support, go here. To process the DSR request, at least one supported identity type must be present in the request.

See here for more info on the DsrProcessingRequest that the integration will receive.

Supported Request Types

mParticle’s DSR implementation currently only handles the Erasure request type.

Supported Identity Types

The identity types supported for DSR integrations are:

Identity Type Description
ANDROID_ADVERTISING_ID The user’s Android Advertising Id
ANDROID_ID The user’s Android Id
EMAIL The user’s Email Address
FIRE_ADVERTISING_ID The user’s Fire Advertising Id
IOS_ADVERTISING_ID The user’s iOS Advertising Id
IOS_VENDOR_ID The user’s iOS Vendor Id
MICROSOFT_ADVERTISING_ID The user’s Microsoft Advertising Id
MICROSOFT_PUBLISHER_ID The user’s Microsoft Publisher Id
ROKU_PUBLISHER_ID The user’s Roku Publisher Id
ROKU_ADVERTISING_ID The user’s Roku Advertising Id


Registration Testing

Prior to deployment, please send mParticle the JSON result of your registration response. There are several ways to easily acquire the JSON:

Unit tests in the sample project

The latest Firehose Sample integration includes a unit test which will output the result of your registration function. See the Sample Firehose Integration README for more information. This is the quickest way to verify the contents of your module registration.

Manually send in a registration request via the AWS console

If you’re unable to run the unit tests, you may also deploy your function to AWS and then use this sample JSON (also available here) as a test event within the AWS console:


Additional Unit Testing

In order to ensure that your lambda function works correctly, we recommend unit testing prior to deployment. Unit testing is quicker and easier than manually sending in JSON to your lambda function via AWS.

Integration Testing

You can send JSON messages manually into your lambda function via the AWS-lambda console.

See here for sample JSON that you can use.


Once you’ve completed development and feel you’ve sufficiently tested your integration, the next step is to register and add it to the mParticle platform. This is a multistep process:

Step 1 (AWS Lambda) - Grant Permissions

You will need to grant mParticle permissions to call your lambda function. Using the Amazon CLI tool, execute the commands below, altering them for your environment:

  • change the --function-name argument (arn:aws:lambda:us-east-1:123456789:function:myLambdaFunction:production) to the full ARN of your lambda function. This can be found by navigating to your AWS Lambda console and selecting your lambda function.
  • you should be using an alias for your lambda function to allow for additional development and testing while your integration is live. In the commands below, be sure to append your production alias name to your lambda-function’s ARN. The examples below use an alias named “production”. See here for more information on Aliases.
  • statement-id must be unique - if you receive an error stating that the provided statement-id already exists, increment the statement-id(s) to a higher value.
aws lambda add-permission \
--region us-east-1 \
--function-name arn:aws:lambda:us-east-1:123456789:function:myLambdaFunction:production \
--statement-id 1 \
--principal 338661164609 \
--action lambda:InvokeFunction
aws lambda add-permission \
--region us-east-1 \
--function-name arn:aws:lambda:us-east-1:123456789:function:myLambdaFunction:production \
--statement-id 2 \
--principal 457804467337 \
--action lambda:InvokeFunction

Step 1 (HTTP) - Expose endpoint

For HTTP integrations, your endpoint must be able to receive HTTP requests.

Once permissions have been granted, mParticle will use an internal tool to send a registration request to your integration. We will work with you to ensure that your registration response looks correct and that it includes what’s necessary for your service.

mParticle requires a high-resolution logo to represent your service in our dashboard. The logo must:

  • be provided in SVG format
  • have a transparent background
  • be easily readable when set on top of a white or light-colored page

Provide mParticle with credentials for the required fields from your registration response for testing configuration.

Step 3 - Final testing and release

Once your integration has been registered and added to the mParticle platform, we will work with you to perform final testing prior to making your service available to all mParticle customers.

Data Rate and Volume

mParticle servers will stream data to your function at the same rate at which it is received. By default, AWS lambda allows for 100 concurrent executions of your function. If your lambda function reaches this limit, mParticle will continually retry requests with a back-off until they have succeeded. If you are expecting a large customer integration, it is recommended that you request a higher limit by opening a case with AWS Support.

See here for more information on AWS rate limiting and how to increase your limit.

Keep this in mind as you’re developing your lambda function as it may determine how it should process and to which of your APIs you should send data. Data rate and volume will depend on:

  1. The size of the customer that has enabled your integration.
  2. The amount of/types of data for which you register.
  3. If you’ve registered to receive Audience data, the volatility and size of a given customer’s audiences.

For HTTP Integrations, you will need to have infrastructure in place to support a high volume of data.

Was this page helpful?