Skip to content

Working with environments

Since many plugins and features you will use in the JavaScript SDK cause tracking and content alterations, it's useful to be able to test new features before putting them live. Orbee provides TMS Environments for this purpose.

In Orbee's Platform, you can create multiple staging environments for your script. When creating a new environment, you can choose a clean slate, or copy the existing production environment.

How to test an Environment

In order to test an environment besides production, you must have a cookie set on your device. Orbee's Platform provides a UI to make this easy for you.


You will need third-party cookies enabled on your browser. If you do not, then this feature will not work.

When loading your site, the script's server will read the cookie and load your staged environment's script!

Creating the Test Environment

  • Navigate to the List TMS Plugins page on the Orbee Platform.
  • Click the "Create Test Plugin Environment" button and hit "Continue" on the modal.
  • A new option will show on the "Select Environment" dropdown. The test environment is appended with "(staging)".

Admin > TMS Plugin Configurations > List TMS Plugins

Adding plugins to the Test Environment

Navigate to the Create TMS Plugin Configurations page on the Orbee Platform.

Admin > TMS Plugin Configurations > Create TMS Plugin Configurations

From here you can add Plugins to your test environment to test new features and integrations.

Additional Environment features

When using staging environments, you get the benefit of some additional features when testing and debugging your setup.

Script Environment Awareness

When loading a staged script, it will be aware that it is in a staging environment. In the debugger, you can disable dropping segments and sending pixels if you want. You can also enable the debugger to open automatically when using a staging script.


Staged scripts also provide you with ways to "trigger" certain scenarios the script might experience. You can fake different inputs and browser features with the debugger, and the script will react as if those things are true.

For example, you can be viewing a regular landing page, but simulate what the page might do if you came through a retargeting Google Ads campaign.