The Activity section of the mParticle platform allows you to view information about your event data.
The Activity Overview tracks basic stats for your workspace:
|Active Users||Displays the number of active users.|
|Installs||Displays the number of installation events.|
|Sessions||Displays the number of active sessions.|
|Average Session||Displays the average length of a session.|
|Data In||Displays the number of event messages received.|
|Data Out||Displays the number of event messages sent to output services.|
|Alerts||Displays the number of alerts which occurred when forwarding data to an output service.
Only the Fatal alert type is displayed.
|Revenue||Displays total revenue.
This tab is only shown if there is a non-zero amount of revenue to display.
All tabs can be filtered by date range, environment and input. Some tabs have additional filters.
Summary information is included in each activity tab displaying a total activity count for the selected time period and and indication of any change from the previous time period.
Below the graphical data for all activity tabs, the following technographic information is displayed:
All Operating Systems
The User Activity view allows you to see a detailed summary of data associated with a single user. Note that only users with the Admin role can access the User Activity view.
To find a user, begin entering any known ID for the user, an email address, customer ID, device ID, etc. The ID must match exactly to return a profile. If multiple profiles are returned, select the user you want from the list.
The following user information will be displayed if available:
List of all devices, including the date the device was last seen, device platform (iOS, Android, etc) and whether
Limit Ad Tracking is enabled for the device.
List of all available user attributes. Display priority is given to reserved user attributes:
All other user attributes will be displayed in alphabetical order.
A list of campaigns, showing Partner and Campaign name.
A list of all Audiences the user is a member of.
If you are collecting event data for your users, the Events tab will show a timeline of historical event data from the user, up until the previous day. Events can be filtered by Date, Input, Event Type and Device. In addition to filtering, you can also choose to highlight selected event names in the timeline.
Events are grouped in batches, with the input source in bold. Click a batch heading to view common attributes for the batch, or an event name to view attributes for the event. eCommerce events show details for the transaction and also for each product, including quantity and total price per product.
Click the Link button in the details view to copy a sharable direct link to the event to your clipboard.
As with the Live Stream You can expand any event or batch to view the raw JSON data.
The System Alerts report provides information related to any issues forwarding data from mParticle to your connected services. The following alert categories are supported:
The report displays the number of alerts in each category for a 12-hour time period, and a breakdown for each active Output service. You can expand the data for any output for a breakdown of alerts by type. The following alert types are supported:
|Error Parsing SDK Version||The SDK version in the event batch is invalid.||Kochava|
|Event Arrived Late||A message arrived which is older than can be supported by the integration and will be discarded.||Adjust, Mixpanel|
|Feature Unsupported by SDK Version||The forwarding of events is not supported by the current SDK version - A later version of the mParticle SDK is required.||Kochava|
|Identifier Too Long||The Device ID or Customer ID exceeds the length which the integration supports.||Leanplum|
|Invalid Credentials||A token cannot be obtained due to invalid credentials.||AgilOne, SFDC Email|
|Missing Android ID||Android ID is required, and is missing in the event batch.||Appboy, AgilOne, Fiksu, Leanplum|
|Missing App Info||Application Info is required, and is missing in the event batch.||AgilOne, Appboy, Google Adwords, Google Analytics, Kochava, Krux, Oracle BlueKai, Tune, Webtrends,|
|Missing AppName||Application Name is required, and is missing in the event batch.||Google Analytics, Webtrends|
|Missing Build ID||Google Adwords|
|Missing Device Info||Device Info is required, and is missing in the event batch.||Appboy, Singular, Google Adwords, Kochava, Krux, Leanplum, Oracle BlueKai, SFDC Email, SFDC MobilePush, Webtrends|
|Missing Event Name||Event Name is required, and is missing in the event batch.||Amazon Mobile Analytics, Amplitude, Customer.io|
|Missing Fire Advertising Identifier||Amazon Fire TV Identifier is required and is missing in the event batch.||Krux|
|Missing Google Advertising Identifier||Google Advertising Identifier is required, and is missing in the event batch.||Facebook Atlas, Google Adwords, Krux, Leanplum, Nanigans, Oracle BlueKai, TapCommerce, Tapstream|
|Missing Google Advertising Identifier and Android ID||Google Advertising Identifier or Android ID is required, and neither is present in the event batch.||Adjust, AppLovin, Leanplum, Quantcast|
|Missing Identity||A required identity (i.e. Customer ID, etc.) is required, and is missing in the event batch.||AgilOne|
|Missing Identity and Device ID||An identity and device ID are required, and both are missing in the event batch. For Appboy, a Customer ID and Push Token are required. For Webtrends, a Customer ID and either IDFA or IDFV (iOS) or Google Advertising Identifier or Android ID (Android) are required. For Localytics data to be forwarded server side, the Customer ID or Other User Identity must be set, or the Google Advertiser ID or Android ID (Android) or IDFA (iOS) is required.||Appboy, Amplitude, Localytics, Webtrends|
|Missing IDFA||IDFA is required, and is missing in the event batch. The IDFA can be turned off by the end user by turning on ‘Limit Ad Tracking’ on their iOS device in Privacy Settings.||Applovin, Fiksu, Facebook Atlas, Google Adwords, Leanplum, Nanigans, Oracle BlueKai, Quantcast, TapCommerce, Tapstream|
|Missing IDFA and IDFV||IDFA or IDFV is required, and both are missing in the event batch.||Adjust, Appboy, Krux, Leanplum|
|Missing IDFV||IDFV is required, and is missing in the event batch.||Leanplum|
|Missing IP Address||IP Address is required, and is missing in the event batch.||Singular, Facebook Atlas, Google DoubleClick, Quantcast|
|Missing LocaleCountry||Google Adwords|
|Missing LocaleLanguage||Google Adwords|
|Missing Model||Google Adwords|
|Missing OS Version||OS Version is required and is missing in the event batch||Singular, Google Adwords|
|Missing PackageName||Package Name is required, and the application is not presenting one in the event batch. For Tune, you can override the Package Name in the configuration settings.||Applovin, Singular, Google Adwords, Quantcast, Tune, Urban Airship|
|Missing Required Setting||A required setting is missing.||Appboy, Appsflyer, Fiksu|
|Missing User Agent||User Agent is required, and is missing in the event batch.||Facebook Atlas, Google DoubleClick|
|No Route Available||The source of the event batch is not supported. This is used to indicate that the source of the event batch was not from a native client with the extended SDK (appropriate kit included) or the mParticle Events API.||Appboy, Urban Airship|
|Request Too Long||The requeest exceeds a size or character limit set by the partner and cannot be delivered||Krux|
|Retry Count Exceeded||This indicates that the data has repeatedly been attempted for delivery, but has exceeded the retry limit.||Any|
|306-Unknown||This may occur in cases of network issues which may be retried.||Any|
|400-Bad Request||This indicates an error with the request sent to the integration and will not be retried by default.||Any|
|401-Unauthorized||This may indicate a poor response from the remote server.||Any|
|403-Forbidden||This may indicate the credentials used to authenticate with the remote server are incorrect. Check the configuration settings to ensure a valid value was entered (i.e. API Key, Username, Password, etc.).||Any|
|404-Not Found||This may indicate an issue on the remote server (i.e. if DNS changes are not observed fast enough).||Any|
|408-Request Timeout||This indicates a timeout occurred in sending data to an integration. A timeout will be noted as a Warning and retried. If the retry limit is exceeded, the timeout will be classified as Fatal.||Any|
|409-Conflict||This may indicate an issue with the request to the integration or the remote endpoint. The request will be dropped.||Any|
|413-Request Entity Too Large||This indicates the request was too large for the integration and it will not be retried.||Any|
|414-Request-URI Too Long||This is similar to 413, but for a different portion of the request, and it will not be retried.||Any|
|500-Internal Server Error||This indicates that there is a server error, and will be retried.||Any|
|502-Bad Gateway||This usually indicates a temporary network glitch or configuration issue on the remote endpoint which may resolve itself. This type of alert will be retried||Any|
|503-Service Unavailable||This is similar to 500, indicates a server error, and will be retried.||Any|
|504-Gateway Timeout||Usually a temporary network glitch or configuration issue on the remote endpoint; will usually resolve itself, and will be retried.||Any|
|525-SSL Termination Error||This may indicate an issue with the SSL configuration, but may also be seen during a network outage, and will not be retried.||Any|
The Event Forwarding report provides information on your app’s incoming event data and the data that is forwarded to enabled output event services. This is where you can verify how much data mParticle captured per event, and how much data was forwarded. If multiple configurations are enabled for an integration, the data sent to each configuration will be shown separately. We recommend checking this report if you notice any discrepancies in your vendor dashboards.
The report displays a daily summary of events, plus counts for each message type and event name, along with the inbound and outbound counts for each enabled service. By default a summary of data for a full day is shown, but you can also select a specific hour to display hourly data.
You may notice differences between an inbound data count and an outbound data count. There are several reasons these differences may occur. Here are some good questions to start with:
Was this page helpful?