I've faced with a strange problem.
I have an event in GTM that triggered by Timer every 5 sec.
GA pageview tag (gtag) is implemented hardcoded above GTM.
In reports I see a lot of sessions with landing page (not set). It seems that timer generates a new session every time.
Any ideas?
I think you should first remove the GTM code on the page and see if the landing pages are showing up fine to find out if mixing both is causing the issue
Related
I'm still learning GTM, so please forgive me if this is a basic question. I've been researching but can't find anyone with a similar issue.
What I want is simple: to set up GTM to track page views in UA. (Easy enough.) But I looked at the setup of my predecessor, and he had the UA tag set up like this:
Tag Type: Google Analytics (UA)
Track Type: Page View
(GA ID)
Triggering:
All Clicks (All Elements)
OR
All Pages (Page View)
I'm trying to understand why they set it up with the All Clicks trigger. What I fear is that this is recording a page view every time a click is recorded, but I can't imagine my predecessor would have created a strange setup like that. I'd just as soon eliminate the All Clicks trigger, but I don't want to harm any of our future data without fully understanding. Bottom line question: is there any good reason for this tag to be set up this way, or is it wrongly inflating my numbers? Thanks in advance for any help.
It's kind of weird.
If the tag is for tracking pageView. The trigger should only be all page.
Still there might be 1% that your predecessor really knows what he or she is doing.
Maybe you can share the website and we can check if it is abnormal or not.
Update about the click trigger
The website is firing "Pageview" when click the link.
You can change the GA tag from pageview to event and set up like this
Category : click
Action : link_click
Label : {{the click Url}}
Then you can see which user is doing pageview and who clicks the link.
I am managing a website where a dynamic landing page, due to a badly written/optimized code, often times out after a few seconds and shows a blank. After refreshing, the page loads but it usually takes long time.
To assess the issue, I am looking at the avg. page load time in GA at Behaviour/Site Speed/Page Timings and I can see a value of 11.62 sec.
Does this value contain any data about page loads that timed out before they could finish loading?
In case not, is there a way I can see any data about the page's time outs (for example how many user sessions were affected by it)?
Many thanks.
If a page load is timing out (say a 500 error) then there would be not GA event firing. If the page is loading but then the data is loading dynamically and timing out, then you would want to use a custom event to learn when it's loaded or perhaps a gtm timer trigger to see if at x seconds the data has loaded or not.
The GA feature you are most closely describing is known as User Timings, but there is no default feature for a timeout of a dynamic element, you'd need to create the measurement event (aka the timing hit).
I have GTM's out-of-the-box scroll depth tracker deployed across my site. When looking at Google Tag Assistant, I'm noticing a new session is created every time a user scrolls beyond a scroll threshhold when scroll tracker is enabled (e.g 25, 50, 75, 100%) and scrolling events fire at each threshhold. The error throws a Client ID reset. This results in a new Client ID each time the event fires at each threshhold. In reports, this means potentially five additional new users and/or sessions per pageview and could affect bounce rate and average time on page stats, with a huge inflation of new sessions across the site from this error.
Disabled scroll tracking and the Client ID error stops. What causes new sessions to be generated from scroll depth event firing?
GA error message: "This hit starts a new session, most likely because the client ID changed. This is caused by an improper tracking code implementation."
I looked at the website, and I noticed that, for some strange reason, the first time I land on your website (with the cookiebar present) the Google Analytics cookie _ga has no content and its deadline also means that being 2 years old is set to yesterday.
A very strange behavior but that would explain the problem. In fact it seems that there is something on the website that deletes that cookie once created so Analytics, not finding it, creates a new one at each event or pageview, for this reason it generates a user every hit it sends in this situation.
if you close the cookiebar and refresh the page, the _ga cookie works correctly.
I have never seen anything like this, it would be interesting to understand what this behavior actually happens, however you would solve it in less time by changing the cookiebar on the website.
I am using GTM/GA to track a site that reloads (http refresh) itself every 30 seconds. This makes pageviews meaningless. How does one track the original page load, but not reloads of the same page?
For GA there is no difference between automatic and manual page refresh. It works by counting each refresh. There is no way to distinguish them from each other.
Although if you use javascript to refresh your website, you can try to disable tracking on page refresh and enable it on page load.
I have an ASP.NET app that uses Crystal Reports through the CR Viewer.
The records shown are based on a session variable.
This part works fine.
However, I want to clear the session variable when they are done looking at the report.
So I tried to clear it in the page_unload event. To my surprise, that event fired while the report was loading up. The first page of the report still displays OK, but additional pages don't as the records it was based on is now empty.
Further testing showed that the page_unload event doesn't even fire when leaving the CR
I don't know why the page_unload fires after the page_load, but I figured I would try clearing my session variable in the page_disposed event. But that didn't fire either when I went to another page in my app.
I also tried the CrystalReportViewer1_Unload event, but that also fires on every page when loading.
So I'm looking for where I can clear the session variable when I know they are done looking at the report. Thanks.
If anyone comes up with an answer, that would still be great. But here's the work around I found.
The reason I wanted to clear the session variable was that it was storing a shopping cart, and after printing, I wanted the shopping cart empty in case they went shopping some more.
What I ended up doing was copying the session variable to another. I clear the fist one before printing use the second one for printing the records. It doesn't matter if the second one is cleared, or not, as it's not the real shopping cart.