mPulse supports the use of custom timers configured using either client-side matching defined as part of your App, or by using a variable (written as Boomerang plugin). A Custom Timer can be based on any measurable user-defined value in the page.
Currently, navigation, resource, and user timers can be defined using the client-side pattern matching method. In addition to being client-side deployed (requiring no code on your web site or app), no Boomerang plugin is required for the non-Variable method.
App Administrators define pattern matching custom timers from within the Configure App box, Custom Timers tab, as well as enter Variable values.
For information about setting custom timers and other custom metrics programmatically, refer to the mPulse Beacon API.
Because browser support varies by brand and/or version, the App Admin should be aware of the following variations.
Browser Support (Custom Timer):
For custom timers, use the following techniques by browser.
App Admins setting up custom timers should also be aware of how browser variations impact custom metric setup.
Browser Support (Custom Metrics):
For custom metrics, use the following techniques by browser.
The App Admin user can define multiple timers using this tab and one timer per row. Custom Timer rows collapse/expand for easier use with multiple timer rows, Timers can use either Variable or URL Pattern.
App Administrators can define custom timers using URL Pattern matching from within the Configure App box, Custom Timers tab.
This features works with basic Boomerang and no additional Boomerang plugin is required.
URL Patterns are any regular URL with * used as a wildcard anywhere in the URL.
Resource URL matching can be used while defining a resource timer.
For example, to set the Resource URL for a specific resource:
If the Resource URL value includes a wildcard at the end, such as:
Then, it will return the first resource that is a match:
A user timer can be created to track the user experience on your site.
See Resource Groups
Use the following pattern match examples to aid in defining your URL Pattern.
URL Patterns are any regular URL with * used as a wildcard anywhere in the URL. With the query string type URL pattern, mPulse looks for the first matching query string parameter for the page that has a URL match. For example, entering:
But will not match (because / is required in the pattern):
mPulse supports the use of custom timers written as Boomerang plugins. Your timer can be added to your domain using the Configure App, Custom Timers tab. An example of such a plugin is provided in the sub-section below.
Once written and deployed, the App Admin can use the Configure App dialog box, Custom Timers tab to bind the plugin to an app and create the Value for dashboard users to filter by. You will need the variable name for the given Custom Timer plugin.
A custom timer is deployed in your application or site. Once written, create an mPulse repository object for your custom timer to enable its selection by users in dashboard filters.
The Custom Timer form appears.
You can define a client-side custom timer using a URL Pattern in tandem with any of the following start and end timers
This example plugin measures something either before or after boomerang loads, and will block beacon firing until the timer is ready. Attach events when you write your own plugin, set flags, etc.
© 2015 SOASTA. All Rights Reserved. Privacy & Legal