The in-app campaign is a great way to survey your active customers, and generally it ensures one of the highest reply rates.

However, before you launch your survey to the wider public, you need to make sure it looks according to your expectations both by itself as well as in your environment.

If you already embedded the script on your website on the correct page it should be displayed, and want to check how it looks or works here is what you should do:

First, go to the audience page and make sure to add a safeguard from your survey firing to your customers. To do so, in the email field, add a rule that will make sure that the survey shows up only to the employees of your company, or even only to you:

Next, go to the schedule settings and make sure that the survey is scheduled to fire immediately without any delays and is recurring daily. Once you are done with the testing phase, please don't forget to adjust this setting.

Depending on your level of access, make sure to either log in to the page where your survey is, either under different emails, or change the email that shows up within the script of the survey.

If you don't have access to the code of your website and want to have a feel of how the survey will look like before sending the instructions to your product team or website developer, you can do it through third parties.

One example of such a third-party platform is Glitch, but you can also use a text editor for code and launch the HTML script l

<div id="retently-survey-embed" data-href="https://app.retently.com/api/remote/tracking/620a4974a8b5393e01eee1dc" data-rel="dialog" data-campaign="regular" data-email="ab@retently.com" data-firstname="Alex" data-lastname="Bitca" data-company="Retently" data-tags="inapp" ></div>ocally.

One advantage to this type of testing is that you have easy access to edit the data and create new respondents, without the need to create new accounts or emails. You can adjust this directly in the script of your in-app.

By simply changing the "data-email" parameter.