Google Analytics E-commerce tracking
It would be nice to support Google Analytics E-commerce tracking in Kentico https://developers.google.com/analytics/devguides/collection/gajs/gaTrackingEcommerce
This support was delivered in version 11.
E-commerce and Platform Product Owner
As already mentioned below by others, using GTM to get a lot of this tracking information is a good way to do this. We have worked around many of the issues by using GTM instead. It hasn't been easy, but has meant we've been able to get eCommerce tracking working reasonably well.
Thomas Golatta commented
my collegue from Digital Marketing - David - gave me this answer, hope it is helpfull:
As the library mentioned in the ticket is no longer supported by google analytics I would suggest to follow the implementation guidelines for the google tag manager which is the preferred method of implementing Universal Analytics.
For this you should refer to https://developers.google.com/tag-manager/enhanced-ecommerce
I would suggest to always fill the dataLayer Object with the basic information for a product as detailed here:
'name': 'Triblend Android T-Shirt', // Name or ID is required.
'id': '12345', // SKU
'list': 'Search Results', // Optional, only for search results or product listings, counted form top left to bottom right
'position': 1 // Optional List position
To make this configurable as originally intended all you need to allow is that the GTM Container is supplied with an ID in the format of GTM-XXXXX. I would always implement enhanced ecommerce so the customer can later easily move from standard to enhanced tracking. Additional data is simply ignored by Google Analytics.
If the Kentico-Customer whishes to use the Google TagManager and supplies the system with an ID, you will need to make sure that one part of the actual snippet code is in the head of the page and the other, immediately after the opening body-tag.
I know this is challenging at present as Kentico always renders a <form> tag onto the page which is non-standard and will throw an error in the debugging of the Google Tag Manager. However, it will work nonetheless.
What e-commerce clients are looking for is usually product interaction (View, Add/Remove from cart), voucher code tracking, checkout step tracking and finally conversion tracking.
More savvy ones will want to know selected shipping supplier, payment methods used, Cart-to-detail rates (i.e. which product was looked at and purchased as opposed to just looked at).
I guess there needs to be a balance between convenience “set-it-and-forget-it” and customization of the dataLayer object for more keen developers wanting to provide more insights.
We have integrated it already through scripts and code changes.
We are interested in:
1. Checkout stages reached. To get an idea of basket abandonment and where it occurs.
2. Total Revenue.
3. Top Products.
4. Conversion Rate.
5. Average Order Value.
6. Total Transactions.
7. Promo Code Use.
8. Shopping Behaviour.
Transaction and item data would be the essentials.
Most people now use Google Tag Manager to do GA tracking, including ecommerce... would be nice to see a Kentico web part to output GTM DataLayer JSON and the GTM code in general.
GTM Datalayer could support things like product impressions, ecommerce, etc.
I've seen many suggestions being culled on this forum recently. I hope this suggestion is still under consideration, and that it may be included in an immenient release. Is there any updates that can be shared at this time?
Are there any further plans for this feature?
Is this going to be included in the Kentico 9 release that's due very soon?
After spending the last few days configuring one of our ecommerce sites tocater for Googles Enhanced Ecommerce Web Tracking I can whole heartly agree this needs to be included as an easy integration.
To be honest the hardest part is navigating the macro's to get the information you need for each page. Ask your support guys, i reckon they're sick of hearing from me.
While Kenticos analytics are ok, i'm sorry they don't come near providing all the aggregated information that Google Ecommerce Analytics provide.
If I could add 20 points to this I would.
One other thing I'd like to suggest: can this integration please include the new Google Universal Analytics, a new way to track analytics data. https://support.google.com/analytics/answer/2790010?hl=en
Thanks Petr! Happy to help with any questions.
Thank you Richard and Stephan for your detailed responses. I really appreciate it! I have added it to our product backlog, so there’s a good chance you’ll see it in the product relatively soon (but not in V8). Please stay tuned, as I will need to discuss your scenarios and integration into Kentico in more details. I expect collecting this information in March 2014. Thank you!
Richard Norris commented
My name is Richard Norris and I am one of the owners of QIS Packaging and I am following this thread of this conversation.
Stephen is exactly correct when he says that “Google Analytics is probably the most important decision making tool we have when it comes to our online store”
If I as a customer has one criticism of the Kentico CMS ( and I don’t have many ) it would be that it is Lacking what I consider to be one of the most important integrations any online shop could have …
I see this as a “mission Critical “ add on to any website and particularly for us with our online store.
I would STRONGLY urge you to consider this as critical improvement to an otherwise excellent system.
My team and I would be happy to answer any further questions that you may have regarding this. We are happy to assist in any way we can
The e-commerce tracking in Google Analytics is needed so we can not only track transactions, but also track things related to each transaction, such as the source of the visit, medium of the visit, the landing page, the operating system on the visitors device, their screen resolution, how many visits before a transaction is made, and a bunch of other valuable information.
It also allows us to easily aggregate the information into useful dimensions such as transaction per hour of day, day of week etc.
In a nutshell, this is how we track the efficiency of our marketing, including paid advertising, campaigns, and determine the ROI for these campaigns.
As a marketing tool, Google Analytics is essential for us to understand what marketing is working for us, and what marketing isn't working for us. It helps us to understand how we should be presenting content, and especially product information, on our site.
Google Analytics is probably the most important decision making tool we have when it comes to our online store, and it is the single most popular web analytics service in the world (by a huge margin). I can't help but feel that making GA e-commerce tracking a simple integration with Kentico would markedly raise the appeal of Kentico to many businesses. It would certainly make me happy. :)
Typically, the e-commerce tracking occurs when the customer lands on an order confirmation page, but I understand this currently is not possible in Kentico because of the way the shopping cart is configured (although my understanding of this is not great). That leaves programming the tracking by interacting with the GA API, which is not simple.
If you have any more questions, please let me know. I am happy to help.
Hi Stephen, thank you for your comment. Unfortunately, this will not be included in V8. Do you know about contact activity tracking for the ecommerce, e.g. "product added to cart" or "product purchased", see http://devnet.kentico.com/docs/onlinemarketingguide/cm_activites_managing_activity_types.htm?zoom_highlightsub=activity%2Btype. Would this cover your needs? Or what are the scenarios when customers need to integrate with Google analytics regarding the ecommerce? Thanks!
Is there any chance this will be included in v8 that is due to be released soon?
This is an essential feature, and I *really* hope it will be an "out-of-the-box" feature very soon.
Here is the workaround: http://www.ramto.com/blog/post/How-to-setup-Google-Analytics-Ecommerce-tracking-in-Kentico
We would like to support it out of the box in the future.