Configuring Virtual Page Turns in Multi-Step Synthetic Scripts

Table of Contents

• Overview 
• Before You Begin 
• Enabling Virtual Page Turn on a Step
• Setting the VT Start Command
• Best Practice: End with a waitForX Command
• FAQ

Overview

A Virtual Page Turn lets you define a custom timer within a single step of a synthetic script — instead of relying on a full page load to mark the start and end of a measurement. This is useful for interactions that don't trigger a traditional page turn, such as clicking Add to Cart, opening a modal, or expanding a section on the same page.

When Virtual Page Turn is enabled on a step, the timer starts on the command you designate as VT Start and ends after the final command in that step. This gives you accurate timing data for in-page interactions that a standard page-load-based step wouldn't capture correctly.

Before You Begin

• You'll need edit access to the synthetic script you want to update. Ensure the Real Browser Synthetic Scripts page is available in the gear icon Settings and Admin menu. If not, please reach out to BT Support or your BT representative. 
• Identify which step in your script represents an in-page interaction (for example, an Add to Cart click, a filter application, or a modal open) rather than a full page navigation.

Enabling Virtual Page Turn on a Step

1. Navigate to the Real Browser Synthetic Scripts page via the gear icon in the top task bar of the portal. 
2. Open the synthetic script you want to edit.
3. Locate the step where you want to measure an in-page interaction.
4. Check the Virtual Page Turn checkbox in the top-right corner of the step.

Setting the VT Start Command

Once Virtual Page turn is enabled on a step, each command row displays a VT Start checkbox. VT Start is required to enable the Virtual Page turn. 

1. Review the commands listed in the step.
2. Check VT Start next to the command where you want the custom timer to begin. This is typically the action that triggers the interaction — for example, a click command on your Add to Cart button.
3. Leave VT Start unchecked on all other commands in the step. Only one command per step should be marked as VT Start.

Once VT Start is set, the timer begins when that command executes and continues until the last command in the step completes.

Best Practice: End with a waitForX Command

For accurate timing, make sure the last command in the step is a waitForX command (such as waitForTextPresent or waitForElementPresent) that confirms the interaction has finished — for example, waiting for confirmation text like "has been added to your cart." This ensures the timer captures the full duration of the interaction rather than stopping prematurely.

FAQ

Can I use Virtual Page Start on more than one command in the same step? No. Only one command per step can be marked as VT Start. If you need to measure multiple distinct interactions, break them into separate steps and enable Virtual Page Turn on each.

What happens if I don't end the step with a waitForX command? The timer will still stop after the last command in the step, but without a wait condition confirming the interaction is complete, your timing may not reflect the true duration of the interaction.

Does enabling Virtual Page Turn affect other steps in my script? No. Virtual Page Turn is configured per step and only affects the timing behavior of that individual step.

What commands are not able to be configured as a VT? Virtual Turns cannot be added to steps including an Open command. To workaround this, place the open command its own step and configure the VT on the subsequent step. 

Need more help? Contact our support team at support@bluetriangle.com