PocketPlatform Analytics

Last Updated: Aug 19, 2020 @ 8:39 am

The Analytics features of PocketPlatform allow you to quickly see how users are engaging with your app, right in MinistryPlatform! The full capabilities of MP are available to you as well, from charting to reports, so you can see user engagement, on your terms, without logging into other systems or relying on third-party toolsets.

How Analytics works:

The PocketPlatform Analytics track screen views and other selected actions (such as event registrations) so when your users interact with your app, you’ll be able to identify where your users spend most of their time.

Reviewing analytics data in MinistryPlatform

Each analytics record in MinistryPlatform is broken up into two main sections, each of which has several columns of information

Core Analytics Information:

  1. Analytics GUID: A unique identifier that ensures that this analytics event is unique.
  2. Device ID: The device identifier for the user’s phone or tablet.
  3. User: The UserID for the event. This value may be empty if no one was logged into the app at the time of the event
  4. Event Type: A text field that indicates what the user did in the app; e.g. “Screen Load” and “Event Registration”
  5. Previous Screen: A text field that indicates what screen the user came from to get to the current screen; not always tracked
  6. Screen Name: A text field that indicates what the user did in the app; e.g. “Screen Load” and “Event Registration”
  7. Analytics Data: Raw analytics information for the event; primarily used for reference and troubleshooting
  8. Timestamp: Date and time of the event
  9. Platform: The device type the user was on at the time of the event, iOS or Android
  10. Screen Size: The physical dimensions of the device
  11. OS Version: The operating system version
  12. Language: UN standard two letter code indicating the user’s language.

Related Records:
When available or necessary, we also keep track of specific items in MinistryPlatform that have been loaded.


1
2
3
4
5
6
7
8
9
10
11
12
13
1

A unique identifier that ensures that this analytics event is unique.

2

The device identifier for the user’s phone or tablet.

3

The UserID for the event. This value may be empty if no one was logged into the app at the time of the event

4

A text field that indicates what the user did in the app; e.g. “Screen Load” and “Event Registration”

5

A text field that indicates what screen the user came from to get to the current screen; not always tracked

6

A text field that indicates what the user did in the app

7

Raw analytics information for the event; primarily used for reference and troubleshooting

8

Date and time of the event

9

The device type the user was on at the time of the event, iOS or Android

10

The physical dimensions of the device

11

The operating system version

12

UN standard two letter code indicating the user’s language.

13

When available or necessary, specific records in MinistryPlatform that were loaded in the App are recorded here


Help!  I can’t delete this (event, opportunity, something else)!

PocketPlatform Analytics uses Foreign Keys in SQL to help make sense of the data that it collects and presents to you.  Depending on your security roles in MinistryPlatform, you may only have “read” rights (or none at all) to records in PocketPlatform Analytics, which could throw an error indicating that records can not be moved when you try to delete an item in MP that has been viewed or interacted with by your app’s users.

A great example of this would look something like:

Your church has decided to cancel an event that you’ve already publicized and put on the dashboard of your app. Many users have viewed that event, adding new records to the Analytics Table. You go to the event to delete it in MP and are informed that you cannot.

To rectify this solution, add a Role to the user that needs Analytics deletion rights that grants enough access to delete records.  Please note that deleting analytics records deletes all reference to that analytics event and this data cannot be recovered. We also do not recommend moving analytics records to another event, opportunity, etc, as this would make your analytics data very inaccurate.