Metrics are user-defined values that refer to a business goal, or to Key Performance Indicators (KPIs) such as revenue, conversion, orders per minute, widgets sold, etc. In mPulse, these values are defined using the Configure App, Metrics tab.
mPulse supports the use of user-defined metrics configured using URL Pattern matching, as well as using a variable.
As of mPulse 57, the behaviour of the percentage data type has improved. Click here for information.
Because browser support varies by brand and/or version, the App Admin should be aware of the following variations.
For latest supported browsers, click here.
Browser Support (Custom Metrics):
To define metrics, use the following techniques by browser.
App Admins setting up metrics should also be aware of how browser variations impact setup.
Browser Support (Timers):
For timers, use the following techniques by browser.
Examples of defining metrics are provided below.
The App Admin user can configure either a variable or a URL Pattern to match metrics in this tab.
URL Patterns are any regular URL with * used as a wildcard anywhere in the URL. For example, entering:
But will not match (because / is required in the pattern):
The Metrics form appears.
For widgets with a custom metric defined, ensure that the correct domain is selected in the Filter tab, and then choose Metric as the attribute, and the metric from the Value dropdown.
For example, use SOASTA.cmet1 or SOASTA.custom_metric1. This variable must be globally readable.
If you also define page groups using a variable, then:
Metric values for mobile apps are also defined using the Configure App, Metrics tab. It requires only a name match in the mPulse Configure Apps UI to go along with your project source code modifications to be operational. Users should note that for the changes can only be applied by re-submitting your app to the App Store. Use the following steps to ensure a match between the named value entered in your app configuration and that used in your source code for the given timer or metric.
Do all of the following to setup your custom metric:
metricName(same as in the API call). Note this metricName for use in your source code.
© 2015 SOASTA. All Rights Reserved. Privacy & Legal