# How to Add Experimental Properties to a Dynatrace Browser Monitor Script **URL:** \ **Category:** Troubleshooting\ **Tags:** troubleshooting-guide, browser-monitors, synthetic-monitoring\ **Created:** [May 15, 2026, 1:45pm UTC](https://community.dynatrace.com/t/how-to-add-experimental-properties-to-a-dynatrace-browser-monitor-script/55920 "2026-05-15T13:45:03Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![hannahmac](https://avatars.discourse-cdn.com/v4/letter/h/dec6dc/32.png) [@hannahmac](https://community.dynatrace.com/u/hannahmac)\ **Post date:** [May 15, 2026, 1:45pm UTC](https://community.dynatrace.com/t/how-to-add-experimental-properties-to-a-dynatrace-browser-monitor-script/55920/1 "2026-05-15T13:45:03Z")
## **Summary** This article explains **how to add experimental properties to a Dynatrace Browser monitor script**. Experimental properties are typically used during **Dynatrace Support troubleshooting** to enable additional diagnostics, or temporary behavior changes in Synthetic Monitoring Browser clickpaths. With a few exceptions, many of these settings are **not documented publicly** and should only be applied when explicitly requested by Dynatrace Support. ## **When to use experimental properties** You may be asked to configure experimental properties in a Browser monitor script when: - Dynatrace Support is investigating **Synthetic Monitoring failures or inconsistencies** - Additional **diagnostic data or logging** is required - A **change in behavior**  of the Synthetic player is needed for a small use-case > ⚠ Experimental properties are **support‑guided only**. Adding undocumented properties without guidance may lead to unexpected monitor behavior. The only exception to this are those documented in the Troubleshooting forum. ## **How to add experimental properties to a Dynatrace Browser monitor** Follow these steps to safely add experimental properties to a Browser monitor script. ### In Latest Dynatrace Synthetic app #### **1. Open the Browser monitor** 1. In Dynatrace, navigate to **Synthetic**. 2. Select the relevant **Browser monitor**. #### **2. Edit the monitor script** 1. Click **Edit monitor settings**. 2. Open the **Advanced Setup**  tab. #### **3. Add the experimental property** 1. Expand the **Experimental properties**  section 2. Select **Add property** 3. Enter the Name and Value - Replace `propertyName` and `value` with the **exact details provided by Support**. - Do not modify or add additional experimental properties unless instructed. #### **4. Save and deploy** 1. Click **Save**. 2. Execute the Browser monitor to ensure the changes take effect. ### In Classic Synthetic #### **1. Open the Browser monitor** 1. In Dynatrace, navigate to **Synthetic,** or the **Synthetic Classic app**. 2. Select the relevant **Browser monitor**. #### **2. Edit the monitor script** 1. Click **Edit monitor settings**. 2. Open the **script editor** for the Browser clickpath. #### **3. Add the experimental property** 1. Locate the `configuration` section of the monitor’s **JSON configuration**. 2. Add the experimental property using the format provided by Dynatrace Support: - Replace `propertyName` and `value` with the **exact details provided by Support**. - Do not modify or add additional experimental properties unless instructed. #### **4. Save and deploy** 1. Click **Save**. 2. Execute the Browser monitor to ensure the changes take effect. ### **Validation** After applying the experimental property: - ✅ Verify that the Browser monitor executes successfully - ❌ If errors occur or the issue persists, share the **updated script** with Dynatrace Support for further analysis For related Browser clickpath scripting guidance, see: [**How to interact with trusted events in a Browser Clickpath**](https://community.dynatrace.com/topic/222074) ## How to remove/ disable an experimental property When an experimental property is no longer required, remove the property that was added during troubleshooting: - **Latest Dynatrace Synthetic app:** Open **Advanced Setup** → **Experimental properties** and delete the property entry. - **Classic Synthetic:** Remove the corresponding code snippet from the monitor’s `experimentalProperties` section, or the entire `experimentalProperties` block if no other experimental properties are configured. After removing the property, save the monitor and execute it again to validate that it runs successfully. ## **FAQ** ### **Are experimental properties officially documented by Dynatrace?** No. Dynatrace does not publish a public list of experimental properties. With the exception of small number documented in the Troubleshooting forum, they are provided **case‑by‑case by Dynatrace Support**. ### **Can I use experimental properties in production monitors?** For any documented in the Troubleshooting forum, yes, these properties are production-suitable. For others, only if explicitly instructed by Dynatrace Support. ## What’s Next If this does not resolve the issue, please open a support ticket and provide - a link to the affected monitor - mention this article and any other troubleshooting steps taken ### **Related reading** 📖  [Classic Script mode for Browser monitor configuration](https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-monitoring/browser-monitors/script-mode-for-browser-monitor-configuration) 📖  [Latest Dynatrace Advanced Setup for Browser monitors](https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-on-grail/synthetic-app/create-configure-browser-monitors#advanced-setup) 📖  [Synthetic Troubleshooting Map](https://community.dynatrace.com/topic/250426) 📖  [How to interact with trusted events in a Browser Clickpath](https://community.dynatrace.com/topic/222074)