Security, Privacy, AI and CSR information for all Piano products now lives in one place. Explore our Compliance Center.
Analytics
English French
English French

How do I create a sandbox site in Piano Analytics?

Piano Analytics doesn't have a separate sandbox environment, but you can get the same result by creating a dedicated site in the Data Collection Portal and using it only for testing. A sandbox site is an isolated copy of your production setup: you can test new tagging, configurations, and updates on it without affecting your production data or your live reports.

A sandbox site lets you:

  • Validate changes: check that a new tag or update works as expected before you deploy it to production.

  • Catch bugs early: find and fix tagging problems in a controlled setup, so they never reach your production data.

  • Train and demonstrate: onboard new users or show a feature to stakeholders without touching production reports.

  • Experiment safely: try new tagging approaches and A/B tests without disturbing real visitors or skewing real numbers.

Before you start

Only organization administrators can create a site. If you don't see the + button in the Data Collection Portal, ask an administrator in your organization to create the site for you or to grant you the required permissions.

Create the sandbox site

  1. Open the Data Collection Portal and go to the Dashboard tab.

  2. Click the + button at the bottom right of the screen.

  3. Fill in the site details:

    • Contract: the contract the site belongs to. This field only appears if your organization has several contracts.

    • Site label: a name that makes the purpose obvious, for example "My Site - Sandbox".

    • Default URL of the site: the URL of your test or pre-production website, for example "https://staging.mysite.com".

    • Timezone: use the same time zone as your production site so that test and production data line up.

    • Strict domain: defines whether traffic from subdomains counts as a referrer site. Use the same setting as production.

    • Duration of inactivity: how long a visitor can be inactive before a new visit starts. Use the same value as production.

  4. Validate the request.

The new site will appear in your site list with its own Site ID.

Copying your production settings keeps test results comparable. For example, if production uses the Europe/Paris time zone, a test site in another time zone would split the same visits across different days.

Send test data to the sandbox site

Update the tagging on your test environment to use the sandbox site's Site ID instead of the production values. Depending on your implementation, this is done in one of these places:

  • Piano Analytics JavaScript SDK: the site and collection domain values in your SDK configuration.

  • Tag manager: the Site ID in your tag template or custom tag.

  • Server-side implementation: the Site ID used by your server-side calls.

Keep the properties in your tagging plan identical between the sandbox and production sites. That way, what you validate on the sandbox is exactly what you will deploy.

For the full implementation details, see the Piano developer documentation.

Verify your data

Select the sandbox site's Site ID in your analyses (for example in Explorer or Data Query) to confirm your test events arrive. Then check that none of those events appear in your production site.

Billing

Piano bills on the number of events collected, not on the number of sites. Test traffic is usually low, so it doesn't normally affect billing.

Last updated: