Dear Intercom team,
We would like to request the ability to use regular expressions when creating outbound communication campaigns, targeting audience by Current Page URL in outbound messages.
At the moment, Current Page URL targeting only supports filters such as is, contains, starts with etc..
This creates limitations when:
-
URLs contain dynamic numeric IDs
-
We need to target a specific range of IDs
-
We want pattern-based targeting without creating multiple OR conditions
-
We want to avoid engineering workarounds (e.g., custom attributes)
For example, we want to target only a specific subset of courses on our Learning Management System (e.g., courses with ids between 123 and 153), but since Current Page URL is a string, without regex, or, the ability to treat IDs in URLs as Numbers allowing us to use comparison operators on URLs, this becomes difficult or requires engineering changes, especially if we are running tens of courses on our platform.
The difficulty in this scenario is also that we cannot afford to just target all courses (e.g. contains /courses/), since many of them would have been concluded (students graduated) or many of them would have just started (i.e. we may not want to send communication to them just yet).
We could see a benefit for having Regex functionality in:
-
LMS and similar platforms with course IDs
-
E-commerce and other platforms with product IDs
-
SaaS apps with resource-specific URLs
Adding Regex support would:
-
Reduce dependency for segmentation and custom attributes. Custom attributes is one solution to this situation, but which would require some engineering work to ensure correct and efficient update custom attributes without creating too much overhead, especially if there are limits on how many times can a custom attribute be updated over a given period of time.
-
Enable more precise targeting
-
Reduce campaign setup complexity (e.g. in above scenario, we would need to manually set up tens of outbound rules to make it work for a specific range of IDs, which would soon become unsustainable if the number of products and product categories grows in the future.
-
Prevent potential errors from large OR-based rule sets
To reference our example from above, if we wanted to target course URLs with IDs ranging between 123 and 153 (inclusive), with regex we could e.g. implement a rule targeting /courses/(12[3-9]|1[3-4][0-9]|15[0-3])
We believe adding regex support to Current Page URL filters would significantly improve targeting flexibility for dynamic web applications and reduce reliance on engineering workarounds as well as custom attributes.
Thank you very much for consideration.