Where: target pages and domains
Choose the pages and devices an experience shows on: what a URL rule is matched against, the operators, the domain filter, trailing slashes and single-page apps.
Where sets the pages an experience shows on, and the devices. It works on the part of the URL after the domain; the domain itself is the job of the environment you pick when you publish.
You will have at the end: URL rules that match the pages you mean, tested before you publish, and none of the usual surprises with trailing slashes, query strings or hash routes.
Environment or Where

Path, query string, # fragment
/pages/billing.html?tab=1#top
The Where rules of the experience
Write only the path in Where, and leave the domain to the environment. A Where domain filter that names a domain outside the selected environment matches nothing.
Choose the pages

Under Page to show this experience, three options. For a tour that runs over several pages, Where sets the page it starts on.
On all pages
Every page where the Jimo snippet runs. For a tooltip, a hotspot or a hint pinned to an element, the experience still only shows where that element exists. If the element is not unique, every matching element on each page is targeted.
On a specific page
One full address, such as https://b2b.usejimo.com/pages/billing.html. If you opened the builder on a page of your app, the field can come pre-filled with that address. The field cannot be left empty: without an address, the Where summary reads Missing url.

On filtered URLs
Up to 20 rules on the path, combined so that a page must match all of them or any of them, plus an optional domain filter. This is the option for a group of pages, for pages with ids in the URL, and for exclusions. Set it up as below.
Write and test rules
Narrow to some domains, if needed
Most of the time the environment already sets the domains and the filter stays empty. When the rules must only run on some hosts, fill the domain filter, see The domain filter. With generated rules, also set the domain, so that they stay on the right site.
What a rule is matched on
A rule is compared with everything after the domain: the path, the query string and the # fragment together.
The user is on
equals /pages/billing.html
starts with /pages/billing
contains billing
/pages/billing.html
Match
Match
Match
/pages/billing.html?tab=1
No match
Match
Match
/pages/billing.html/
No match
Match
Match
/pages/profile.html#billing
No match
No match
Match
Trailing slash
Many apps add a / at the end of the URL. An equals rule then fails. Use starts with, or a regex that accepts both: ^/pages/billing\.html/?$.
Query strings
equals / matches the home page only without parameters, not /?tab=1. Use starts with, or matches regex ^/(\?.*)?$ for the home page with any query string.
Hash-routed apps
In an app whose screens live after #, such as /#/projects/123, the fragment is part of what the rule reads. Target it like any path: starts with /#/projects/.
Operators
Equals / Doesn't equal
is exactly the value
One page without parameters
Starts with / Doesn't start with
begins with the value
A section of the app, /settings
Ends with / Doesn't end with
ends with the value
A file or last segment, .html
Contains / Doesn't contain
holds the value anywhere
A keyword, exclusions
Matches regex
matches the regular expression
Ids, "something after a prefix", several variants
The Doesn't operators exclude. Combine a positive rule with a Doesn't rule and match all of them: Starts with /pages/ and Doesn't contain /sign-in. Every other operator can also be written as a regex.
Variable parts of a URL
Ids and other variable parts of a URL go in a matches regex rule: the other operators read the value as plain text.
Any user profile, /user/<id>/profile
^/user/[^/]+/profile$
/user/42/profile
/user/42/settings
An article in any category
^/blog/[^/]+/article
/blog/108/article, /blog/tuto_1/article
/article108, /blog/article/tuto_1
A blog post by year and month
^/blog/\d{4}/\d{2}/
/blog/2026/10/launch
/blog/latest
Regex you will reuse
A record page, any id: /projects/123
matches regex ^/projects/[^/]+$
At least one segment after a prefix, not the bare prefix
matches regex ^/#/enrich/product/.+
The same page with or without a trailing slash
matches regex ^/pages/billing\.html/?$
A page with any query string
matches regex ^/pages/billing\.html(\?.*)?$
starts with /#/enrich/product/ also matches /#/enrich/product/ itself. Use the regex with .+ when the page must have something after the prefix. Escape a literal dot as \..
The domain filter
With On filtered URLs, the domain filter narrows the rules to some hosts. Most of the time the environment already does this, and the filter stays empty. A typical use: the same rule on two sites, such as blog.yourapp.com and test.yourapp.com in the domain filter with starts with /article_ as the rule, for every article on both.
Write the host only:
app.acme.com,localhost:3000. A full URL withhttps://or a path never matches.Several domains: separate them with a space, or press Enter after each one.
The
www.of the page is ignored: writeacme.com. This rule is for the Where domain filter only. The Domains field of an environment is a different field with its own rule: there, awww.prefix is part of the host, see Environments and domains.An entry with regex characters is read as a regular expression:
\.acme\.com$for every subdomain.With On all pages or On a specific page, the domain filter is ignored.
Devices
Under Select devices to show this experience on: Desktop, Tablet, Mobile. A new experience is set to desktop only. You can tick several devices on the same experience. When the content needs a different copy or layout on small screens, duplicate the experience and adjust each copy for its device.
From your assistant
Ask: "Show the Billing banner only on /pages/billing.html on b2b.usejimo.com." The preview warns that equals excludes the same page with a query string, and says whether visibility widens or narrows. More in What to ask?
Verify
Type the address of a target page in Test your URL: it matches. Type a page where the experience must not show: it does not.
Open the Troubleshoot tool on the page you target. If the URL condition is unmatched, the experience is Ineligible: compare the address in your browser, character by character, with the rule.
Check the end of the address for a
/, a?or a#that your rule does not expect, and the rule itself for a space before or after the value.
Go further
Environments and domains: what the Domains field accepts.
Targeting on dynamic apps: single-page apps and dynamic selectors.
Why my experience does not show, cause 3.
In-app tour of Where: opens a guided tour of the section in your Jimo dashboard.
Next page: Who: target the right users
Last updated


