CategoriesAll

Event

SessionM - Stronger customer relationships through smarter engagement.

Prerequisites

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.

Data Processing Notes

  1. Event Attributes - Only 10 event attributes can be sent to SessionM per event. If an event has more than 10 attributes, the additional attributes are dropped.
  2. User Attributes - There is a 200 custom user attribute limit for profiles in SessionM. This includes attributes defined in SessionM and those sent to mParticle. If the limit is reached, not all attributes will be available in SessionM.
  3. Only logged in users should be sent to SessionM using the Id Sync Forwarding Rules

Supported Platforms

  • Alexa
  • Android
  • FireTV
  • iOS
  • Mobile Web
  • Custom Feeds
  • Roku
  • SmartTV
  • tvOS
  • Xbox

User Identities

mParticle will always forward the mParticle Identity (MPID) to SessionM. Additional User Identities can be sent to SessionM by enabling them in filters.

Configuration Settings

Setting Name Data Type Default Value Description
Host Name string Host name for your SessionM account. e.g. https://api.sessionm.com

Connection Settings

Setting Name Data Type Default Value Platform Description
API Key string All Your platform-based SessionM API Key.
API Secret string All Your platform-based SessionM API Secret.
mParticle to SessionM Event Mappings string All Define the mapping of mParticle event names to the corresponding SessionM event name

Was this page helpful?