To Test an Experience before you publish, follow the steps below:
- Go to the Left Nav Menu > Settings > Scroll down to Experience Settings.
In the Send Test Emails To field, give an email to receive the test email window
Note: Send Test leads with the pattern (name)hlytest(0-9)@hushly.com, which will be enriched as Test leads by Hushly. - Then, go to Experiences: From the Left Nav Menu > Experience > Hover over an Experience you want to test and click on the test icon.
or
Open an Experience and click Test in the top right corner of the Experience page. - Enter the URL of the page where you want to show the Experience. Click Test.
Important: The page should have Hushly code embedded to trigger the Experience.
- A new browser window is launched, and when the user attempts to exit, the Experience is displayed.
- The Experience is triggered based on the configuration. When you configure an:
- On Exit-Intent Experience, when the user tries to exit the webpage, the On Exit-Intent Experience opens.
- On Click Experience, and the user clicks the designated elements, the On Click Experience opens.
- On JavaScript Experience, and the webpage detects the event, the On JavaScript Experience opens.
- On Timer Experience, and the webpage detects the expiry of the timer, the On Timer Experience opens.
- Embed Experience and the user accesses the content, the Embed Experience launches.
- You can also test the opt-in message by giving a business email with the pattern (name)hlytest(0-9)@hushly.com. Leads that come in with this pattern will be enriched as Test leads by Hushly.
- You will receive an email with a link to download the content. Click Download.
- A pop-up window asks for permission to share your enhanced business profile, click Download Now.
- You are redirected to the Asset’s full view with the download button enabled. You can read and download the Asset by clicking the download icon that is placed in the top-right corner of the page.
Related Topics:
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