It depends on the target application: if there is an area restricted to a subset of users, then you can deploy the content there before going live, as a way of piloting the project.
You can also define some visibility rules and make the Journey available, for instance, only in some countries before going for a global rollout.
Another possible solution is to deploy on the production server with our Browser Extension: By doing this, only those who have the Browser Extension installed and set to your own server will be able to see the Journeys and Tips that you have made. For more info regarding this technology, please check out this article: Browser extension
Please check this article to see our suggested test environments.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article