AKAMAI REAL TIME WEB MONITOR CODE
The following code delays the firing of the mPulse beacon for 2.5 seconds. If no bot beacons are present in the data, the values of these system dimensions will be null.įor cases when you want to delay the mPulse beacon from firing on the load event. You can add these dimensions to custom dashboards as filters that segment your RUM data based on visitor type and bot category in order to better understand how bots may be impacting your performance data in aggregate.īot Manager indicates whether Bot Manager was enabled for the page visit or notīot Manager Bot Type indicates the bot type as classified by Bot Managerīot Manager Bot Category indicates the bot category as defined by Bot Manager There are three system dimensions associated with this integration. Select the Include Bot Beacons checkbox in the app configuration UI to enable this feature. mPulse uses Botman to determine whether a visitor is a bot or not so you can diagnose performance issues and identify if bots are the root cause. You can control whether or not mPulse collects beacons from bots in order to more precisely focus on performance, user engagement, and business metrics from real end users. The integration with Bot Manager improves bot detection and classification capabilities and allows you to easily compare bot data against real user performance data. Bot Manager integration improves mPulse bot detection and classification capabilities.īots can skew performance data reported within mPulse.
0 kommentar(er)
