How mPulse works

mPulse gives you the power to collect and analyze detailed information about your users' experience whenever they visit your site or native application.

When a visitor looks at a page on your site, mPulse captures over 200 business and performance facts about that experience directly from the visitor's browser, and sends the data back to mPulse so you can see how your site is performing for real users, in real time.

With mPulse you can collect performance timers such as bandwidth and page load times as well as business metrics like bounce rate, conversion rates, or order totals.

As soon as your first mPulse beacon arrives, system dashboards are instantly populated, giving you real-time views of real user activity at a glance. Widgets in the mPulse dashboards show a breakdown of the data by segments such as page groups, browser type, bandwidth distribution, and geography. You can create custom dashboards that let you slice and dice your data in a variety of ways.

How mPulse collects data

mPulse uses a bit of JavaScript code that ‚ÄčAkamai‚Äč calls the mPulse snippet. It includes the boomerang JavaScript (boomerang.js) library to collect web performance data from a user's web browser. That data is sent back to ‚ÄčAkamai‚Äč on the mPulse beacon.

What an mPulse beacon is

The mPulse beacon is an object that contains all of the business and performance information about a visitor's experience while they're looking at your website.

The beacon collects the following data and sends it back to mPulse for analysis in the mPulse dashboards. See this list of available parameters for complete details on what the mPulse beacon collects for web apps.

  • Top-level (for example, domain, timestamp, and IP address)

  • Session (for example, session ID, and session start time)

  • User agent (for example, browser family, major version, and device type)

  • Geographical (for example, country, and region)

  • Bandwidth (for example, in kbps and bandwidth block)

  • Timers (for example, response time and DOM loaded)

  • Custom metrics (for example, conversion and revenue)

  • Custom dimensions (for example, store number, logged in status, or origin server)

  • Third-party analytics (for example, Google, Adobe, and IBM Digital Analytics)

  • Resource timing data (for example, startTime, dns_start, and dns_end)

How the mPulse snippet works

The mPulse snippet creates an empty inline frame (IFrame) that's typically used to embed an HTML page within the current HTML page. In mPulse, the IFrame is used to wrap the snippet's components (for example, boomerang.js, an API key, and a domain name) and your web page's performance results together to generate and deliver the mPulse beacon to a collector such as a server on the ‚ÄčAkamai‚Äč edge, where your performance data is processed, stored, and displayed in the mPulse dashboards.

How mPulse works if ‚ÄčAkamai‚Äč delivers your web traffic

When the mPulse behavior is included in a rule in a new Property Manager property, it's automatically enabled. The mPulse API key field is also blank. This uses the default setting which creates a new mPulse app that corresponds to the new property.

After the mPulse-enabled property is active on the ‚ÄčAkamai‚Äč production network, beacons of your data are directed to that mPulse app. Your mPulse app appears in mPulse on your Home page under the Apps menu, and will have the same name as the mPulse-enabled property in Property Manager.

If you have an existing mPulse app that you'd like to use for your web traffic, enter the app's API key into the mPulse behavior, then activate the property configuration on the ‚ÄčAkamai‚Äč production network.

Once your first mPulse-enabled property is active on the ‚ÄčAkamai‚Äč network, it takes about 15 minutes to deploy the configuration to the edge servers and to generate data. This depends on the amount of traffic being sent and the time to populate the data in the portal. If you experience delays greater than 4 hours, open a case to contact ‚ÄčAkamai‚Äč Support.

Whenever a visitor requests a page from your site, the edge server injects the mPulse snippet on the page and sends the page to your visitor's device to collect performance data. The visitor's browser sends the data back (in a beacon) to the edge server where ‚ÄčAkamai‚Äč processes and stores the data for performance analysis in the mPulse dashboards. (See Explore mPulse system dashboards and widgets).

mPulse flow diagram

If you're not an ‚ÄčAkamai‚Äč CDN customer

Even if ‚ÄčAkamai‚Äč isn't delivering your web traffic, you can still use mPulse to collect and analyze performance data. The workflow is pretty much the same, but with a few minor exceptions. To start, you'll need to create an mPulse app, then either manually place the mPulse snippet on your site's pages at the origin server or use a tag manager for that task. Instead of the ‚ÄčAkamai‚Äč Platform processing and storing your data, you can choose an mPulse collector of your liking for those tasks. For details, see Set up mPulse at the origin.

Tell me more

For general information and frequently asked questions about mPulse, visit Community.