Proxy, Useberry Snippet, and their differences

Useberry’s Website Usability Testing feature enables researchers and product teams to test live websites—rather than static prototypes—within the Useberry platform. This facilitates a more authentic evaluation of user behavior, capturing real interactions such as clicks, user flows, and optional session recordings.

To enable this functionality, a secure communication channel must be established between the test environment and the target website. Useberry offers two distinct implementation methods to achieve this: the Proxy Method and the Useberry Snippet Method. While both allow websites to function within Useberry tests, the underlying technologies, performance characteristics, and limitations are significantly different.

This article provides a comprehensive comparison between the two methods, outlines how each operates, and clarifies why the Useberry Snippet is generally the preferred and more robust approach.

2. Proxy Method: How It Works

The Proxy Method functions by routing all test traffic through a Useberry-managed proxy server. The original website is fetched and re-served under a proxy domain, where Useberry’s tracking logic is injected on-the-fly.

Strengths:

No need for code changes on the target website.
Suitable for quick, one-off tests or for users without access to website source code.

Limitations:

Domain Mismatch: Websites often serve cookies scoped to their domain. When served through a proxy, these cookies cannot be written or accessed properly.
Subresource Integrity (SRI) Conflicts: Modern websites use the integrity attribute to ensure scripts and resources haven’t been tampered with. These checks fail when routed through a proxy, causing some resources (e.g., JavaScript files, stylesheets) to be blocked by browsers.
Blocked Functionality: Complex web applications may rely on CSP (Content Security Policy), CORS headers, or tightly bound authentication flows—all of which are susceptible to disruption in a proxied environment.
Visual or Interactive Discrepancies: Minor but critical UI elements may fail to load, breaking the test experience.

The Proxy method is continuously being improved, but structural limitations inherent in how modern web security works mean some issues are unavoidable.

3. Useberry Snippet Method: How It Works

The Useberry Snippet Method uses a dedicated JavaScript snippet that is manually embedded into the <body> of the live website. Once present, the snippet serves as a secure bridge between the test participant’s interactions and the Useberry platform.

Key Characteristics:

Native Domain Execution: Because the site is loaded directly under its own domain, all cookies, secure headers, and browser policies function as intended.
Scoped Activation: The snippet is dormant when the website is accessed normally and only activates when loaded within the Useberry testing environment.
Event Tracking: The snippet captures click events, mouse movement, element hovers, and task completion events, then securely transmits this data to Useberry’s analytics engine.
Element Targeting: For tests involving task completions, the snippet identifies and flags DOM elements when specific actions are performed. These are then logged and used to assess test success criteria.
No UI Breakage: Since the Website remains under its original domain, no proxy-related rendering or logic issues occur.

Implementation Requirements:

The snippet must be inserted at the bottom of the <body> of each page you want to test.
This action must be performed by a developer with access to the site’s codebase.
Once implemented, the website can be imported to the Useberry workspace via the “Snippet Method” option.

4. Security and Data Integrity

The Useberry Snippet Method offers distinct advantages in terms of data integrity and test fidelity:

Domain-Level Isolation: Snippet data collection occurs in-browser, scoped exclusively to the Useberry test environment, and cannot capture any user data when the site is accessed outside of that context.
No Third-Party Routing: Unlike the Proxy method, no external domain intermediates traffic, eliminating the risk of data loss or transformation.
Failsafe Design: The snippet is built to gracefully degrade. If for any reason the snippet is inactive or removed, the website continues to function normally—outside the test context—with no risk to live traffic.

Conclusion

While the Proxy Method provides a convenient entry point for quick or informal tests, its reliance on domain rerouting and the limitations imposed by modern browser security standards make it less reliable for production-grade testing. Conversely, the Useberry Snippet Method offers a technically sound, secure, and comprehensive integration that ensures consistent data collection and accurate insights.

For robust usability testing, especially in production environments or with high-value user flows, the Useberry Snippet is unequivocally the recommended choice.