SessionM - Stronger customer relationships through smarter engagement.
mParticle forwards custom events, screen views, user attributes and user identities to SessionM. Events must first be defined in SessionM. For this reason, unlike most integrations, the Send new data points by default setting is set to Off. You must manually enable all data points that you wish to forward, and ensure that the necessary events are defined in SessionM. You can use the Data Filter interface to enable the events, event attributes, user identities and user attributes you want to send to SessionM.
mParticle will always forward the mParticle Identity (MPID) to SessionM. Additional User Identities can be sent to SessionM by enabling them in filters.
mParticle forwards user attributes to SessionM as profile attributes. mParticle will send at most 200 user attributes and will normalize user attribute keys as described below. Note that all attribute values will be forwarded as strings.
When mParticle forwards user attributes to SessionM, the following normalization steps will be performed:
Some mParticle user attributes are mapped to SessionM reserved fields. These are mapped according to the table below.
|mParticle User Attribute||SessionM Field|
|Setting Name||Data Type||Default Value||Description|
||Host name for your SessionM account. e.g. https://api.sessionm.com|
|Setting Name||Data Type||Default Value||Platform||Description|
||All||Your platform-based SessionM API Key.|
||All||Your platform-based SessionM API Secret.|
|mParticle to SessionM Event Mappings||
||All||Define the mapping of mParticle event names to the corresponding SessionM event name|
Was this page helpful?