> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/getting-started/publish-your-first-experience/test-safely.md).

# Test safely

Preview tests the content. Only a publication tests the trigger, the pages, the audience and the environment. So you will publish to test, and the question is how to do it without any user seeing a draft. Three tools: a test segment, the Troubleshoot tool, and a few settings to change while testing.

***

## A segment with only you in it

{% stepper %}
{% step %}

### Create the test segment

Go to [Users & Segments > Segments](/docs/analyze/users-and-segments/audience/segments.md) and create a segment whose condition is your email (or your user ID). Name it "Test, me". See [Create a segment](/docs/analyze/users-and-segments/audience/segments/create-a-segment.md).
{% endstep %}

{% step %}

### Add an internal segment

Add a second one, "Internal", with your company's email domain, for the second circle of tests.
{% endstep %}

{% step %}

### Publish to the test segment

In **Who** on the experience, pick the test segment. Publish. Only you see it, on production, with real data.
{% endstep %}
{% endstepper %}

This needs identify to be in place ([Step 4](/docs/getting-started/install-jimo.md)). Without it, the alternative is a Staging environment where only your team goes.

## The Troubleshoot tool

Your window into what Jimo sees on a page. It shows your user, segments and attributes, and every published experience with its status and the conditions evaluated. Open it from an experience's **...** menu, or with the shortcut once enabled in [Settings > Troubleshoot](/docs/settings/troubleshooting.md).

#### Reset user activities

In the tool's user panel, it clears what this browser has seen: experiences shown once, completed checklists, dismissed banners. Use it between two test runs. It acts on this browser only, does not touch analytics, and does not remove you from segments.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F8ml2sTHOOoUdooUpU7vS%2Fn23-reset-scope.png?alt=media&amp;token=83b164bb-c200-49e8-8a6a-1cc37a6f9b8e" alt="Reset clears what this browser has seen, it does not touch analytics, segments or other browsers"><figcaption></figcaption></figure>

## Settings to change while testing

| Setting              | While testing                                                                    | Before going live                                                      |
| -------------------- | -------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| Rate limiting (When) | Off on the experience, so it shows on each reload                                | Back on, otherwise a user who opens three pages gets three experiences |
| Show once (When)     | Keep it on and use Reset user activities, so your test matches the real behavior | Keep it on                                                             |
| Env                  | Staging if you have one                                                          | Production                                                             |
| Who                  | Test segment                                                                     | The real audience                                                      |

Changes to Who and Env apply without republishing. Changes to When require a republish.

## What to look at

* On a second browser, or in a private window logged in as another test account, to confirm "show once" behaves per user and not per browser.
* On the screen sizes your users have. A tooltip that fits on your monitor may overlap on a laptop.
* On the pages before and after the targeted one, to confirm the Where rule does not leak.
* In [Analytics](/docs/analyze/analytics.md), that your test views are there. They count: if you want clean numbers for the real launch, duplicate the experience and archive the test copy.

## Related

* [Why my experience does not show](/docs/getting-started/publish-your-first-experience/why-my-experience-does-not-show.md)
* [Troubleshooting](/docs/settings/troubleshooting.md)
* [Rate limiting](/docs/publish/trigger-at-the-right-time-when/rate-limiting-prevent-overwhelming-users.md)