Currently, we support:
Implementing mParticle can range based upon your objectives. Depending on if you’re solving for speed and simplicity or if you’re going for total control, mParticle can be implemented in as little as 5 minutes.
We take data ownership very seriously which means your data is your data and yours alone. You decide what you want to do with it. We do not combine data across clients for our own marketing purposes or co-mingle client data in any way.
It varies by plan, and each plan can be customized further depending on how long you want your data to be readily available.
Your data can be exported or will be deleted within 30 days.
Not to worry! We store your data on Amazon S3 and then again on Amazon Glacier for long term storage. Amazon S3 has never had an outage resulting in data loss and is designed to provide 99.999999999% durability of objects over a given year. If an integration goes down, we queue up all pending messages and send them on their way once the integration is restored.
No! mParticle is a data and integration layer that makes it easier for you to use the great services without further code changes. You still have to establish a direct relationship with each of the integrations you want to use.
Contact our customer support team - we love questions and feedback!
mParticle allows you to specify a minimum version of your app for data forwarding to mParticle. The main reason to specify a minimum version is if you have already been sending data to a service outside of mParticle. Specifying a minimum version can ensure that you do not send duplicate data once you start forwarding from mParticle. Users that have an older version of your app will be still sending data via the partner’s own SDK, and when you enable data forwarding from mParticle you will want to ensure that the same data is not sent twice - by the partner’s SDK and then by mParticle.
For example, let’s say your current version - which includes a partner’s SDK - is version 1.0. You next version, which incorporates the mParticle SDK and removes the service SDK, is version 2.0. In your mParticle connection settings, you will want to specify 2.0 in the Version settings. This will ensure that older app versions that still have the service’s SDK still send data directly to the service and that newer versions with the mParticle SDK included and the services SDK removed will forward data via mParticle.
App versions with non-numeric characters or parenthesis (e.g., 1.0ab or 1.0 (1234)) may cause filtering to not function as desired.
Security is a priority for mParticle. As part of our security policy, our SDK clients pin SSL certificates and will only communicate directly with the mParticle server. However, we offer several other methods for monitoring traffic in and out of mParticle:
The SDKs automatically capture:
Information about the device being used, including:
Information about the current state of the device at the time of an event:
App lifecycle events:
The SDKs DO NOT automatically capture:
mParticle is not a screen recorder and cannot be used to capture the current state of a user’s screen. The SDKs NEVER capture: