How to test content before sharing it with your users

There are several ways how you can restrict your content until is ready.

Save & Publish

You have to Publish your Tour, Hint or Announcement in order to be seen by your audience. When you work in the editor, you can Save your work in progress, don't worry, it wont be seen by anyone, until you Publish it.

Resctricted Access

In Workspace Settings, you can restrict all Product Fruits content, for example to one domain only. Keep in mind that you are restricting all content, including the content you already published. These usernames are usernames you are passing via the JS snippet into Product Fruits.

You need to be using the PF code snippet, not just the PF extensions for restricted access.


Segmentation is the best way how to restrict the content, because you can do it for each Tour or Hint group separately. You can create a segment based on email domain (domain of your company) and then that content will be seen only by users with this email domain. Make sure you are sending the right email address to Product Fruits. When you are satisfied, you just remove this segment from the rules.

For the testing of "Once per user" content its useful to use Restarting.

You need to be using PF code snippet, not just the PF extensions for the segmantation.

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

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.