If you are having trouble with mParticle, use the following information to diagnose and correct the issue.
Any known issues affecting mParticle are tracked on our status page (mParticle login required). If you are encountering problems in mParticle, first check this page to see if any service interruptions have been reported. You can also subscribe to receive service updates by email, SMS or RSS feed.
The status page displays information about any ongoing incidents above the first table, after the “About This Site” section.
A table displays past and current availability for the following mParticle components:
APIs: mParticle’s ability to receive data at HTTP endpoints:
You can also view uptimes for the last ten years (mParticle login required).
The status page’s second setion displays average latency for mParticle’s key API endpoints, updated every five minutes. On this page, Latency means the average time, in milliseconds, between mParticle receiving a request at an API endpoint and sending a response. You can view the metrics by day, week, or month.
The status page’s third section displays any known incidents that caused recent service disruptions. You can also view reported incidents for the last ten years (mParticle login required).
Many configuration settings or other circumstances may cause event data to not be forwarded:
Use the following techniques to find the cause of the data discrepency.
If the answer is yes, then continue diagnosing the problem. If not, review the knowledge base or log a ticket with mParticle Support.
Some integrations require that data points be mapped in order to be sent to a downstream service. No mapping results in no data forwarding. The following integrations have this requirement—for other integrations, check the documentation for that integration:
Check system alerts and look for issues.
For kit-based integrations, you may not have included the kit:
Some services require the presence of a kit, even to send data that is sent to mParticle server-side. For example, AppsFlyer, Adjust, Adobe MCID, and Airship all require a kit. Check the documentation for the integration to verify whether a kit is needed.
These integrations use the kit to obtain an identifier (an integration attribute). For data that is sent to mParticle server-side, the user needs to have been in an app version that contains the kit in order to send the data. This means that for server-side data, not having seen the user in a version of the app with the kit would trigger errors in system alerts and cause data not to be sent. Data not being forwarded is expected in this case.
If you still can’t identify the issue, review the knowledge base or log a ticket with mParticle Support.
For additional SDK troubleshooting:
Was this page helpful?