Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In this article, we explained how you could check the deployment conditions on your website. We also explained how you can debug your script if your survey did not show as you had expected. In the following article, we will elaborate more on the deployment conditions and the reasons why these conditions can show a false-value in your console.

...

Once your cookies are deleted, go back to the ‘Console’ tab, and click on refresh. You will see a line with ‘passive condition set’ and a random number. If this random number is smaller than your percentage, it will return the value true. If this random number is larger than your percentage, it will return the value false. You will only see this line the first time you refresh the page. In this case, 79.5 is the random number, which is larger than 10, so it will return a false - value. If all is done well, and you got a false-value, you should not see ‘triggered!’ on the last line anymore, instead, you should see ‘not all OK…’ on the second to last line.

...

Testing and triggering surveys with a low ‘Show only to a percentage of users’ rate can be time-consuming. To manually trigger the survey you can edit the cookie values of the following cookies:

...

You can set the value of Pastease.[trigger_type].chance.XXXXX to “chance01.0” (or anything below the value used at ‘Show only to a percentage of users’). This is done by double-clicking on this cookie, in the Application tab. In our example, the random number was 79.5, which gave us a false-value. If you change this number to 1.0 we will get a true-value, since 1.0 is smaller than our percentage, 10. You can delete Pastease.[trigger_type].activated.XXX. 

...