Allow us to Include or Exclude specific pages with Wildcard URLs
In wordpress, the plugin only allows you include/exclude the widget on a specific page, which is nice.. but if you want to exclude an entire site directory, you should be able to do so as well. For example:
website.com/help/*
vs
website.com/help/user
website.com/help/employee
website.com/help/developer
etc...
This is useful because it's a less specific rule, and if you add a page under /help/* it will still follow the rule, rather than having to manually add it to the list.
It also makes those lists far shorter.
yusareba
shared this idea
-
Jonathan
commented
This is a brilliant idea, I'd like to show a specific chat message on any page that has the phrase "checkout" or "offer" on it, for example.
-
Martin G. Blendinger
commented
We need use wildcard in trigger url too, cause we have the site in multiple languages, so I want a trigger for all pages www.domain.com/*/service1
-
Anonymous
commented
ISSUE: Currently a trigger is only url fired when a the url is exactly as provided by the admin, but should fire if unknown parameters are appended.
SCENARIO CASE: When a user comes to the trigger url page from say an advertisement on google, the landing page, or trigger url, is appended with tracking and conversion parameters causing the trigger to never be fired.
IMPROVEMENT IDEA OPTIONS:
1. Provide option (checkbox) to filter url params out if they exist from URL.
2. Filter out params entirely as if they do not exist
3. Allow wildcard /* in the url to accept any params as they fall under the already provided trigger URL.
ANYONE ELSE HAVE options or suggestion that can help get their dev team to iterate on this option in an upcoming sprint or deployment?
-
Anonymous
commented
In wordpress, the plugin only allows you include/exclude the widget on a specific page, which is nice. But, what if I want to exclude an entire site directory? For example:
Excluding this - https://www.elkeesdeals.com/blog/*
should also exclude all pages starting with /blog/ slug.
https://www.elkeesdeals.com/blog/category/tips
https://www.elkeesdeals.com/blog/employee
https://www.elkeesdeals.com/blog/postname.html
etc...This is useful because it's a less specific rule. if i add a page under /help/* it will still follow the rule, rather than having to manually add it to the list.
Please help me how to achieve this because https://www.elkeesdeals.com/blog/* is not working on my site.
-
Anonymous
commented
I just came across this suggestion thread from looking for a solution to the issue you have brought up. Wildcard exclusion should certainly be a feature of the application.
-
Raido
commented
Second that.
In our case we wanted to hide the chat widget on specific pages.
But those specific pages are also reached by ads (Google AdWords). AdWords will automatically add dynamic parts to the URL and this causes exclude pattern to fail.