Category: Web Development

The web hosting I am using is ICDSoft, but from time to time I will help people setting up website using other web hosting base on their requirement and the budget they can afford.

ICDSoft is very famous in her stable services as well as their extreme helpful support (Suresupport). And I never find them so helpful once I started using some other web hosting, namely, GoDaddy and Hostgator.

Hostgator comes to my eye-sight because of they open China market when I search for economic China web hosting. It does not cost much, but their admin panel is quite messy, and their support is also not fast enough in catering my inquiry. However, it is much better than GoDaddy.

GoDaddy is very famous in their domain sale, she often provides very cheap domain sale. But it also famous in their un-user-friendly admin panel, complicated control of your account. You are not only fail in using username to login your admin panel (you have to use the customer ID). And recently when I help my friend setup the Delux web hosting plan, it almost turns me crazy during the email setup. Therefore I seek for their online support.

After looking up the whole website, GoDaddy only provide Live chat or call-in support. There is no email support or online support ticket system for firing support ticket. I turn out opening the Live chat window and see the screen:

It turns out I waited an hour for a support expert to chat with me. And before I reach the expert, I already sort out the issue by surfing from the Internet.

To know that, [email protected] no longer work:

And this is really poor to me, as I often wish to share screen or text file for resolving issue, and GoDaddy turns me down really deeply.

Well, my friends look for economic approach, I can only try harder to help them by myself.

I assume you have a rough idea what Google Tag Manager (GTM) is, if not, you may either read its official website, or watch the nice Introduction Video to get the brief idea.

Once you have a brief idea of it, it sounds like ‘Yeah! That is our choice and we need it to empower our marketing / site tracking strength and management.’ by marketer, or ‘Gosh! We have to implement it in order to off-load the work of various tag setup from IT Team to Marketing Team’ by I.T. Tech. I am a front-end web developer and often need to make suggestion / decision to confirm whether to go for an approach, and Google’s product often a nice choice to have, but probably not this time when I am writing this blog.

Somewhere over the WWW have people like blogger / SEO expert introducing GTM by coping / elaborating its good point (mostly the good points that mentioned by Google Tag Manager official website). But when you come to the analysis phase, you will find it lack of detail documentation to implement it when you need it a bit more advance.

My case is to start preparing the migration of Google Analytic (ga,js) to Google Universal Analytics (analytics.js) for my company’s E-Store, and I have no difficulty to setup the Containers, Tags, Firing Rules, Marcos for general site tracking using Google Universal Analytics tracking type. I can see the configuration I did in GTM start populating data to various report, mostly similar with what I can see in existing Google Analytics profile. However, for some case we need to have different tracking code with different value per several different page, then the problem I face is the grow of Firing rule. And the worse thing is, all the rules / tag are listed linear, without folder structure for organization.

Furthermore, leverage the tracking code deployment task from IT team to marketing team is not an ideal way in terms of site stability. If there is bug in tracking code and is being deployed without proper testing, the site will subject to the issue and the IT department often be the party who being blaming by site user instead of the marketing team.

I would advise IT team to implement Google Tag Manager to their website, and use it as a way to simplify their tracking code deployment, and keeping the account secret from non-IT team member, so as to avoid them from introducing issue to the site.