Manage connected domains
Add the domains where Appcues runs and choose which ones each experience uses.
Table of Contents
Connected domains are the websites where your Appcues experiences can appear, such as app.yourcompany.com or a staging site. Add each domain once in Settings, then choose on each experience whether it shows on every domain or only on some. Studio called these available domains.
Prerequisites
- Appcues is installed on the domains you want to add. See Install the Appcues SDK.
See your connected domains
- Click your account menu at the bottom of the left sidebar, then Settings.
- Under Apps & Installation, click Web. Connected domains lists every domain with its status:
- Installed: Appcues has seen page views from this domain.
- Not installed: Appcues hasn't seen page views from it yet.
The status comes from tracked page views, so a newly installed domain can show Not installed for a while. To check an installation directly, open the Appcues debugger on that domain.

Add a domain
- On the Web page, click Add domain.
- Enter the domain, such as
app.yourcompany.com:
- Leave out
https://and any trailing slash. - Enter it exactly as it appears in your browser's address bar. Domains are case-sensitive.
- Leave out
www.unless your site uses it. If experiences don't load, add thewww.version as a separate domain. - For local testing, enter
localhostwithout a port number.
- Click Add domain. "Domain added." appears, and the domain is listed.
Add one domain at a time.
Remove a domain
- Click the menu (⋮) next to the domain.
- Click Remove domain, then Remove to confirm.
Choose the domains for an experience
- Open the experience and click Settings.
- In Where this appears, under Which environment should this experience appear on?, choose one:
- Everywhere my Appcues embed script is installed: every domain where Appcues runs.
- Only the domains I choose: tick the domains in the table. Leave at least one ticked.
See Configure an experience's settings.
Use wildcard domains
A wildcard (*) matches any one subdomain, which helps when your team creates environments on the fly, like a staging site per developer. Add the wildcard pattern as a domain, then tick it on the experience.
A * replaces exactly one part of the domain between dots:
| Pattern | URL | Matches? | Why |
|---|---|---|---|
*.staging.yourapp.com |
steve.staging.yourapp.com |
Yes |
* matches steve
|
*.staging.yourapp.com |
staging.yourapp.com |
No | There's no part for * to match |
*.staging.yourapp.com |
dev.test.staging.yourapp.com |
No |
* matches one part, not two |
*.yourapp.com |
app.yourapp.com |
Yes |
* matches app
|
*.yourapp.com |
yourapp.com |
No | There's no subdomain for * to match |
Wildcard domains never show Installed. That's expected, and the wildcard still works.

If a domain or experience isn't working
- A domain is missing from an experience's list. Add it on the Web page first.
-
The experience doesn't show on a domain. Check that the domain matches exactly, including
www.and casing, and that the experience's page and audience rules are met. Use Test URL targeting on the experience's Settings tab. - A domain shows Not installed. Open the Appcues debugger on that domain. If the debugger loads, Appcues is installed and the status will catch up.
Still stuck?
Collect the following and contact support:
- Your Account ID, from the top of the Web page.
- The domain and the full page URL where the experience should appear.
- The experience's name and Experience ID.
- A screenshot of the debugger on that page.