Overview

Skill Level: Any

Prerequisites

Limitations

  • DOM Capture operates on a page level.
  • Privacy Rules that specify regular expressions as identifiers are currently not supported for this release.  
  • DOM Capture can be replayed only in BBR.

Step-by-step

  1. Use the Configuration wizard.

    DOM Capture is part of the Replay module. To enable DOM Capture, you must enable the Replay module.

    1. Enable DOM Capture.
    2. Enable DOM diff (default) or disable DOM diff.
      Note: DOM Diff functionality is not supported for replaying Hybrid Mobile apps.
    3. Configure maximum threshold size for the DOM Capture message.
    4. Configure user interaction triggers for DOM Capture (for example, screenview load or user clicks), including waiting for same-origin frames and iframes to load before capturing a screenview.
    5. Optional. Configure custom events to trigger DOM Capture.
    6. Optional. Specify whether same-origin frames and iframes are captured. The default setting is to capture same-origin frames and iframes.
    7. Optional. Specify whether scripts are removed. The default setting is to remove the scripts.
  2. Use the Configuration wizard to be sure the DOM Capture includes the same-origin frames and iframes.

    DOM Capture on page load occurs as soon as the page itself has completed loading. If the page has same-origin frames or iframes, the browser does not wait for them to load before the DOM Capture occurs. If you configure DOM Capture snapshot to trigger on the page load trigger (i.e. screenview name “root”) then there is a chance that the frame content may not be captured.

    1. Configure a custom event in the Replay Module. Name the event “loadWithFrames”. Configuring the “loadWithFrames” event will cause the UIC to record a screenview load message with screenview name: “rootWithFrames” when the same-origin frames and iframes on the page have finished loading.
    2. In the DOM Capture configuration, use the screenview “load” event with screenview name “rootWithFrames” as a trigger for DOM Capture.
  3. Configure these DOM Capture settings with the Configuration wizard.

    1. Threshold for snapshots – The maximum size a snapshot can be and still be sent. Any snapshots over this threshold are not sent. The threshold is the character length of the serialized HTML.
    2. DOM Capture event triggers – events that trigger a DOM Capture. Default event triggers include:
      • Click – any click event triggers a DOM Capture
      • Change – any change to a specific screenview triggers a DOM Capture
      • Load – any load of a specific screenview event triggers a DOM Capture
      • Unload – any unload of a specific screenview event triggers a DOM Capture

      Load and unload triggers support regex matching of screenview names.

    3. Custom DOM Capture triggers – Create a custom trigger, for example trigger a DOM Capture at Login. If you want DOM Capture to wait until all of the same-origin frames on a page are loaded you configure a “load” trigger for the “rootWithFrames” screenview in the DOM configuration. You must also configure the custom event “loadWithFrames” in the Replay module.
    4. (Optional) Specify if a full DOM snapshot should be captured for a specific trigger, including when DOM Diff is enabled.
    5. Capture frames – Whether you want to capture child Frames and iFrames. If the child frame and iframes do not contain business critical data, you do not need to capture them. Not capturing frames saves on the amount of data that is captured and sent over the network.
    6. Remove scripts – Whether script tags are removed from the captured snapshot. Scripts should be normally removed as they are not required for replay and add to the overhead of transmission and storage.

Join The Discussion

Your email address will not be published. Required fields are marked *