> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/browser-synthetics/information-transmitted-in-page-load-or-transaction-test.md).

# What Information Is Transmitted in a Page Load or Transaction Test?

{% hint style="warning" %}
Due to recent platform-wide naming, navigation, and URL changes in the product, you may notice some discrepancies between the product and the screenshots displayed in our technical documentation. The instructions and actual pages in the product are still valid and haven’t changed. Please bear with us as we update our screenshots to better match the in-product experience. See the full scope of changes on [Naming and Navigation Menu changes - Summary List](https://docs.thousandeyes.com/whats-new/naming-and-nav-phase-2-changes).
{% endhint %}

ThousandEyes Cloud Agents and Enterprise Agents transmit the following information when executing page load or transaction tests:

* HTTP request and response headers only. Response bodies are not sent.
* `Authorization` and `Proxy-Authorization` headers are masked. Cookies are also masked.
* Waterfall data, including
  * Request and response headers for each waterfall object or component
  * Provider information is not sent by the ThousandEyes agent, but is instead deduced by the back-end
  * IP addresses
* Screenshots are transmitted if a marker is present in the transaction test script or if a test error occurs. For screenshot settings, see [Page Load Test Page Load Performance and Browser Settings](https://docs.thousandeyes.com/product-documentation/tests/web-layer-tests#page-load-test-page-load-performance-and-browser-settings) and [Transaction Test Transaction Performance and Browser Settings](https://docs.thousandeyes.com/product-documentation/tests/web-layer-tests#transaction-test-transaction-performance-and-browser-settings).
* Console logs are transmitted for transaction tests when **Collect console logs** is enabled. Console logs can include browser runtime errors, application messages, script-authored console output, and final script error or timeout output for the selected run. Known sensitive values might be redacted as `[REDACTED]`, but redaction is not a substitute for safe logging. Console-log data is truncated to 1 MB per test run. Do not log credentials, tokens, session identifiers, customer PII, or other sensitive values. For details, see [Using the Transaction Test View](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/viewing-data/using-the-transaction-test-view#console-logs-tab).

You can review collected waterfall data by visiting the **Waterfall** tab under **Network & App Synthetics > Views**, as described in [Navigating Waterfall Charts for Page Load and Transaction Tests](https://docs.thousandeyes.com/product-documentation/browser-synthetics/navigating-waterfall-charts-for-page-load-and-transaction-tests). For transaction tests with **Collect console logs** enabled, you can review console output in the **Console Logs** tab for the selected run, agent, and round. Data that’s not directly used or displayed on the ThousandEyes platform is not collected.

Selecting each component in the **Waterfall** tab shows:

* Element/component-specific URL
* HTTP method
* Target IP
* Response code
* Content type
* Protocol

## Additional Notes

* Questions about user privacy and who can see personally identifiable information (PII) are different from where the data itself resides, and what is retained on the back-end. For example, a transaction test for a healthcare organization might access a patient name list and take a screenshot as part of a longer user journey. The screenshot action can be disabled for that test without impacting any other tests.
* Note that although the ThousandEyes agent receives body payloads as part of executing the test, it doesn’t preserve them. For example, when loading a page with an image, it has to download the image in order to time how long that download takes. However, the image file itself is stored in a temporary container that is destroyed when the test run completes.
* User credentials are not stored in the transaction test script itself, nor are they exposed in any test views or test settings available to ThousandEyes users. Instead they are stored and masked in a **Credentials Repository** as described in [Working With Secure Credentials](https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/getting-started/working-with-secure-credentials).
* For general information on data availability and retention policies, see [How Long Is My Data Accessible via ThousandEyes?](https://docs.thousandeyes.com/product-documentation/user-management/user-activity/how-long-is-data-accessible).