I am tracking analytics through a Google Analytics - Universal Analytics tag implemented through GTM.
I've noticed recently that there may have been an issue with the setup of this which has resulted in a large amount of data missing (a few months worth) - specifically there is a lack of data in the site content > all pages report. Some data was recorded in June 2018 before recording appears to have stopped, however it appears this data is incorrect with very high page readings that are not reflected by the timeline in the audience overview report.
What's strange is that goals have still been recorded, including form submission and calls (these were also set up through GTM), also the audience overview has recorded data for the last six months.
I have added the analytics tag again making sure to have the correct property ID and have verified that it is firing via preview mode and via the real-time report in Analytics.
I'm confused how sessions and goals have been recorded if analytics may have been incorrectly installed and what may have occurred for there to be a black hole in the data?
If there is a lack of data in the site content report it means that on some pages from your site, either GTM is not firing (thus not firing GA) or there are some filters in your GA trigger in GTM which do not load the tag on all pages.
If you can provide some URL's which you think should be in the site content report, but are missing, we can check how GA is installed.
Related
I have a website where we're working on migrating from analytics.js to GTM, so we've created a new temporary property for verifying that GTM is working as per expectations. The existing analytics.js code sends data to an older property.
I see a lot of cases where many users simply don't appear in the GTM tracking data, and we've also done multiple pageview audits to confirm if all pages are tagged properly. There's always a gap of 10-15% in the user comparison, and 20-25% in the pageview comparison.
Has anyone worked on any similar situation where GTM tracking shows lesser data than normal analytics.js tracking?
Many of the conversions that my Firebase web app reports to my Google Analytics 4 property aren't showing up in Google Ads.
I have a single-page web app that uses the Firebase Analytics JS API to report custom events for a Google Analytics 4 property, including two events that have been marked as conversions in the Google Analytics "Conversions" page. All of the events reported by the app appear as expected in Google Analytics.
The GA4 property is linked with a Google Ads account that has auto-tagging enabled. I've imported the conversion events using the Ads site with a Count setting of "Every" (rather than "One"), but less than half of new ad-derived conversions are shown in Ads. For example, Analytics reports 55 occurrences of a conversion event two days ago, but Ads reports only 20 occurrences of the event for the same day.
I've used the Google Analytics Debugger extension to confirm that events contain a tid parameter with the GA4 property ID and a dl parameter that preserves the URL's gclid query parameter (using this approach). I've also used BigQuery to view the underlying Analytics events, and I can see that their page_location parameters preserve the gclid parameter and that they have correct value and currency parameters (e.g. 0.5 and "USD").
Are there other factors that affect whether GA4 events are correctly displayed in Google Ads? I'm confused by the way that some, but not all, events are showing up in Ads. I had a call with Google Ads support this morning but they aren't trained in diagnosing conversion-reporting issues.
Are the conversion events not showing up at all, or just not showing up after a couple of days? If it's the former, it's possible that there is a delay before the conversion reporting makes it to Google Ads and gets reported to the console.
As for inspecting the BigQuery conversion events for the correct tracking data, make sure to use the events_ table rather than the events_intraday tables as the summary tables more accurately reflect the count for events logged that day.
Beyond that it looks like your setup is correct since some conversion events are already being reported, but just in case here is a link to the Google Ads help center on all the steps required to make sure the Google Analytics 4 property used by Firebase is correctly linked to Google Ads.
in my site i have google analytics tag coded it works in real-time but when i go to behavior nothing show up.. it says there is only one event, in the graph section but down in the report section there's nothing.
![sample][1]
If you are using GA free, please be advised that the data will be visible in reports within 24-72 hrs. If you see the data in real-time reports, be assured it will show up in the reports in due time.
Previously, we had implemented Traditional e-commerce analytics (_gaq) using _trackTrans, _addItem, etc. We had several years of data in GA that correlated conversions with our Ad campaigns, based on UTM source, campaign, medium.
When switching over to Google Tag Manager, we did the following things:
• Removed the _gaq code related to e-commerce (transactions & addItem)
• Kept the rest of the GA code related to page tracking, events, and custom variables
• Implemented the Google Tag Manager javascript + a GTM data layer that included our new E-commerce information (Google Tag Manager data layer)
• Configured a "Tag" in GTM for "Order Completed" for Google Analytics, set to Universal Analytics (Configured with our UA- property identifier, etc.). Tag type= Universal Analytics; Tracking ID= our GA environment, Track Type = "Page View" , Enable enhanced e-commerce feature = true, Use data layer = True; Fire on "Order completed"
Upon switching over, we indeed see E-commerce numbers come through, but there's something off about the recording of these conversions correctly back to the campaigns. It appears that while some are attributed back, not all conversions are counted correctly as being from the ad campaign they originated from.
What went wrong here? After thorough reading of the GTM documentation, we were led to believe that it would "just work" but it appears that GTM and GA don't know how to communicate with each other regarding UTM information, and as a result GA tracks conversions but fails to attribute them to right session (that is, ITS session information that contains the correct UTM for that user).
We found a very scant amount of information about this on the internet-- but some people suggest setting all the UTMs are "Variables" in GTM, and then passing them as fields in the Tag firing back to GA. Is that necessary? It seems like these two technologies should work together with less friction.
Please advise.
I'm new to Google Analytics. Yesterday, I created an account and I pointed it to our website. I've added the JavaScript codes that Google Analytics generated for us. I put the code on all of our .html files.
I've been hitting our website from outside and so does my officemates since last night and also today. However, when I visited https://www.google.com/analytics under Reporting, everything was showing 0. I don't see any single spike at all.
I would recommend navigating to the Reporting -> Realtime -> Overview tab within your Google Analytics (GA) account. This is an almost realtime view into users on your site. In a separate tab access your site and refresh the page, this page view event should then be visible in the GA Realtime view.
If you can see your page view then its likely that you've inserted the correct GA script into your page and that you've used the correct GA property id. If you cant see your own page view then you will know that your script is incorrectly inserted or your GA property id is incorrect.
Last bit of advice: GA often has a 24-48 delay before you are able to use its full suite of insight tools (such as GA Goals). If you're expecting to see Goals populate immediately you're gonna have a bad time.
Last-last bit of advice: make sure that you select the current date from the date range picker in the top right of the GA Reporting view. It defaults to yesterday.