mPulse provides built-in, system dimensions that are automatically
captured and stored in the mPulse beacon.
mPulse system dimensions are available in the filter bar at the top of the
dashboards. Dimensions are categorized in a variety of ways such OS families as shown in
this example.
System dimensions
This table lists the mPulse system dimensions that are common to most
dashboards.
Name
Description
A/B Test
If A/B testing is used, this variable specifies the test bucket the
visitor was in when they sent the beacon.
Action
Indicates the name of the action, as defined by the mobile app owner
using the SDK.
Akamai Adaptive Acceleration
Denotes whether Adaptive Acceleration was applied to the requested
page. Adaptive Acceleration uses real user monitoring (RUM) navigation and timing data
to intelligently cache content that viewers will likely need ahead of when it’s
actually needed. This approach shortens delivery times, reduces the load on the
network, and renders web pages faster. Requires Akamai
CDN.
Akamai FEO
Denotes whether FEO was applied to the requested page. FEO reduces
the number of HTTP requests, compression, and optimizing browser rendering, all of
which can help you improve performance, especially on smartphones and tablets.
Requires Akamai CDN.
Alert
The name of the alert that was triggered.
Alert Severity
The severity of the alert that was triggered.
App Error Code
The error response status code.
App Error Message
The error response message.
App Error Source
The component that generated the error. For example, Global,
Handler, Network or Manual.
App Error Type
The error type that is parsed from the error message. For example
ReferenceError or SyntaxError.
Bandwidth Block
The bandwidth of the requesting browser's connection.
Beacon Type
Beacon types include; page view, SPA hard or soft navigation, XHR,
and error.
Boomerang Version
The version number of the Boomerang that fired the beacon.
Browser
The browser name and browser version that are requesting the
object.
Browser Family
The name of the browser requesting the object.
Connection Type
The mobile connection type.
Country
The country from which the request originated.
Device
The full device name and model. For example, Samsung Galaxy
S8.
Device Manufacturer
The mobile device manufacturer. For example, Apple, Samsung and
LG.
Device Type
The form factor of the device on which the requesting browser is
running. For example, mobile desktop, tablet, and console.
Full URL
The entire raw URL of the page that sent the beacon.
HTTP Protocol
The HTTP protocol used to deliver the page
(1.1/2/2+QUIC/.../etc).
IP Address
Identifies the IP address of the visitor or the proxy they’re
connected through.
IP Version
The IP version used to deliver the page. Requires Akamai
CDN.
ISP
If the page was requested over a mobile data connection, this is the
mobile service provider.
Network Errors
4xx client errors. Note: This dimension is present only when XHR
instrumentation is enabled (see Set up page groups).
OS
The OS and OS version of the platform on which the requesting
browser is running.
OS Family
The platform on which the requesting browser is running.
Page Groups
The groups that are either auto-defined by mPulse or user defined in
the web app configuration, on the URLs tab.
Region
The area of a country from which the request was sent.
Site Version
For mobile applications, this is the version of the application
installed on the visitor’s device. For web applications, site owners may use this to
specify a release number for their site.
TLS version
The version of the transport layer security (TLS) protocol that the
visitor uses to connect to the Akamai network
(edge).
URL
For web apps, this is often the domain of the page that sent the
beacon. For mobile apps, if URL patterns are configured, it is the URL pattern of the
network request that sent the beacon.
Landing Page
Whether or not this was the first page of the session. The first page
is likely to be one of the slowest pages views because it may not have cached data and
may require a full DNS/TCP/TLS connection. This data gives you insight into where the
optimize for first-time visitors and landing pages.
Early Beacon
Whether or not this beacon's data was from an Early Beacon (and the
full beacon data did not arrive). Early Beacons allow you to capture as much data as
is available when mPulse first loads on the page, which is superseded by the full
beacon page load. This dimension allows you to filter to just the Early Beacons that
never reached a full beacon.
Visibility State
The visibility state of the page: Always Visible, Partially Hidden, or Always
Hidden.
If the page was loaded in the background tab, you might want to exclude the
performance metrics from the page view, because browsers can throttle non-visible
tabs, which has potential to skew results.
Navigation Type
The type of the navigation: Navigate, Reload, or Back-Forward.
Indicates if the user navigated to the page, refreshed the page, or navigated back
through their history to find the page. Excluding refreshed pages and back/forward
navigations could give a more realistic performance distribution for your
pages.
Akamai Property Version
Available when using mPulse Edge Injection. This allows you to
compare performance and roll out speed between versions of your CDN configuration,
automatically collected from Akamai with every page view. This only works if mPulse is
enabled via your property configuration.