> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/getting-started/first-steps-in-the-portal/set-up-the-application-url.md).

# Set up the application URL

Add and manage the application URLs that activate tracking, analytics, and the browser extension.

An application URL tells Userlane which domains to activate on. Without at least one URL, the browser extension does not respond on any page, the Editor[^1] does not open, and HEART[^2] does not collect data. Add every domain where Userlane should run.

{% hint style="warning" %}
**Prerequisites.** Sign in to the Userlane portal with the **Administrator** or **Moderator** role. The target application must be accessible at an HTTPS address.
{% endhint %}

## Add an application URL

The portal prompts for the first application URL during account creation or the first time you open the Editor. The first specific URL you add becomes the default automatically. To add more URLs afterward, use the steps below.

{% stepper %}
{% step %}

#### Open application URL settings

In the portal, open the application you want to add URLs to and select **Settings** at the bottom of the left sidebar. Under **Application Settings**, select **Application URLs**.

<div align="left" data-with-frame="true"><figure><img src="https://259567114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF6bxg8i3T6U4vZ3k7PHi%2Fuploads%2FX5Bt9xHwSV4kY7MsHK6s%2Fimage.png?alt=media&#x26;token=557e52bf-bf8f-4a8f-a6b0-3c416fe9ae17" alt="Application Settings menu in the portal with Application URLs selected" width="259"><figcaption><p>Application URLs sits under Application Settings.</p></figcaption></figure></div>
{% endstep %}

{% step %}

#### Add the URL

Select **Add Application URL**. In the dialog, enter the full domain including the protocol (for example, `https://app.example.com`). Select **Save**.
{% endstep %}

{% step %}

#### Confirm the URL appears in the list

The new URL appears in the list with its **Active** toggle switched on.

<div data-with-frame="true"><figure><img src="https://259567114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF6bxg8i3T6U4vZ3k7PHi%2Fuploads%2FOaPbBoDCuQuofPfcm7yz%2FScreenshot%202026-09-08%20at%2009.00.57.png?alt=media&#x26;token=61219360-2472-451f-a0c5-538d6a65e359" alt="Application URLs list showing a newly added URL with the Active toggle switched on"><figcaption><p>A new URL is active as soon as you save it.</p></figcaption></figure></div>
{% endstep %}
{% endstepper %}

The browser extension now activates on the added domain, HEART begins collecting data for it, and you can open the Editor there.

{% hint style="info" %}
**Refresh delay.** The browser extension refreshes its URL list once per hour. After you add a new URL, end users may need to wait up to 60 minutes. Restarting the browser forces an immediate refresh.
{% endhint %}

## Use wildcards to cover multiple subdomains

A wildcard URL matches any subdomain under a given domain. Use a wildcard when the application runs on multiple subdomains and each one should activate Userlane.

**Pattern:** `*.example.com` matches `us.example.com`, `eu.example.com`, `staging.example.com`, and any other subdomain of `example.com`.

Two limits apply to wildcard URLs:

* The Editor does not open on a wildcard URL. The portal checks editing access against specific URLs only, so list each domain where you need the Editor individually, and open the Editor from a specific URL in the list.
* A wildcard URL cannot be set as the default.

## Set a default URL

The default URL opens when you select **Open Application** in the guides section. It is also the redirect target when an end user starts a guide from a shared link. The first specific URL added to an application becomes the default automatically. To change the default, follow these steps.

{% stepper %}
{% step %}

#### Open application URL settings

Select **Settings** at the bottom of the left sidebar, then select **Application URLs** under **Application Settings**.
{% endstep %}

{% step %}

#### Select a different default

Hover over a URL that is not the default to show the **Set as default** button, then select it. The selected URL shows a **Default** badge. Only a specific (non-wildcard) URL can be the default.

<div align="left" data-with-frame="true"><figure><img src="https://259567114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF6bxg8i3T6U4vZ3k7PHi%2Fuploads%2FP6vBrDfNmp0jxjdD9mt6%2FScreen%20Recording%202026-09-08%20at%2009.14.43.gif?alt=media&#x26;token=f1af2009-0cea-466c-a633-15e15c58cc0a" alt="Animation of hovering over an application URL and setting it as the default" width="563"><figcaption><p>Hover over a URL to set it as the default.</p></figcaption></figure></div>
{% endstep %}
{% endstepper %}

