Page tree
Skip to end of metadata
Go to start of metadata

A page-render beacon (or a web beacon) is a file in your web application that calculates the page-render time metric for content served by a CDN.

Web beacons do not affect the functioning of your web application and are not visible to end users (usually, the beacon is an image sized to 1x1 pixel). They execute special JavaScript code whenever a page has finished loading.

Before you begin

Ensure that the web beacon file name meets the following requirements:

  • It must contain 1 to 256 characters.
  • It must not contain the following characters: \ / : " < >.
  • It must not consist of a wildcard mask only (for example, *, *.*, or ?).
  • The file extension must be .!cm to ensure that it is cached.

Recommendation

BMC recommends that you do not rename page-render beacons because external content providers can cache the request and response.

To perform this procedure, you must have Operator-level access, or higher.

To deploy a web beacon

  1. Put the web beacon target file on your web server.
  2. Locate the web beacons in the directory that is specified by the PL_GO_IMG variable in the instrumentation code.
    The default name for the web beacon used to measure page-render time is crd_prm_go. For more information, see Web beacon JavaScript library.
  3. Make the system detect the web beacons.
  4. Turn the web beacons on.
  5. In the Real User Analyzer, point to Administration > Data flow settings, and click Web beacons.

  6. In Instrumentation beacons, click ON.

Where to go from here

Configure the system to detect the web beacons and use the code snippet from the Web beacon JavaScript library.