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.
|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?