Use a Page Source Trigger to specify content in the source code on the page you want to match. SiteSpect can match any content on a page, including HTML doctype, head, and body sections. Use this condition when multiple pages share the same URL or when content is not always present on a page.
For example, if each stage of the checkout process uses the same URL (e.g., /checkout.asp) but you want to match only the final stage that includes the page title "Confirm Order," use the following combination of Triggers:
A URL Trigger set to:
^/checkout\.asp
AND
A Page Source Trigger set to:
<title>Confirm Order</title>
For the best regex performance, use the Page Source Trigger in conjunction with the other Triggers. The Page Source Trigger is evaluated last and only if the other conditions successfully match.
Matching Options
SiteSpect offers several matching options to help refine your trigger definition. The entire list of Page Source Trigger options looks like this:
- Exactly ("Equals" in SuperFresh)
- Does not match exactly ("Doesn't equal" in SuperFresh)
- Contains
- Does not contain
- Starts with
- Does not start with
- Ends with
- Does not end with
- Regex
- Does not match regex
For legacy component types that do not have matching options, such as Global changes and Factors, prefix the Page Source Trigger with an exclamation mark (!) to match when the specified text is not found on a page.
For example, to match pages that do not contain "Welcome back," use:
!Welcome back
Note: This is not regex syntax. SiteSpect supports regex only in certain fields.