How UX Metrics Handles Sharing and Analysis of Research Results

Updated

UX Metrics is built so that research outputs can leave the researcher's account and reach teammates, stakeholders, or clients. Based on the platform's own description, results are distributed through links, embeds, live URLs, and shareable analysis, and every method — card sorts, tree tests, surveys, prototypes, interviews — runs inside one workflow rather than in separate tools. That matters if your main bottleneck is not collecting data but getting other people to look at it and act on it.

What "shareable analysis" means in practice

The site describes its output as shareable analysis rather than a static report export. The practical implication is that you are distributing a view of the results, not a frozen document. Two consequences follow:

  • Updates travel with the link. If you keep collecting responses, anyone holding the link sees the current state rather than the state at export time. This is useful for ongoing studies; it is a risk if you need a fixed snapshot for a formal sign-off.
  • The audience needs no account of their own to view what you send — the distribution methods listed are links and embeds, which are view-oriented. Note that the site's free tier is defined by participant count, not by viewer count, so sharing with a large internal audience is not the same constraint as running a large study.

The four distribution routes

Route Best for What to check before you rely on it
Shareable link Sending findings to a client or a Slack channel Whether the link is public or restricted, and whether it can be revoked
Embed Putting a live result view inside a Confluence page, Notion doc, or internal dashboard Whether the embed updates automatically or is a one-time snapshot
Live URL testing Testing a real, deployed page instead of a static prototype Whether the URL is publicly reachable or sits behind a login
In-platform collaboration A research team reviewing the same study together Who on your plan can open the study versus only the shared view

The distinction that trips people up most is the third row. Live URL testing means participants interact with an actual address, so anything gated behind authentication, a staging password, or a VPN will not behave the way it does for a normal visitor. Decide early whether you are testing the real experience or a prototype of it, because that choice determines whether your results reflect production conditions.

A concrete workflow

Say you have run a tree test on a redesigned navigation and need sign-off from a product manager and two designers.

  1. Confirm the study is complete enough to interpret. Partial results are still viewable through a shared link, so decide whether you want reviewers seeing a half-filled sample.
  2. Generate the shareable analysis view for that study.
  3. Distribute by the route that matches the audience — a link in the project channel for a quick look, an embed in the design doc if the team will return to it repeatedly.
  4. State the conditions alongside the link: sample size, participant source, and whether the study is still open. A shareable view does not carry that context on its own.
  5. Collect feedback in one place. Because results are viewable rather than exported, comments tend to land in chat or the doc — pick one and say so, or you will be reconciling three threads.

Where this approach fits and where it does not

Choose the link-and-embed model if your stakeholders are internal, your studies are iterative, and you want people checking results repeatedly without asking you for a fresh export.

Prefer a fixed export if you need an immutable record — a client deliverable, a compliance artifact, or a results appendix attached to a dated decision. A live view that changes after the fact is the wrong object for that purpose.

Watch the participant limit, not the viewer limit. The free tier covers up to 3 participants per study. That is a constraint on how much data you can collect, not on how many people can look at it — so a small pilot study can still be shared widely.

Questions the site does not answer

The available material does not specify link permissions, expiry, password protection, or whether embeds are live or static. If any of those determine whether you can use this with an external client, verify them directly before committing a study to the platform. Likewise, the pricing page is linked but no figures are given here, so treat cost as something to confirm rather than assume.