![]() ![]() Page Group for the page (Page Groups are defined in the mPulse App Config dialog) Type of beacon: page view, XHR, SPA hard or soft navigation, etc Page view xhr unload spa spa_hard interaction client_batch api_custom_metric api_custom_timer api_network_request IP address of the CDN provider that handled the edge connection for this beacon (for internal use only) (not truncated) Set to true if the beacon was sent using IPv6 (for internal use only) This may be blank depending on browser privacy settings. HTTP Version used to send the beacon (for internal use only) ![]() HTTP Request method used to send the beacon (for internal use only) IP address of the end user (or the proxy they are connected through) (truncated) Server timestamp when beacon arrived ( Unix epoch) Registered domain or registered dev domain in mPulse of the page sending the beacon aaaa:bbbb:cccc:dddd:eeee:ffff:gggg:hhhh to aaaa:bbbb:cccc:dddd::). In this document, we will describe the various parameters collected via the boomerang beacon as well as how they are mapped to other parts of mPulse such as S3, Asgard and DSWB.Īs of April 2020, all IP addresses are truncated. Within the web performance community, this data is commonly called RUM or Real User Measurement data because it involves measuring the experience of real users. All of this data is included on the beacon via HTTP headers or as part of the query string or form payload. MPulse is built on top of the boomerang JavaScript library which collects web performance data from a user’s web browser and sends the data back to the mPulse servers via a beacon.īeacons are invisible network requests that contain performance data and other page-load characteristics. Documentation for mobile apps is available here. The content of this page applies to mPulse web apps. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |