In case anyone else is interested in the subject, here's a follow up... A few days ago I received an email from Alexander - a Client Support Supervisor at CCBill:
Quote:
Good Afternoon,
My name is Alexander and I'm a Supervisor here in CCBill's Client Support Department. I'm contacting you today in regards to your concerns on Google Analytics.
As you are already aware, from what you have stated in your GFY post, our system does not currently function with the "Asyncronus" method in Google Analytics. The reason for this is that CCBill has chosen to support what is called the "Traditional" method. While this method does have many benefits, unfortunately, one of the negatives however, is that we cannot support multiple domain tracking code.
Our system does support custom code through Custom Forms. However we're unable to reference external Javascript on our payment forms as it is a security risk to consumer information. This feature is more intended on visual modification to the layout of the form.
At this time I'm not able to find any projects with our Programming Department that would indicate we're moving ahead with supporting additional functionality from Google Analytics.
I apologize for not having an option available to you to resolve this specific matter.
Regards,
Alexander
|
I guess it's difficult to be satisfied with that kind of answer... I sometimes find there is so much inertia with what seems to be basic implementations at CCBill. Being able to track multiple domains, especially from the paysite to the payment processor, seems like the most useful purpose of having the Google snippet on the CCBill forms. It is even more incomprehensible to refuse to change GA Asynchronous snippet on a case to case basis because it represents "a security risk to consumer information". I believe the Google Asynchronous script is not that different from the traditional one and it could easily be reviewed by CCBill's programmers. Yet, as they state it,
they don't believe they'll be moving ahead with supporting additional functionality from Google Analytics, not even on case by case. It's a bit of a disapointment.