Hoping for some advice please. I need to setup ecommerce tracking on my company website. Is it better to setup Enhanced e-commerce tracking for UA, or the new Google Analytics 4 setup? Struggling with pros and cons, as it appears G4 is the way forward but still missing a lot of functionality.
Any advice appreciated!
With the enhanced ecommerce of Universal Analytics you certainly know which is the optimal setup, that of GA4 may be subject to subsequent adjustments. The advice is always the same, which is to use both in parallel so that we have the data as we know it and start tracking with the new method.
Related
I have question regarding integration Google Analytics 4 into Prestashop. My company has setup some years ago Universal Analytics. Now that Google forces everyone to slowly migrate to Google Analytics 4 I was tasked to do it.
I have created GA4 property, inserted gtag into site's code and connected it to the existing UA tag on the site. Everything is working fine, user's data is here except for revenue. Do I need to manually add everywhere custom events as in this documentation? https://developers.google.com/analytics/devguides/collection/ga4/ecommerce?client_type=gtag
I know that they are Prestashop modules for this but they are paid and because of this aren't a option. Also current Google Analytics module don't support GA4
Yes, the url you posted describes ecommerce implementation through gtag. If that's what you're doing, then yes, to get revenue, products, transactions and the rest of EEC-related data, you'll have to implement it as described there.
Most of people choose to implement GA4 through GTM since it's much easier to manage and maintain there. But if the intention is to have tracking with the front-end team, then direct use of gtag may be justified.
I am going to change old analytics code into "Universal google analytics code" it affect existing Google Analytics reporting or does it just affect Adwords? (I need to remove old code from the website or both codes are needed to present in the website )
I am new to marketing please help.
Thank you.
If you replicate your old analytics implementation using the new library it will not affect reporting. I.e. if you are only collecting pageviews, then replacing one code snippet with another is 100% safe.
If there are some custom implemented scripts you will need to rewrite them using new analytics library syntax.
If you are just tracking pageviews - GTM (Google Tag Manager) is an overkill for you.
I have implemented eCommerce tracking on below domain but it seems nothing is recording so far. If anyone can check this and let me know what has gone wrong, it would be much helpful.
http://www.champacentralhotel.com/
Thanks
I'm trying to find a web site/resource that has a working demo of Google Analytics to use.
As I have no website etc to be able to link my Analytics account to, I have no way of reviewing/learning to use Google Analytics.
Is anyone aware of such a demo available to the public?
Are you're asking for is a site where you can see GA working?
Years ago I set up 3 unusual but extremely effective GA learning sites mainly for myself (so they are crude).
I still use 2 of them today with Real Time reporting and Chrome extensions dataSlayer & WASP.
They accept your own Web Property ID (UA-xxxxx.yy) and save it in a cookie so the data goes into your own account.
Captures data to be sent to GA.
It's currently at http://cyclonal.com.
It still uses Classic GA (_gaq) - any offers to upgrade it to Universal gladly accepted
I also cloned a site used by the GA Dev team's (with permission)
It tested almost every feature of GA at the time.
Which is at http://cyclonal.com/g (has a history of the site link in the footer)
Finally, and probably what you may want to clone/create yourself, is a free form version of the concepts behind the above sites at http://cyclonal.com/sandbox/codeExec
Let me know if that works for you.
Google team released a Google Analytics demo account: https://support.google.com/analytics/answer/6367342?hl=en#access You can start "playing" with this account to get familiarized with google analytics api!
I have a client that runs a number of sites and I manage some of them. They are a large company so they have had a premium Google Analytics account for some time, likely because another project requested it and it was upgraded across the board.
Enter me, one project we are working on is improving the data we track in GA. Step one of my plan was to upgrade to analytics.js & the new universal tracking code and to add ecommerce tracking. Seemed simple enough, I've already done it for other clients.
Well I just discovered that premium account can not use the new universal tracking code. Insane move by Google IMO, I don't understand who signed off on giving free accounts a feature that premium accounts don't have access to but alas it is what it is. Source: https://developers.google.com/analytics/devguides/collection/upgrade/
I'm wondering what the best course of action is. Ideas:
Use the "old" method using ga.js--annoying because I'll have to rewrite everything once Google turns on support for premium accounts, I enjoy double the billable hours but would rather be more efficient
Downgrade part of the account--huge headaches here too, presumably whoever wanted premium to begin with will continue wanting it. Don't think I can seperate out only my projects without losing all past data.
Something else that will solve my problem? I'm hoping there's a plan I've overlooked.
Have you thought about implementing Google Tag Manager? By using GTM, you could
create a new universal analytics (analytics.js) account
create a google tag manager account
create a staging environment and add GTM to that
add both your ga.js and analytics.js accounts to GTM
QA and push to production
When analytics.js comes out of beta and is enabled for premium, simply do the migration and move your ga.js tracking code over to the analytic.js tags you've already setup.
I've written about the benefits of using dual-tagging using google tag manager in a blog post, but I think it's your best bet for not having to redo your implementation.