Wildcard for triggers
I would love to send a trigger to all users doing a search on my site. However, this is not possible, as each search generates a URL with the search term in it. Other chat services offer wildcards, so I could enter the URL as http://beta.vraagalex.nl/?action=search&page_id=6&dosrch=1&q=*, where * can be replaced with any value.
To All Our Valued Users,
Thank you for choosing tawk.to and for reaching out.
Our Advanced Trigger includes an option to fire a message based on a Visitor’s search term.
Other conditions for firing a trigger may include Visitor Name, referrer, and search engine.
Learn more about advanced triggers here: https://help.tawk.to/article/advanced-triggers
Vageta San commented
While playing, have these few things in mind. Let's put an end to this discussion by telling the truth. The finest thing one can do is work on oneself while having pleasure. https://wordle-unlimited.online/
Please, this is so important, when users come from Facebook Ads triggers are not firing
not implemented yet? OMFG
This would be very beneficial. I want a trigger that fires on all pages as my customers land on 100s of different landing pages for our products.
I don't understand why this is not yet available... It's a very usefull feature and easy to implement.
please have this enabled, should not be too complicated :-/
I can't believe that this still isn't available. Triggers are almost unusable without this basic functionality.
While you are at it, allow the "page title" to be case insensitive.
Wildcard support for the url in the Page Notification trigger. Any plan for that? I can see that more users had this idea. I give here my 2c
David Watkinson commented
I have been waiting for this feature and found that has now been added, but not as a wildcard. It is an advanced trigger. Some of the items such as page title didnt work for me, but this is the config I used to get it to work.
It uses conditions instead of wildcards. I hope this helps everyone who had the same issue as me.
The initial problem I had was that visitors who arrived via AdWords (or similar) had a query at the end of the URL which caused the normal trigger to fail.
Visit Admin, Triggers and click on Add Trigger
Under Conditions, I added:
"still on page" 10 seconds
"Visitor page url" contains my-special-page
(you can add another conditions if there are other similar urls where you do not want the trigger to action and set it to "does not contain" such as "my-special-page-2)
I then added the agent name and message. Tested and all worked.
Chris Todd commented
Yes please add this feature!!! :)
Felipe Maurer commented
Allow triggers to trigger based on url variables. So for example domain.com/checkout?showErrors=True would be the url for the checkout process when the user encountered an error while checking out.
Tiago Siebler commented
Right now you can only provide an absolute URL for a trigger, for example if I want a trigger to happen after a customer spends more than 3 minutes sitting on this page:
It won't trigger on this page:
In reality, it would help if we can define partial matches like this:
If user visits via Adwords advert, url includes ?glic=*** at the end of url and trigger does not work. Allowing a wildcard or query at the end of the url would be great.
Yep, me too. This is a killer feature. For many of my sites this would put tawk.to out of the running completely. Just too labour intensive to have to define 1,000s of urls.
trigger in a shopping cart section where the url is random, because of the last digits. example: checkout/1234 trigger suggestion will be: checkout/*
Ismael Briasco commented
Yes please add this feature!!! :)
Ashish Patel commented
There should be a parameterized trigger for page like http://mywebsite.com/submit-job/?order_id=%%NUMBER%%&job_id=%%NUMBER%%&step=4
So that visitors can see chat pop notification when a user stuck at checkout page in a shopping site.
This way we can preserve the url and %%NUMBER%% indicates there can be any valid integer number.
There have been other posts about wildcards for triggers, but they're referring to Visitor Page URL. I'm referring to the Advanced. I'm trying to filter swear words, but there's a few bumps in the road. It triggers words such as "assassinate". Also, I was going to make a trigger for "Hi", but it triggers words such as "high" and "hit". A wildcard for these could fix this. If this would take too much time in development, an alternative could be to add a "do not trigger" option, and it'd be our responsibility to find those words to not trigger. This isn't as easy for us, but it's not impossible, and it may be easier to implement. Hopefully this gets noticed.
This is very useful also when you have the same category string in the url on thousands of products. You can't certainly enter each url singularly
Need to be able to use wildcard for Trigger Visitor page url e.g. www.site.com/support/* so that the trigger will work on any page visited rather than the need to set-up separate triggers for each/every page