Catalog gives you a single view of every unique event, attribute and identity collected in an mParticle workspace, detailed insights into each of these Data Points, and lets you provide your own annotations.
You can use the Catalog’s List view to:
View a centralized listing of all your Data Points.
Spot Data Points which are duplicated, inconsistently named, etc.
Identify and eliminate unnecessary or redundant Data Points
The list view displays six main categories:
Search and Filter
You can filter the list view to find specific Data Points by:
Search: show Data Points with matching name, description or other name.
Input/App Version: show Data Points that have been seen for the selected inputs/app versions.
Environment: show Data Points that have been seen in the dev or prod environments.
Channel: show Data Points that have been seen for the selected channel. Channel is distinct from input and describes how a Data Point arrived at mParticle. For example, a Data Point may arrive fron the client-side, server-side, or from a partner feed. Valid channels include:
Date Range: show Data Points that have been seen within a selected date range.
You can combine the above filters to quickly browse and explore your Data Points. Setting a filter will also clear any current category selection.
The details view gives you detailed information on an individual Data Point, including environments the event has been captured for, and when an event was last seen for each platform.
Users with admin access can annotate Data Points in the following ways:
Tags: a freeform list of labels you’d like to associate to the Data Point.
External Link: a link to your wiki or any other resource containing documentation about the Data Point
Description: a custom text field where you can describe the Data Point, expected attributes, how it’s used, and any other relevant information.
Additional Names: a list of alternate names the Data Point is known by. For example, legacy names or names from a partner feed.
Data Point Attributes
Your event Data Points may include attributes, and the details view shows every attribute name that has ever been seen within the given Data Point. You can see the total volume received in the last 30 days, when the attribute was last seen, and the detected data type. The supported detection types are:
For Data Points, the stats view shows two important groups of statistics for a selected date:
Input stats show how many instances of the event have been received, by platform and channel.
Output stats show the volume sent to each output, as well as the delta between the number of events received and outgoing messages sent. This delta can be useful for troubleshooting, but note that the difference between volume sent and received usually doesn’t indicate a problem. Expansion of eCommerce events can cause multiple messages to be sent to an output for a single event. Likewise, filtering or an output partners minimum requirements can cause mParticle not to forward every event we receive.