You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible the pass the keywords entered into the quicksearch into the url hash, so we can track in GA etc what terms users are entering?
We are filtering content with a search field and button filters, and passing the button filters to create a URL hash. However, I cannot figure if its even possible to do the same with the quicksearch filter. Would I have to create a submit button to the input that passes whatever query term is entered into a hash?
@ksascomm — your debug expired, but regardless, i'm pretty sure you can do this with just a listener through GA without having to attach it through a hash. it's been awhile since i've done this so i can't make the best recommendation on exactly how to do it, but i'm pretty sure it's possible.
if you did want to do it via hash—and without a submit button—i suppose you could set some kind of debounce listener on the keyup listener (sort of how it's configured now, but perhaps with different settings as needed) that attaches the hash. i would probably go the route of the first one though, assuming it's possible.
Is it possible the pass the keywords entered into the quicksearch into the url hash, so we can track in GA etc what terms users are entering?
We are filtering content with a search field and button filters, and passing the button filters to create a URL hash. However, I cannot figure if its even possible to do the same with the quicksearch filter. Would I have to create a submit button to the input that passes whatever query term is entered into a hash?
codepen: https://codepen.io/ksascomm/pen/OJKVPWy
debug: https://cdpn.io/pen/debug/OJKVPWy?authentication_hash=vWkRwpWQZOnM#filter=*
The text was updated successfully, but these errors were encountered: