Skip to main content

Test User Setup - Verify Your Site Experience

Learn how to create a test user, log in like a real member, and verify that your site’s access, navigation, and user experience work exactly as intended.

Updated this week

Use a test user account to validate your site's functionality, access rules, and user experience — especially before launching products, onboarding flows, or full site access. This guide walks you through why it matters, how to set it up, and how to test properly.


🤔 Why Test with a Real User Account?

Preview mode is helpful, but it doesn't simulate everything. Creating a test user allows you to:

  • ✅ Confirm that product access, triggers, and navigation work as intended

  • ✅ Verify onboarding flows, email delivery, and progress logic

  • ✅ Experience the site exactly as a real user would from start to finish


📝 Before You Create a Test User

Make sure you're set up to get accurate results:

  • Use a real email address that isn’t already used in your CustomerHub site

  • Identify which product or experience you want to test (e.g., onboarding, access, purchase flow)

  • Open an incognito or private browser window to avoid session conflicts

🧠 Tip: You can use variations of your email by adding +test to the address (e.g., you+test1@email.com). Most email providers will still deliver these to your main inbox.


🛠️ How to Create and Test with a New User

  1. Add a new test user
    Go to Users > + Add User, enter a valid email, and create a test account.

  2. Assign product access
    Grant access to any product, collection, or experience you want to test. Click Save.

  3. Open a private or incognito window

  • Chrome/Edge: Ctrl + Shift + N or Cmd + Shift + N

  • Firefox: Ctrl + Shift + P or Cmd + Shift + P

  1. Log in as the test user
    Go to your site's login page and use the test user credentials.

  2. Verify the experience
    Check that onboarding flows, task lists, access rules, and page visibility all behave as expected.

  3. Complete the flow
    Test content progression, email delivery (if applicable), and any conditional logic tied to completion or access.


✅ Use Cases for Test Users

  • Testing onboarding experience triggers and visibility

  • Verifying product access, sequencing, or visibility rules

  • Simulating real user progress and completion

  • Debugging checkout, email, or automation behavior

Did this answer your question?