Inspector
Live inspector
See which experiments are running on any page — right on your own site — and preview both versions without waiting to be bucketed. The inspector outlines every element an experiment touches and lets you flip between the control and the variant just by reloading. It’s a separate, optional script for you and your team; your visitors never see it.
Setting it up
-
1
Copy your
inspect_tokenfrom your workspace settings. This is a separate, private token — not your public workspace token. -
2
Add it to the same
window.$mezura.dataobject you set up during installation. -
3
Load
inspect.jsright after the tracker. The inspector needs the tracker (track.js) on the page to work. -
4
Open a page that has a running experiment. You’ll see the outlines appear.
<script>
window.$mezura = {
data: {
workspace_token: "{workspace_token}",
page_type: "ProductListing",
inspect_token: "{inspect_token}"
}
};
</script>
<script async src="https://mezura.test/track.js"></script>
<script async src="https://mezura.test/inspect.js"></script>Parameters
| Field | Type | Required | Description |
|---|---|---|---|
| inspect_token | string | Required | Your private inspector token, found in workspace settings. It’s different from your public workspace_token: only someone with this token can inspect your experiments, and you can rotate it any time. |
What you’ll see
- A dashed outline around every element an experiment changes on this page.
- A small tab on each outline showing whether the Original or the Variant is currently displayed.
- Hover an element to open a card with the experiment name, a short summary, its target metric, and the control vs. variant content side by side.
- Reload to flip. The first load shows the page as usual; every reload after that switches every experiment between control and variant, so you can review both versions.
Keep your inspect token private
The inspector is a tool for you and your team, so use it on staging or while developing — not on your live site. Anyone loading a page that has both inspect.js and a valid inspect_token would enter the reload-to-flip mode, and their visits are kept out of your real results. When you’re done, remove the inspector script (or the token). If a token ever leaks, just rotate it from your workspace settings — your public tracker keeps working untouched.
[mezura-inspect].