Monitor synthetic and bot beacons

Compare beacons like WebPagetest to confirm your synthetic results and end false positives. Keep an eye on web crawler beacons like Googlebot and others.

mPulse captures as much real visitor data as possible, including synthetic monitoring services. Synthetic monitoring services are not real end users. They do not run the same transactions or access the same page on a scheduled basis. As a result, this could skew both traffic and performance statistics. To help you track synthetic and bot beacons, mPulse matches the user-agent string to detect most of them. If mPulse spots a request from a suspicious source such as Gomez or Facebook, it returns an HTTP 204 No Content response.

How to

  1. In mPulse, click Central.
  2. In the left pane, click Apps, then double-click the app that you want to use for your SPA.
  3. Click Beacons.
  4. To collect synthetic beacon data, select the Include Synthetic Monitoring Beacons checkbox.
  5. To collect bot beacons, select the Include Bot Beacons checkbox.
  6. Click OK to save the configuration.

Next steps

Use the Browser Families filter on the mPulse dashboards to select synthetic and bot beacons.