Requirement | Configuration |
Run the test only on product pages | Include /products/ |
Run the test on all product pages except one | Include /products/ + exclude the specific URL |
Run the test across a section of your website | Include the relevant URL path |
Prevent specific pages from participating | Add an exclusion condition |
Match type | What it does | Example | When to use |
Domain | Targets webpages within a specific domain | example.com | When you want to target pages across a domain |
Simple URL Match | Matches the URL based on the standard URL structure | example.com/pricing | For common URL targeting requirements |
Exact Match | Matches only the specified URL | example.com/pricing | When you want to test one specific webpage |
URL Pattern Matches With | Matches URLs that follow a specific pattern | example.com/products/* | When multiple pages follow a similar URL structure |
URL Regex Matches With | Matches URLs using a regular expression | example.com/products/.* | For complex URL structures |
URL Contains | Matches URLs containing a specific value | /products/ | When the URL contains a common path or term |
URL Starts With | Matches URLs beginning with a specified value | example.com/products/ | When you want to target a section or group of pages |
URL Ends With | Matches URLs ending with a specified value | .html | When pages share a common URL end |
Do | Avoid |
Use Exact Match for a single webpage | Using broad conditions for a single page |
Use Starts With for predictable URL paths | Creating individual rules unnecessarily |
Use patterns for groups of similar pages | Using complex regex when a simpler match works |
Add exclusions for pages that shouldn't participate | Assuming a broad rule will exclude unwanted pages |
Preview your targeting before launch | Launching without verifying the targeted URLs |
Tip: Choose the simplest URL match type that accurately targets the webpages you want to test.