109 D
Comments
-
Hi Brian, Thanks for sharing that. We've continued tracking data from a few client sites. Since 9/13/22, we've tracked visits from 16,435 distinct IP addresses where Callrail was not blocked (the "...
-
Thanks Adam! I've enjoyed the opportunity to explore this problem, and have learned quite a bit in the process. This was an immensely satisfying solve. We've rolled this out to four client sites (a...
-
Hi Adam, Last week, our proxied requests started failing. I was able to resolve the underlying DNS-related issue with some help from Stackoverflow, and everything is working again. The filename ran...
-
Thank you Adam! I attended the event in Tampa this Wednesday, and had the chance to demo this for some of the team. That was awesome, I really appreciate the opportunity. We're currently implementi...
-
I'm thrilled to say that after experimenting with some different approaches to this problem, we've come up with something much more effective than CNAME cloaking. While my primary concern was dynam...
-
Hi Elliot, thanks for the thoughtful response! I really appreciate the attention to this issue. There's a case to be made that CallRail domains should be removed from these adblocker lists because...
-
Thanks Adam! This is a critical need, it sounds like things are going to progress slowly. I'm talking to my devs about some additional approaches. I'd like to beta test on some client sites and the...
-
Hi Adam, thanks for your reply! I'm thrilled to hear that CallRail is exploring this increasingly important issue. Aside from the increased tracked call volume - this sort of feature is something t...