Hi Guys,
I’m new to Tawk.to, and wanted to ask a question about a potential use case we’re considering. We’ve developed a click tracking app to monitor ppc campaigns for authenticity - to help weed out fake clicks from bots or other malicious users. A big component of this is what we gather from URL customer attributes we gather from the ad servers like the click id - so if someone clicks on a ppc ad, the url they’d be sent to would be something like https://ad-domain.com/?click_id=123¶m_1=456…
From there we issue various challenges. For instance, if we recognize the url is populated with the click_id parameters, we might want to automatically pop the tawk.to widget to ask the visitor if they need assistance or some other challenge that helps prove the visitor is a live user and not a bot.
In the past, we’ve used our own custom script and our own web socket connection to gather this data and dump it into our databases.
I believe incorporating our tracking script alongside tawk.to’s chat functionality would appeal to a lot of our customers that may not only want to confirm a ppc click is legit, but also see if they can quickly assist any legitimate visitor. I’m wondering if we should try to combine our script with the tawk.to script because it looks like tawk.to already gathers many of the parameters we’re insterested - like for instance the referring url that contains all the url custom parameters? I’ve only just started playing around with the javascript API and webhooks, though I’m not sure if developing things to track and communicate with an external api like ours was the intention of such funcationality in tawk.to?
Was looking for advise - would it be best to keep our tracking script separate or try to combine it w/ tawk.to’s widget?