For the complete documentation index, see llms.txt. This page is also available as Markdown.

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 does not open, and HEART does not collect data. Add every domain where Userlane should run.

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.

1

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.

Application Settings menu in the portal with Application URLs selected
Application URLs sits under Application Settings.
2

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.

3

Confirm the URL appears in the list

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

Application URLs list showing a newly added URL with the Active toggle switched on
A new URL is active as soon as you save it.

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

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.

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.

1

Open application URL settings

Select Settings at the bottom of the left sidebar, then select Application URLs under Application Settings.

2

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.

Animation of hovering over an application URL and setting it as the default
Hover over a URL to set it as the default.

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.

URL limit. The number of application URLs available depends on the contract. If you reach the limit, contact the customer value team to discuss options.

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

Symptom
Cause
Resolution

Userlane does not appear on the page

The domain is not in the application URL list, or the URL is inactive

Add the domain or switch on the Active toggle in Settings > Application URLs

The Editor does not open

A wildcard URL is being used

Open the Editor from a specific, non-wildcard URL that is in the list

HEART data is missing for a subdomain

The subdomain is not covered by an exact or wildcard entry

Add a wildcard (for example, *.example.com) or add the specific subdomain

URL was just added but Userlane does not appear

The browser extension refreshes its URL list once per hour

Wait up to 60 minutes, or restart the browser to force a refresh

Relevant articles

Roll out the extensionEnvironment prerequisitesTroubleshoot the extensionA tour of the Editor

FAQ

Is there a limit to how many application URLs can be added?

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

Can a wildcard URL be set as the default?

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.

Does disabling a URL delete analytics data?

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.

What happens if no application URL is set?

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.

Last updated

Was this helpful?