Synthetic Classic has reached end of support and is no longer available. Existing Synthetic Classic customers have been upgraded to the all-in-one Dynatrace software intelligence platform.

Recording a transaction

Use the Web Recorder to create tests for all test types and agents.

  • To use the Web Recorder, you must open the Synthetic Classic Portal in the Chrome browser.

    The first time you use the Web Recorder, you are prompted to add the required Chrome extension when you open the Web Recorder. Click Add Dynatrace Web Recorder to Chrome. When prompted to Add Dynatrace Recorder, click Add extension.

  • To create a test that doesn't begin by navigating to a web page, see Creating an advanced script.

Select Menu icon > Tests, then click Create test at the top of the Tests page.

Synthetic Classic Tests page

Continue with the procedure for the selected test type(s):

Browser tests

  1. Select the desired combination of Backbone and Private Last Mile tests and agents.

    Synthetic Classic test combinations

  2. Click Continue to proceed to the Specify Scripts or URLs page.

  3. Select Record a Transaction, then click Open Web Recorder.

  4. Continue with Record the Transaction, below.

Mobile tests

Select Mobile, then click Continue to proceed to the Choose Networks page.

Classic add Mobile test

Backbone network is automatically selected. Click Continue.


Mobile tests can only be provisioned to run on the Backbone network and are identified as Backbone in the test lists.

Synthetic Classic mobile test on backbone

On the Specify Scripts page, select Record a Transaction, then click Open Web Recorder.

Classic record mobile script

On the Record a Transaction page, select the mobile device to emulate.

Click the downward-facing arrow for Device settings, click the list arrow, select the device, and click Save Selected Device.

Specify a location.

Click the downward-facing arrow for Geolocation settings, click the list arrow, select the desired option, and click Save Geolocation Settings. You can keep the default of No location, Use the mobile node location or specify a Custom Location. For a custom location, enter the latitude (use a negative for the southern hemisphere) and longitude (negative for western hemisphere).

Continue on to Record the Transaction.

After you record a Mobile transaction, and after you provision a Mobile test, you can change the device type or geolocation in the Script Options. See Reviewing and Editing a Transaction.

Record the transaction

  1. Enter the URL of the web page where you want to begin the test, and click Start Recording.

    The Web Recorder launches a new window to record your interactions with the web application. The window is sized to match your browser or device selection. The Web Recorder extension icon appears on the right side of the address bar in the browser window.

  2. Navigate through your web application's workflow: make selections, type in form fields, click links for web pages, etc.

    If you are recording a Mobile transaction, you can insert a Rotate action to change the device's orientation (from portrait to landscape, or vice versa). Click the Web Recorder extension icon to access the Rotate options. See Web Recorder Actions for details.

    When you record typing text into a masked field (e.g., a password), the text is automatically encrypted in the Keystrokes action. You can also manually encrypt Keystrokes text after you finish recording. The values recorded in the Keystrokes action are only encrypted for playback in the Web Recorder. They aren't encrypted when the test runs on the Browser Agent. See Web Recorder Actions for details.

  3. When you have finished the workflow, click the Web Recorder icon in the address bar.

    A popup window displays the number of steps and actions recorded. Click Stop Recording.

    Classic stop Web Recorder

    The recording window closes. In the Synthetic Classic Portal, the transaction editor shows the sequence of actions you recorded.

    Classic recorded transaction

After you finish recording, review the transaction and edit the actions if needed.

If the transaction requires a cookie with the same value for every test run, you can insert a Cookie action after you record the transaction. You can also add filters to the transaction. See Reviewing and Editing a Transaction and Web Recorder actions for details.