RB2B users can fine-tune the pages on which they wish RB2B to identify visitors using our URL restrictions feature.
How URL Stubs Work for Matching
When defining URL stubs to include or exclude pages, the behavior depends on the length of the stub:
URL stubs longer than 3 characters are treated as "includes." This means that any page whose URL contains the specified stub will be considered a match.
Example: Using/blog
as a stub will match/blog
,/blog/article-title
,/blog/category/tech
, etc.URL stubs with 3 characters or fewer are treated as exact matches. In this case, the system looks for URLs that match the stub exactly, with no partial matching.
Example: Using/
will only match the homepage (/
) and not other paths like/home
or/about
.
This distinction allows for precise or broad targeting of pages based on your goals.
Use shorter stubs for pinpoint accuracy and longer ones for more inclusive matching.
Limitations
The total number of URL restrictions that can be added to an account is 100.
URL extensions like .html, .php, etc. cannot be added to the URL restrictions tool.
Setting Up URL Restrictions
There are two methods available:
Method 1: "RB2B will trigger on all pages, except the URLs listed below"
The "RB2B will trigger on all pages, except the URLs listed below" setting will enable RB2B to run on all pages on which it is installed but it will not identify visitors on the defined pages.
To add pages to be ignored, type their relative URL (ex: /careers) and then hit enter to add it to the list. Once happy with your changes, click the "Save" button.
To remove URLs from the list, click the X that appears to the right of the URL then click "Save."
To allow RB2B to run on all pages on which you have installed the script, remove all URLs from the list and click "Save."
ℹ️ Note: URLs on subdomains are entered as relative URLs.
Method 2: "RB2B will only trigger on the URLs listed below"
The "RB2B will only trigger on the URLs listed below" setting will prevent RB2B from identifying visitors on all pages on which it is installed except for those defined.
To add pages that you wish to allow RB2B to run on, type their relative URL (ex: /careers) and then hit enter to add it to the list. Once happy with your changes, click the "Save" button.
To remove URLs from the list, click the X that appears to the right of the URL then click "Save."
This field cannot be left blank.
ℹ️ Note: URLs on subdomains are entered as relative URLs.
Best Practices
Using URL Restrictions on Multiple Domains/Subdomains
The URL Restrictions tool applies path-based rules and does not distinguish between different domains or subdomains. This means that if you set a restriction for /careers
, it will apply to:
https://domain.com/careers
https://subdomain.domain.com/careers
In other words, the tool treats all matching paths equally across any domain or subdomain where the RB2B script is installed. If more granular control is needed—such as limiting entries to a specific subdomain—you’ll need to implement custom logic outside of the built-in URL Restrictions feature.
Preventing RB2B from Tracking an Entire Subdomain
To stop RB2B from tracking visitors on a specific subdomain, simply do not install the RB2B tracking script on that subdomain. RB2B only identifies visitors on domains or subdomains where the script is actively installed. If the script isn’t present, no tracking or identification will occur.
Troubleshooting
After adding a URL, it disappears
Possible Reason
If a URL disappears after being added to the URL Restrictions tool, it was likely entered in an invalid format. Only URL stubs like /page
are accepted—full URLs such as https://domain.com/page
will be rejected.
Possible Reason
If a URL disappears after being added to the URL Restrictions tool, it could be because the slug has too many characters. Each entry has a maximum character length of 80 characters. If length is an issue, consider removing a URL segment or two from the beginning of the slug.