Starting in November we noticed that our click rate had skyrocketed to 25%. Come to find out that isn't the case - that somehow Constant Contact is recording a click because some email servers trigger the first URL in our email (which is our company website). We knew that the open reporting is not accurate because some servers record an open when it isn't actually opened. Now the click reporting isn't accurate because some servers record a click when it isn't actually clicked. This makes it almost impossible to track to opened or clicked on newsletters. I have to filter out all of the contacts who "clicked" once on our newsletter because they probably didn't. The ones who actually did will never be contacted or marketing to further.
This is a huge drawback to Constant Contacts value to us. Is there a workaround to this? Do I put a fake URL as the first link in our newsletter? I need some help to resolve this issue please.
I can absolutely understand the want to have that reporting be as accurate as possible. You're correct that some server-side programs can cause false-click reports. The most common program type is server-side security programs. Those programs actually do open the email, follow the links, etc. The problem is that our system is unable to tell the difference between a click from an automated system, or a click from the recipient. There's no real work-around for this kind of problem though, and no way for us to bypass their server security.
We are absolutely tracking requests for us to find a workaround for this solution, though as I'm unaware of one in existence anywhere else, it would need to be custom built, and need to function across numerous email clients and their security programs. It will likely be some time before anyone is able to develop and deploy a solution.
Why doesn't CC set up an algorhym to analyze this when results are received? (recipients opening at the exact time it's sent, opening ALL links at the same time, etc). If our eyes can see this problem, why can't your analytics????
That's likely the solution that will need to be implemented. We do have a feature request in to our development team for a solution. I'll add you to the list of people requesting this as well. The more people that make a request like this, the higher priority it becomes for our development team.
Are we any closer to a solution for this? I just spoke with customer service and was told there is no timeline for when this will be solved.
You are correct, at this time we do not have a timeline when this experience will be resolved. I apologize for any inconvenience this may cause. There are many factors that are used to decide what is added to or updated in our product which can cause us to sometimes not have a timeline for when a feature will be available. Though this may be the case, this feature request has been tracked in your account. You will be notified directly when something like this becomes available. Please let us know if there is anything else we can assist with in the meantime.