The **Open Application** button and shared guide links now redirect to the selected URL.

## Disable or remove a URL

**Disable** a URL to stop the browser extension from activating on that domain without deleting the entry. **Remove** a URL to delete it permanently.

**To disable:** In **Settings** > **Application URLs**, switch off the **Active** toggle next to the URL. The browser extension stops activating on that domain, and HEART stops collecting new data for it.

**To remove:** Open the three-dot menu (⋮) next to the URL and select the delete option. Confirm the deletion when prompted.

{% hint style="info" %}
**URL limit.** The number of application URLs available depends on the contract. If you reach the limit, contact the [customer value team](/support/scope-of-customer-value-services.md) to discuss options.
{% endhint %}

## How application URLs interact with analytics

HEART activates on every application URL in the list, including URLs matched by a wildcard. Adding a wildcard such as `*.example.com` activates analytics for all matching subdomains without adding each one individually.

## Troubleshooting

<table><thead><tr><th width="231.1146240234375">Symptom</th><th>Cause</th><th>Resolution</th></tr></thead><tbody><tr><td>Userlane does not appear on the page</td><td>The domain is not in the application URL list, or the URL is inactive</td><td>Add the domain or switch on the <strong>Active</strong> toggle in <strong>Settings</strong> > <strong>Application URLs</strong></td></tr><tr><td>The Editor does not open</td><td>A wildcard URL is being used</td><td>Open the Editor from a specific, non-wildcard URL that is in the list</td></tr><tr><td>HEART data is missing for a subdomain</td><td>The subdomain is not covered by an exact or wildcard entry</td><td>Add a wildcard (for example, <code>*.example.com</code>) or add the specific subdomain</td></tr><tr><td>URL was just added but Userlane does not appear</td><td>The browser extension refreshes its URL list once per hour</td><td>Wait up to 60 minutes, or restart the browser to force a refresh</td></tr></tbody></table>

## Relevant articles

{% content-ref url="/pages/ZbAA5aBZMukn2qqLRZji" %}
[Roll out the extension](/deployment/rollout/roll-out-the-extention.md)
{% endcontent-ref %}

{% content-ref url="/pages/SRW9iMERFNl0SSjAfJnd" %}
[Environment prerequisites](/deployment/rollout/environment-prerequisites.md)
{% endcontent-ref %}

{% content-ref url="/pages/FRU06enU3lsRJrh5njNu" %}
[Troubleshoot the extension](/deployment/rollout/roll-out-the-extention/troubleshoot-the-extension.md)
{% endcontent-ref %}

{% content-ref url="/pages/brm1JWKM3yHqhKU1n5G2" %}
[A tour of the Editor](/assistance/a-tour-of-the-editor.md)
{% endcontent-ref %}

## FAQ

<details>

<summary>Is there a limit to how many application URLs can be added?</summary>

The number of application URLs available depends on the contract. Contact the customer value team if you reach the limit.

</details>

<details>

<summary>Can a wildcard URL be set as the default?</summary>

No. The default URL must be a specific domain, not a wildcard pattern. The default controls the redirect target for the **Open Application** button and shared guide links.

</details>

<details>

<summary>Does disabling a URL delete analytics data?</summary>

No. Disabling a URL stops the browser extension from activating and stops new HEART data collection for that domain. Existing analytics data is not deleted.

</details>

<details>

<summary>What happens if no application URL is set?</summary>

The browser extension does not activate, the Editor does not open, and HEART does not collect data. Userlane prompts for a URL during account creation and when you open the Editor for the first time.

</details>

[^1]: The Editor is the workspace where Userlane content is built, separate from the portal where content is targeted and analytics are viewed.

[^2]: HEART is Userlane's five-dimension model for scoring how well an application works for the people using it, on a scale of 0 to 100.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.userlane.com/getting-started/first-steps-in-the-portal/set-up-the-application-url.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.