SharpSpring's wildcard URL matching feature allows you to create triggers for page visits with changing URL extensions. When you create a page visit trigger you can replace the extension parts of the URL with an asterisk (or wildcard). By adding an asterisk, you're telling SharpSpring that you want the trigger to allow that bit of the URL to be variable.
Wildcard Matching Feature Overview
Check out this example URL:
The "order-received" and "order_number" are both extensions that will change every time a customer visits the transaction page. The rest of the URL will remain the same. In this example, we can replace the "order-received" and "order_number" extensions with an asterisk. Here's how this looks in the app:
The wildcards will stop matching the extensions when they encounter any of the following boundary characters: /, ?, &, and =.
For example, http://example.com/* would match http://example.com/home but would not match http://example.com/home/john because the "/" character occurring after the word "home" would prevent the wildcard from matching that particular URL extension.
To include all variations of a URL beyond a certain point, you can utilize a double-star (**) Wildcard to indicate that any additional variations beyond the location of the Wildcard are to be included in the rule.
With the above in place, everything before the “**” will need to match, but anything after the catch-all will be ignored, unlike the single star Wildcards, which will respect boundary characters present in the URL.