With mPulse enabled, you can collect and analyze detailed information about your users' experience whenever they visit your site or native application.

How it works

When you create a new property in Property Manager, the mPulse behavior is automatically turned on in the property configuration by default with a blank mPulse app API key. Leaving the mPulse API key blank creates a new mPulse app that corresponds to the property.


Match conditions are not applied when the API Key is blank. If you want to apply a match condition to a mPulse behavior, enter an API key for a preexisting mPulse app into the API Key field. To locate the API Key of an existing mPulse app, log in to mPulse, select the mPulse app from the home page, then click the General tab to view the API Key.

mPulse apps are created as โ€œLiteโ€ apps by default. You can change this when you configure your app within the mPulse app configuration panel. For details, refer to Lite apps for enterprise tenants.

After the property is active on the โ€‹Akamaiโ€‹ production network, your mPulse app collects data in the form of beacons, so you can analyze different parts of your website independently.

See the mPulse documentation for complete usage instructions.


The deprecated RUM behavior and the mPulse behavior should not coexist on the same property. If you choose to use RUM and mPulse, you need to explicitly provide an API key for the mPulse behavior.

mPulse and PCI compliance

Your mPulse data can be set up for payment card industry (PCI) compliance and optional configuration selections to fine tune your traffic. For details, see mPulse advanced options.