As part of configuration, you will select which event types (Exposures, Configuration Changes, and/or Custom Events) to send to mParticle.
By default, Statsig User IDs will be sent to mParticle as Customer ID. If you would like to map Statsig’s User IDs to another mParticle identity type, contact your Statsig account manager.
Statsig will set the mParticle environment based on the value of the Statsig environment.
Statsig Environment
mParticle Environment
prod
production
All other Statsig environments
development
Supported Event Types
Statsig will send all logged events to mParticle as Custom Events with:
Custom Event Type - other
Custom Event Name - Statsig event_name
Custom Event Attributes - All Statsig event metadata will be sent to mParticle as custom event attributes.
Supported User Information
User Identities
By default, Statsig User IDs will be sent to mParticle as Customer ID. If you would like to map Statsig’s User IDs to another mParticle identity type, contact your Statsig account manager.
User Data
Statsig will send User Data to mParticle. The table below shows how predefined fields will be mapped. All custom user attributes will be prefixed with “statsig_” (e.g. “statsig_my_custom_user_attribute”).
Be mindful of how you store sensitive attributes in Statsig. Use Private Attributes to prevent certain attributes from being sent to mParticle.