We are developing a new version of our application. It will be the first version to include Cookiebot and Google Analytics.

Currently, we have the following configuration in Cookiebot admin console. The stage environment is listed as an alias for the production environment.

When we publish the new version to the production environment, we would like to be GDPR compliant from the moment we go live (with all the cookies listed, including ones used by newly-added Google Analytics). Is it possible to perform a cookie scan on the stage environment kb-stage.website (which has Google Analytics) and later switch the URL to production kb.website, but keep the list of cookies which were found on the stage environment?

Release cycle of most applications follows the pattern dev -> test -> stage -> prod. If a new version of the application uses some new cookies, Cookiebot will only be able to scan them when the application is deployed to production. This means that:

1. Website will not be GDPR compliant until the scan on the production environment is finished and new cookies are detected.
2. You can't verify the consent screen on the stage environment because it will not list cookies which were added in the new version.