Enquisite Update - Secure Tracking Update
No Responses since May 14th, 2007
Later this week we’re making an important update to the way we gather data. I’ve emailed everyone affected (anyone hosting the tracking script on secure / https: / ssl pages), but thought I would also make a note here. If anyone ever searches our site for the information, it’ll be easy to find.
For the last few months we’ve been working very hard at putting together a framework & architecture to support all the great user requests which we have received. One of the issues we recognized a long time ago was that we would need to migrate to a massively distributed logging system to permit us to record all the information required to generate user reports. We’re there now.
What this means is that if you’re located in NYC, Hong Kong, London, or Rio, our logging system will be the fastest item loading on your site. This will guarantee that we can provide the absolute best reporting possible (no transactions will be lost due to network error outside our control), at unrivaled speeds. We’re excited.
The changes involved in this migration also will permit us to roll-out a lot of cool new features. Just watch us over the next couple of months!
Anyhow, here’s the important technical part for anyone tracking search referrals on the https: sections of your site. If you’ve been using Enquisite on your secure pages, your code (within the javascript) appeared as follows:
“https://log.enquisite.com/log.js?id=siteid”
Now, you’ll want to use the following syntax:
“https://logssl.enquisite.com/log.js?id=siteid”
A minor change, but a world of difference.