m_​pulse

Version: v2025-01-13Includes use: No

Behavior name: m_pulse

mPulse provides high-level performance analytics and predictive recommendations based on real end user data. See the mPulse Quick Start to set up mPulse on your website.

Default behavior

These samples reflect the behavior's default settings. You can use these as is in your configurations or make adjustments based on the behavior's available options.

data "akamai_property_rules_builder" "m_pulse" {
  rules_v2025_02_18 {
    name     = "m_pulse"
    comments = "Establishes a mTLS connection between the edge server and the origin to authenticate requests."
    behavior {
      m_pulse {
        enabled = true
        require_pci = false
        loader_version = "V12"
        api_key = ""
        buffer_size = ""
        config_override = ""
      }
    }
  }
}
"behaviors": [
  {
    "name": "mPulse",
    "options": {
      "enabled": true,
      "requirePci": false,
      "loaderVersion": "V12",
      "apiKey": "",
      "bufferSize": "",
      "configOverride": ""
    }
  }
]

Options

Option Description
enabled
Applies performance monitoring to this behavior's set of content.
require_pci
Suppresses gathering metrics for potentially sensitive end-user interactions. Enabling this omits data from some older browsers.
loader_version
Specifies the version of the Boomerang JavaScript loader snippet. See mPulse Loader Snippets for more information. Value is one of:
  • V10. Use version 10.
  • V12. Use version 12.
  • LATEST. Automatically update to the latest available production version.
  • BETA. Use the latest version, including beta releases.
api_key
This generated value uniquely identifies sections of your website for you to analyze independently. To access this value, see Enable mPulse in Property Manager.
buffer_size
Allows you to override the browser's default (150) maximum number of reported performance timeline entries.
config_override
A JSON string representing a configuration object passed to the JavaScript library under which mPulse runs. It corresponds at run-time to the window.BOOMR_config object. For example, this turns on monitoring of Single Page App frameworks: "{\"history\": {\"enabled\": true, \"auto\": true}}". For more information, see Configuration Overrides.