Use URL allow and block lists to control where your Brightcall Speed To Lead™ widget can appear. You can match a specific page, a section of your website, or use a regular expression for more advanced rules.
URL(s) Allow List
When the allow list contains rules, a page must match at least one of them for the widget to be eligible to appear. If the allow list has no entries, it does not restrict pages. Other widget settings can still prevent the widget from appearing.
Log in to the Brightcall Dashboard at https://app.brightcall.ai/.
Open Speed To Lead™ → Widgets and select the widget you want to configure.
On the Main tab, turn on Show advanced settings.
Turn on Show advanced settings on the Main tab.
Find URL(s) Allow List.
URL(s) Allow List and URL(s) Block List controls.
Select a match type and enter the URL or pattern. To allow one specific page, select Exactly equals and enter https://example.com/contact. Replace example.com with your website’s domain.
Click Add. Add each additional rule separately. For example, add another Exactly equals rule for https://example.com/pricing.
Two separate Exactly equals rules in the allow list.
Click Save to save the widget. Check a page that should be allowed and a page that should be excluded.
If a page uses a subwidget, configure the URL lists in that subwidget. The parent widget’s lists do not apply to subwidgets.
To change an existing rule, click its pencil icon, select the matching mode and enter the new value, click Update, then click Save. To remove a rule, click its × button and then Save. Replace or remove an incorrect old rule rather than adding another rule alongside it.
URL(s) Block List
Use the block list to exclude pages. The block list is checked after the allow list: a page that matches a block rule is excluded even if it also matches an allow rule.
Open the widget’s Main tab and turn on Show advanced settings.
Find URL(s) Block List.
Select a match type and enter the URL or pattern. To exclude one specific page, select Exactly equals and enter https://example.com/pricing. Replace example.com with your website’s domain.
Click Add. Add each additional rule separately. For example, add another Exactly equals rule for https://example.com/checkout.
Block-list rules exclude /pricing and /checkout, even if an allow rule matches.
Click Save to save the widget. Check a blocked page and a page that should remain eligible to display the widget.
If a page uses a subwidget, configure the block list in that subwidget.
Choose a matching mode
Choose the matching mode before entering a value. The default mode is Contains, which treats your input as literal text.
Purpose | Matching mode | Value |
One specific page | Exactly equals |
|
The /blog/ section and its subpages | Starts with |
|
All pages | Regular expression |
|
The /blog/ section using a regular expression | Regular expression |
|
These are alternative examples. Choose the rule for your intended result. Do not add the all-pages rule .* alongside rules intended to restrict the allow list to specific pages or sections: a page only needs to match one allow rule. The same editing and removal steps apply to the block list.
Replace example.com with your website’s domain. Use the same protocol, hostname and path as the pages you want to match. For the rules shown above, enter the page address without query parameters (the part after ?) or a fragment (the part after #). These examples match the protocol, hostname and path; tracking parameters and fragments do not change the result. Exactly equals distinguishes /contact from /contact/, and paths are case-sensitive. The /blog/ prefix includes /blog/ and its subpages, but does not include /blog without the final slash.
Alternative allow-list example. The block-list rules shown below still exclude /pricing and /checkout.
A standalone * is not a valid regular expression. To match all pages, select Regular expression and enter .* (a dot followed by an asterisk). Entering .* in Contains mode searches for the literal characters instead.
Alternative allow-list example. The block-list rules shown below still exclude /pricing and /checkout.
These matching modes work in both lists. An allow rule makes a matching page eligible to display the widget; a block rule excludes it. To display the widget on all pages except specific exclusions, you can leave the allow list without entries and add the exclusions to the block list.
Test your rule
Before adding a rule, click Test. For the Starts with rule https://example.com/blog/:
https://example.com/blog/post should return Match found.
The /blog/post address returns Match found.
https://example.com/blogger/post should return No match found.
The /blogger/post address returns No match found.
Use page URLs without query parameters or fragments for these examples. The Test dialog checks the URL text you enter as-is; it does not remove query parameters or fragments. For example, an Exactly equals rule for https://example.com/contact matches that page in the widget even when a tracking parameter is present, but entering the full address with that parameter in Test will show No match found. The dialog does not check the entire widget configuration. After adding your rules and clicking Save, reload the actual pages and check the widget.
Websites without full page reloads
If your website changes pages without a full browser reload, open the widget’s Behavior tab and turn on Support single-page application so URL rules can be checked again when the page path changes.
If visitors can start on an excluded page and then navigate to an allowed page without reloading, also turn on Support single-page application works on pages where widget disabled. Keep both settings enabled for that scenario.
Click Save, reload the website, and test navigation in both directions: from an allowed page to a blocked page and from a blocked page to an allowed page. Also test opening a blocked page first, then navigating to an allowed page without reloading. Allow a few seconds after each navigation for the widget to update.
The automatic page-change check detects changes to the page path. Changes only to query parameters or the fragment after # do not trigger it. The URL examples in this article do not distinguish routes that differ only after #. If your website uses that kind of routing, contact support to review the integration.
If you need help setting up URL allow or block lists, contact our support team at [email protected].