Handling different environments - staging vs production

Many applications have a staging environment and a production environment. What’s the best way to implement Product Fruits when your application is developed in this manner? 

With Product Fruit’s workspaces and the ability to copy content between them, this is easy to tackle. Infact, it’s just a matter of figuring out which approach you’d prefer.   

One workspace approach


It's possible to just use one workspace located on your production environment. To test content before deploying it to your users, you can utilize segmentation, creating a segment just for a specific username or email address. Once the content testing process is completed, the segment can be removed or changed.  

Two workspace approach


Another option is to create one workspace for your staging environment, and then a second for your production environment. This allows you to create the content on your staging environment and then copy it to your production workspace when it’s ready to be shared with the masses. Note that only tours and hint groups can be copied but other types of content should be easy to transfer manually.