We just released an upgrade to our Page Visit trigger that gives you more flexibility when targeting surveys inside your web app.
Previously, matching was always done using the absolute URL of a page. This worked well in many cases, but became limiting when deploying Refiner across multiple sub-domains or environments.
You can now configure Page Visit triggers using relative URL paths. This makes it much easier to set up consistent targeting rules across different sub-domains, staging environments, or internationalized sites – without having to maintain multiple absolute URLs.
Relative URLs work with all existing match operators:
- Equals
- Contains
- Starts with
- Pattern match
This update brings more flexibility and cleaner configurations, especially for teams managing complex app structures.