> 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](https://help.usejimo.com/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](https://help.usejimo.com/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](https://help.usejimo.com/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](https://help.usejimo.com/docs/settings/troubleshooting.md).

#### Reset user activities

Click your name at the top of the tool, then **Reset** under **Reset my user activities**: it resets your user activities, including experiences viewed and checklists completed, and refreshes the page. Use it between two test runs. To replay only the experience on screen, or one you are stuck in, use **Reset current experience** in the same panel. See [Troubleshooting](https://help.usejimo.com/docs/settings/troubleshooting.md#reset-user-activities).

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FQrFlY5p1U5U91yv4pPQN%2Ftroubleshoot-05-reset-actions.png?alt=media&amp;token=3a8b23cc-b7cd-4cd1-abc2-666ee02fae64" alt="Two reset actions of the Troubleshoot tool: Reset my user activities resets experiences viewed and checklists completed and refreshes the page; Reset current experience gets you out and lets the experience show again even if seen, dismissed or snoozed"><figcaption></figcaption></figure>

## A preview link from your assistant

If an AI assistant is connected to your project, ask it: "Send me a preview link for {draft} on {environment}." The link opens the draft in your app without the dashboard and without publishing, so a colleague can walk it too. Like the builder's preview, it tests content and positioning, not the trigger or the audience. The link expires: ask for a new one when it does. See [Set up with an AI assistant](https://help.usejimo.com/docs/getting-started/set-up-with-an-ai-assistant.md).

## 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 my 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](https://help.usejimo.com/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](https://help.usejimo.com/docs/getting-started/publish-your-first-experience/why-my-experience-does-not-show.md)
* [Troubleshooting](https://help.usejimo.com/docs/settings/troubleshooting.md)
* [Rate limiting](https://help.usejimo.com/docs/publish/trigger-at-the-right-time-when/rate-limiting-prevent-overwhelming-users.md)
