"}]},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://www.pluginview.com/"},{"@type":"ListItem","position":2,"name":"Integrations","item":"https://www.pluginview.com/integrations"},{"@type":"ListItem","position":3,"name":"RUM","item":"https://www.pluginview.com/categories/rum"},{"@type":"ListItem","position":4,"name":"Akamai mPulse","item":"https://www.pluginview.com/integrations/akamai-mpulse"}]},{"@type":"FAQPage","@id":"https://www.pluginview.com/integrations/akamai-mpulse#faq","mainEntity":[{"@type":"Question","name":"Can PluginView detect Akamai mPulse without logging in?","acceptedAnswer":{"@type":"Answer","text":"Yes. PluginView only reads publicly accessible responses when checking for Akamai mPulse — typically cookies, javascript globals, dom selectors, html markup. It does not bypass authentication or paywalls."}},{"@type":"Question","name":"What category is Akamai mPulse?","acceptedAnswer":{"@type":"Answer","text":"Akamai mPulse is classified under RUM, Analytics, Product Intelligence & Monitoring in the PluginView directory."}},{"@type":"Question","name":"How many fingerprint rules cover Akamai mPulse?","acceptedAnswer":{"@type":"Answer","text":"This reference currently tracks 4 fingerprint rules across cookies, javascript globals, dom selectors, html markup. Individual rule bodies are proprietary and are not published."}},{"@type":"Question","name":"What public signals suggest a site uses Akamai mPulse?","acceptedAnswer":{"@type":"Answer","text":"Illustrative public indicators for Akamai mPulse include akaas_AB-Testing; BOOMR_API_key; script#boomr-if-as, script#boomr-scr-as, link. A live scan may match additional proprietary rules beyond these examples."}},{"@type":"Question","name":"Which pages are best for detecting Akamai mPulse?","acceptedAnswer":{"@type":"Answer","text":"For Akamai mPulse, start with: All pages; observe performance beacon."}}]},{"@type":"HowTo","name":"How to check a site for Akamai mPulse","description":"Scan a public URL with PluginView to detect Akamai mPulse from publicly accessible website signals.","totalTime":"PT1M","step":[{"@type":"HowToStep","position":1,"name":"Enter the URL","text":"Enter a public website URL in PluginView — homepage, pricing, checkout, or login pages usually expose the strongest Akamai mPulse signals."},{"@type":"HowToStep","position":2,"name":"Evaluate public signals","text":"PluginView evaluates public signals such as cookies, javascript globals, dom selectors, html markup against the Akamai mPulse signature set (4 rules)."},{"@type":"HowToStep","position":3,"name":"Review the result","text":"Review the confidence score and text explanation for Akamai mPulse on the results page."}]}]}
Detect Akamai mPulse
Akamai mPulse is a real user monitoring (RUM) solution that enables companies to monitor, find, and fix website and application performance issues.
Detection looks at cookies, javascript globals, dom selectors, html markup across 4 fingerprint rules among the site's public responses.
01
Websites using Akamai mPulse
Loading website list…
02
Signal classes
PluginView evaluates public page signals in these classes when identifying Akamai mPulse. Individual fingerprint rule bodies are proprietary and are not published.
- Cookies
- JavaScript globals
- DOM selectors
- HTML markup
03
Example public indicators for Akamai mPulse
Illustrative indicators derived from public catalog metadata for Akamai mPulse. A live scan may match additional proprietary rules beyond these examples.
- akaas_AB-Testing
- BOOMR_API_key
- script#boomr-if-as, script#boomr-scr-as, link
- <script>*?go-mpulse.net/boomerang*?</script>
04
What a detection means
- Establishes
- The listed vendor-controlled browser component was present and active on the scanned page at scan time.
- Does not establish
- It does not prove a sitewide installation, current commercial contract, backend-only use, exclusive use, or production transaction volume.
05
Minimum proof rule
Observe a live browser request, loaded script, or iframe to the listed unique vendor endpoint. Source-text-only matches do not qualify.
Best pages to check: All pages; observe performance beacon
06
How to check a site for Akamai mPulse
- 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Akamai mPulse signals (prefer: All pages; observe performance beacon).
- 2. PluginView reads only public responses (cookies, javascript globals, dom selectors) and scores them against the Akamai mPulse signature set (4 rules).
- 3. Review the confidence score and text explanation for Akamai mPulse on the results page.
07
Commonly implies
A confirmed Akamai mPulse match also implies these technologies are present.
08
FAQ: detecting Akamai mPulse
- Can PluginView detect Akamai mPulse without logging in?
- Yes. PluginView only reads publicly accessible responses when checking for Akamai mPulse — typically cookies, javascript globals, dom selectors, html markup. It does not bypass authentication or paywalls.
- What category is Akamai mPulse?
- Akamai mPulse is classified under RUM, Analytics, Product Intelligence & Monitoring in the PluginView directory.
- How many fingerprint rules cover Akamai mPulse?
- This reference currently tracks 4 fingerprint rules across cookies, javascript globals, dom selectors, html markup. Individual rule bodies are proprietary and are not published.
- What public signals suggest a site uses Akamai mPulse?
- Illustrative public indicators for Akamai mPulse include akaas_AB-Testing; BOOMR_API_key; script#boomr-if-as, script#boomr-scr-as, link. A live scan may match additional proprietary rules beyond these examples.
- Which pages are best for detecting Akamai mPulse?
- For Akamai mPulse, start with: All pages; observe performance beacon.
