Why might Google Analytics report a sudden, but persistent, drop in bounce rate (70% to 12%)
I was tracking data for a site and realize that there is a sudden drop in bounce rate in Google Analytics. The sudden drop happened across 2 days and remained consistent after.
The bounce rate in January 2019 is about 70% whereas after 2 days, it became 12-15%. I am unaware of what my colleague did so I am trying to figure it out now.
Is a bounce rate of 12% normal?
google-analytics bounce-rate
New contributor
add a comment |
I was tracking data for a site and realize that there is a sudden drop in bounce rate in Google Analytics. The sudden drop happened across 2 days and remained consistent after.
The bounce rate in January 2019 is about 70% whereas after 2 days, it became 12-15%. I am unaware of what my colleague did so I am trying to figure it out now.
Is a bounce rate of 12% normal?
google-analytics bounce-rate
New contributor
add a comment |
I was tracking data for a site and realize that there is a sudden drop in bounce rate in Google Analytics. The sudden drop happened across 2 days and remained consistent after.
The bounce rate in January 2019 is about 70% whereas after 2 days, it became 12-15%. I am unaware of what my colleague did so I am trying to figure it out now.
Is a bounce rate of 12% normal?
google-analytics bounce-rate
New contributor
I was tracking data for a site and realize that there is a sudden drop in bounce rate in Google Analytics. The sudden drop happened across 2 days and remained consistent after.
The bounce rate in January 2019 is about 70% whereas after 2 days, it became 12-15%. I am unaware of what my colleague did so I am trying to figure it out now.
Is a bounce rate of 12% normal?
google-analytics bounce-rate
google-analytics bounce-rate
New contributor
New contributor
edited yesterday
Stephen Ostermiller♦
68.4k1393252
68.4k1393252
New contributor
asked yesterday
J. ShiJ. Shi
315
315
New contributor
New contributor
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
I'd be willing to bet that your colleague implemented on-page events.
By default Google Anaytics only measures page views. Bounces are defined as users who only view one page; even if that user spends hours on one page.
Events allow you to track what happens within the page. You can send GA information about items such as:
- User clicking on buttons
- User scrolling the page
- User spending X minutes on the page
- User typing on the page
- User watching a video on the page
- Additional AJAX content gets loaded
All of those events can be marked as "interactive" which causes GA to say "this user did not bounce." They also could be marked as "non-interactive" which does not affect the bounce rate.
If I'm right, you will see data in the "Behavior" -> "Events" -> "Overview" report starting right when your bounce rate went way down.
A 12% bounce rate when events are implemented is quite normal. It is also very normal for some types of sites to have a 75% bounce rate before events:
- Single page applications (SPAs) only have multiple page views if users refresh or click to the site a second time.
- Many sites provide all the information that most users need right in the landing page. That is common for articles and calculators. I feel that it shouldn't be a "bounce" if the user reads the entire article.
Events are the way to let GA know that you are satisfying your users even when they are only viewing one page.
You may want to review the events that are being sent and make sure that each is being marked as "interactive" or "non-interactive" appropriately.
1
Well this is a real eye-opener. You would think that a person landing on the exact page they needed from a Google result would be calculated more favorably. By adding these events does it also improve the SEO algorithm by showing Google that your user did not "bounce" per the redefined definition?
– MonkeyZeus
yesterday
2
Google Analytics statistics have no direct impact on SEO. Improving your bounce rate by implementing events doesn't change user behavior and can't affect your rankings. For ranking purposes, Google cares that users are satisfied. Rankings could get worse if lots of users head back to the search results after visiting your site and click on another site instead. For a detailed explanation of why, see my answer to "Does a site's bounce rate influence Google rankings?"
– Stephen Ostermiller♦
yesterday
This is a new area for me. Thank you. After a quick bit of reading it appears that Google Tag Manager is loaded Asynchronously. Still, is there a performance hit on pages using GTM?
– Trebor
14 hours ago
You don't need to use Google tag manager for events. It can be done that way, but I've never used it for that purpose. I've always implemented events with JavaScript loaded in the normal js way.
– Stephen Ostermiller♦
12 hours ago
add a comment |
The bounce rate, generally becomes low when any of the following changes are done:
- Better Landing Page Experience
- Content served to the user is highly valuable compared to others
- No changes on-page are made but traffic from a low quality source, stopped coming.
To understand why, check the following with your Analytics and colleague:
- Any changes to landing page/content?
- Any changes to the sources of visitors to your webpages?
Is a bounce rate of 12% is not normal?
This totally depends on your website category and traffic sources. For my website, I'm maintaining less than your 12% bounce rate, which not a lot of people could achieve. (The % is not relevant as it also has to be accounted with the no. of users that visit the webpage in a particular period.)
add a comment |
Is that an average bounce rate over different pages/sources?
Usually if it drops to zero it is due to double pageview events firing but since you are showing a consistent 12% I imagine that the tracking issue is only affecting some pages.
I like to use Tag Assistant Chrome add-on for debugging
add a comment |
Those all are good things, and of course all of us want data to look like that, no doubt :) , but do not forget that there is "other" side of medal. This can be result based on intercepted script/wrongly setup or double tracking, if someone accidentally implemented code twice, or if you have Both GTM and GA scripts on website code. Check those as well. I hope i am wrong but...
I would expect the bounce rate to be lower (almost zero) if GA is being called twice. If that were true there should also be a corresponding big jump in the page views. Certainly worth checking.
– Stephen Ostermiller♦
16 hours ago
IF it is GTM over GA, not quite, i know odd thing, but that actually happened, bounce rate dropped on 5,6% avg.
– Filozof666
13 mins ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "45"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
J. Shi is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwebmasters.stackexchange.com%2fquestions%2f121360%2fwhy-might-google-analytics-report-a-sudden-but-persistent-drop-in-bounce-rate%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
I'd be willing to bet that your colleague implemented on-page events.
By default Google Anaytics only measures page views. Bounces are defined as users who only view one page; even if that user spends hours on one page.
Events allow you to track what happens within the page. You can send GA information about items such as:
- User clicking on buttons
- User scrolling the page
- User spending X minutes on the page
- User typing on the page
- User watching a video on the page
- Additional AJAX content gets loaded
All of those events can be marked as "interactive" which causes GA to say "this user did not bounce." They also could be marked as "non-interactive" which does not affect the bounce rate.
If I'm right, you will see data in the "Behavior" -> "Events" -> "Overview" report starting right when your bounce rate went way down.
A 12% bounce rate when events are implemented is quite normal. It is also very normal for some types of sites to have a 75% bounce rate before events:
- Single page applications (SPAs) only have multiple page views if users refresh or click to the site a second time.
- Many sites provide all the information that most users need right in the landing page. That is common for articles and calculators. I feel that it shouldn't be a "bounce" if the user reads the entire article.
Events are the way to let GA know that you are satisfying your users even when they are only viewing one page.
You may want to review the events that are being sent and make sure that each is being marked as "interactive" or "non-interactive" appropriately.
1
Well this is a real eye-opener. You would think that a person landing on the exact page they needed from a Google result would be calculated more favorably. By adding these events does it also improve the SEO algorithm by showing Google that your user did not "bounce" per the redefined definition?
– MonkeyZeus
yesterday
2
Google Analytics statistics have no direct impact on SEO. Improving your bounce rate by implementing events doesn't change user behavior and can't affect your rankings. For ranking purposes, Google cares that users are satisfied. Rankings could get worse if lots of users head back to the search results after visiting your site and click on another site instead. For a detailed explanation of why, see my answer to "Does a site's bounce rate influence Google rankings?"
– Stephen Ostermiller♦
yesterday
This is a new area for me. Thank you. After a quick bit of reading it appears that Google Tag Manager is loaded Asynchronously. Still, is there a performance hit on pages using GTM?
– Trebor
14 hours ago
You don't need to use Google tag manager for events. It can be done that way, but I've never used it for that purpose. I've always implemented events with JavaScript loaded in the normal js way.
– Stephen Ostermiller♦
12 hours ago
add a comment |
I'd be willing to bet that your colleague implemented on-page events.
By default Google Anaytics only measures page views. Bounces are defined as users who only view one page; even if that user spends hours on one page.
Events allow you to track what happens within the page. You can send GA information about items such as:
- User clicking on buttons
- User scrolling the page
- User spending X minutes on the page
- User typing on the page
- User watching a video on the page
- Additional AJAX content gets loaded
All of those events can be marked as "interactive" which causes GA to say "this user did not bounce." They also could be marked as "non-interactive" which does not affect the bounce rate.
If I'm right, you will see data in the "Behavior" -> "Events" -> "Overview" report starting right when your bounce rate went way down.
A 12% bounce rate when events are implemented is quite normal. It is also very normal for some types of sites to have a 75% bounce rate before events:
- Single page applications (SPAs) only have multiple page views if users refresh or click to the site a second time.
- Many sites provide all the information that most users need right in the landing page. That is common for articles and calculators. I feel that it shouldn't be a "bounce" if the user reads the entire article.
Events are the way to let GA know that you are satisfying your users even when they are only viewing one page.
You may want to review the events that are being sent and make sure that each is being marked as "interactive" or "non-interactive" appropriately.
1
Well this is a real eye-opener. You would think that a person landing on the exact page they needed from a Google result would be calculated more favorably. By adding these events does it also improve the SEO algorithm by showing Google that your user did not "bounce" per the redefined definition?
– MonkeyZeus
yesterday
2
Google Analytics statistics have no direct impact on SEO. Improving your bounce rate by implementing events doesn't change user behavior and can't affect your rankings. For ranking purposes, Google cares that users are satisfied. Rankings could get worse if lots of users head back to the search results after visiting your site and click on another site instead. For a detailed explanation of why, see my answer to "Does a site's bounce rate influence Google rankings?"
– Stephen Ostermiller♦
yesterday
This is a new area for me. Thank you. After a quick bit of reading it appears that Google Tag Manager is loaded Asynchronously. Still, is there a performance hit on pages using GTM?
– Trebor
14 hours ago
You don't need to use Google tag manager for events. It can be done that way, but I've never used it for that purpose. I've always implemented events with JavaScript loaded in the normal js way.
– Stephen Ostermiller♦
12 hours ago
add a comment |
I'd be willing to bet that your colleague implemented on-page events.
By default Google Anaytics only measures page views. Bounces are defined as users who only view one page; even if that user spends hours on one page.
Events allow you to track what happens within the page. You can send GA information about items such as:
- User clicking on buttons
- User scrolling the page
- User spending X minutes on the page
- User typing on the page
- User watching a video on the page
- Additional AJAX content gets loaded
All of those events can be marked as "interactive" which causes GA to say "this user did not bounce." They also could be marked as "non-interactive" which does not affect the bounce rate.
If I'm right, you will see data in the "Behavior" -> "Events" -> "Overview" report starting right when your bounce rate went way down.
A 12% bounce rate when events are implemented is quite normal. It is also very normal for some types of sites to have a 75% bounce rate before events:
- Single page applications (SPAs) only have multiple page views if users refresh or click to the site a second time.
- Many sites provide all the information that most users need right in the landing page. That is common for articles and calculators. I feel that it shouldn't be a "bounce" if the user reads the entire article.
Events are the way to let GA know that you are satisfying your users even when they are only viewing one page.
You may want to review the events that are being sent and make sure that each is being marked as "interactive" or "non-interactive" appropriately.
I'd be willing to bet that your colleague implemented on-page events.
By default Google Anaytics only measures page views. Bounces are defined as users who only view one page; even if that user spends hours on one page.
Events allow you to track what happens within the page. You can send GA information about items such as:
- User clicking on buttons
- User scrolling the page
- User spending X minutes on the page
- User typing on the page
- User watching a video on the page
- Additional AJAX content gets loaded
All of those events can be marked as "interactive" which causes GA to say "this user did not bounce." They also could be marked as "non-interactive" which does not affect the bounce rate.
If I'm right, you will see data in the "Behavior" -> "Events" -> "Overview" report starting right when your bounce rate went way down.
A 12% bounce rate when events are implemented is quite normal. It is also very normal for some types of sites to have a 75% bounce rate before events:
- Single page applications (SPAs) only have multiple page views if users refresh or click to the site a second time.
- Many sites provide all the information that most users need right in the landing page. That is common for articles and calculators. I feel that it shouldn't be a "bounce" if the user reads the entire article.
Events are the way to let GA know that you are satisfying your users even when they are only viewing one page.
You may want to review the events that are being sent and make sure that each is being marked as "interactive" or "non-interactive" appropriately.
edited yesterday
answered yesterday
Stephen Ostermiller♦Stephen Ostermiller
68.4k1393252
68.4k1393252
1
Well this is a real eye-opener. You would think that a person landing on the exact page they needed from a Google result would be calculated more favorably. By adding these events does it also improve the SEO algorithm by showing Google that your user did not "bounce" per the redefined definition?
– MonkeyZeus
yesterday
2
Google Analytics statistics have no direct impact on SEO. Improving your bounce rate by implementing events doesn't change user behavior and can't affect your rankings. For ranking purposes, Google cares that users are satisfied. Rankings could get worse if lots of users head back to the search results after visiting your site and click on another site instead. For a detailed explanation of why, see my answer to "Does a site's bounce rate influence Google rankings?"
– Stephen Ostermiller♦
yesterday
This is a new area for me. Thank you. After a quick bit of reading it appears that Google Tag Manager is loaded Asynchronously. Still, is there a performance hit on pages using GTM?
– Trebor
14 hours ago
You don't need to use Google tag manager for events. It can be done that way, but I've never used it for that purpose. I've always implemented events with JavaScript loaded in the normal js way.
– Stephen Ostermiller♦
12 hours ago
add a comment |
1
Well this is a real eye-opener. You would think that a person landing on the exact page they needed from a Google result would be calculated more favorably. By adding these events does it also improve the SEO algorithm by showing Google that your user did not "bounce" per the redefined definition?
– MonkeyZeus
yesterday
2
Google Analytics statistics have no direct impact on SEO. Improving your bounce rate by implementing events doesn't change user behavior and can't affect your rankings. For ranking purposes, Google cares that users are satisfied. Rankings could get worse if lots of users head back to the search results after visiting your site and click on another site instead. For a detailed explanation of why, see my answer to "Does a site's bounce rate influence Google rankings?"
– Stephen Ostermiller♦
yesterday
This is a new area for me. Thank you. After a quick bit of reading it appears that Google Tag Manager is loaded Asynchronously. Still, is there a performance hit on pages using GTM?
– Trebor
14 hours ago
You don't need to use Google tag manager for events. It can be done that way, but I've never used it for that purpose. I've always implemented events with JavaScript loaded in the normal js way.
– Stephen Ostermiller♦
12 hours ago
1
1
Well this is a real eye-opener. You would think that a person landing on the exact page they needed from a Google result would be calculated more favorably. By adding these events does it also improve the SEO algorithm by showing Google that your user did not "bounce" per the redefined definition?
– MonkeyZeus
yesterday
Well this is a real eye-opener. You would think that a person landing on the exact page they needed from a Google result would be calculated more favorably. By adding these events does it also improve the SEO algorithm by showing Google that your user did not "bounce" per the redefined definition?
– MonkeyZeus
yesterday
2
2
Google Analytics statistics have no direct impact on SEO. Improving your bounce rate by implementing events doesn't change user behavior and can't affect your rankings. For ranking purposes, Google cares that users are satisfied. Rankings could get worse if lots of users head back to the search results after visiting your site and click on another site instead. For a detailed explanation of why, see my answer to "Does a site's bounce rate influence Google rankings?"
– Stephen Ostermiller♦
yesterday
Google Analytics statistics have no direct impact on SEO. Improving your bounce rate by implementing events doesn't change user behavior and can't affect your rankings. For ranking purposes, Google cares that users are satisfied. Rankings could get worse if lots of users head back to the search results after visiting your site and click on another site instead. For a detailed explanation of why, see my answer to "Does a site's bounce rate influence Google rankings?"
– Stephen Ostermiller♦
yesterday
This is a new area for me. Thank you. After a quick bit of reading it appears that Google Tag Manager is loaded Asynchronously. Still, is there a performance hit on pages using GTM?
– Trebor
14 hours ago
This is a new area for me. Thank you. After a quick bit of reading it appears that Google Tag Manager is loaded Asynchronously. Still, is there a performance hit on pages using GTM?
– Trebor
14 hours ago
You don't need to use Google tag manager for events. It can be done that way, but I've never used it for that purpose. I've always implemented events with JavaScript loaded in the normal js way.
– Stephen Ostermiller♦
12 hours ago
You don't need to use Google tag manager for events. It can be done that way, but I've never used it for that purpose. I've always implemented events with JavaScript loaded in the normal js way.
– Stephen Ostermiller♦
12 hours ago
add a comment |
The bounce rate, generally becomes low when any of the following changes are done:
- Better Landing Page Experience
- Content served to the user is highly valuable compared to others
- No changes on-page are made but traffic from a low quality source, stopped coming.
To understand why, check the following with your Analytics and colleague:
- Any changes to landing page/content?
- Any changes to the sources of visitors to your webpages?
Is a bounce rate of 12% is not normal?
This totally depends on your website category and traffic sources. For my website, I'm maintaining less than your 12% bounce rate, which not a lot of people could achieve. (The % is not relevant as it also has to be accounted with the no. of users that visit the webpage in a particular period.)
add a comment |
The bounce rate, generally becomes low when any of the following changes are done:
- Better Landing Page Experience
- Content served to the user is highly valuable compared to others
- No changes on-page are made but traffic from a low quality source, stopped coming.
To understand why, check the following with your Analytics and colleague:
- Any changes to landing page/content?
- Any changes to the sources of visitors to your webpages?
Is a bounce rate of 12% is not normal?
This totally depends on your website category and traffic sources. For my website, I'm maintaining less than your 12% bounce rate, which not a lot of people could achieve. (The % is not relevant as it also has to be accounted with the no. of users that visit the webpage in a particular period.)
add a comment |
The bounce rate, generally becomes low when any of the following changes are done:
- Better Landing Page Experience
- Content served to the user is highly valuable compared to others
- No changes on-page are made but traffic from a low quality source, stopped coming.
To understand why, check the following with your Analytics and colleague:
- Any changes to landing page/content?
- Any changes to the sources of visitors to your webpages?
Is a bounce rate of 12% is not normal?
This totally depends on your website category and traffic sources. For my website, I'm maintaining less than your 12% bounce rate, which not a lot of people could achieve. (The % is not relevant as it also has to be accounted with the no. of users that visit the webpage in a particular period.)
The bounce rate, generally becomes low when any of the following changes are done:
- Better Landing Page Experience
- Content served to the user is highly valuable compared to others
- No changes on-page are made but traffic from a low quality source, stopped coming.
To understand why, check the following with your Analytics and colleague:
- Any changes to landing page/content?
- Any changes to the sources of visitors to your webpages?
Is a bounce rate of 12% is not normal?
This totally depends on your website category and traffic sources. For my website, I'm maintaining less than your 12% bounce rate, which not a lot of people could achieve. (The % is not relevant as it also has to be accounted with the no. of users that visit the webpage in a particular period.)
answered yesterday
idkidk
54611
54611
add a comment |
add a comment |
Is that an average bounce rate over different pages/sources?
Usually if it drops to zero it is due to double pageview events firing but since you are showing a consistent 12% I imagine that the tracking issue is only affecting some pages.
I like to use Tag Assistant Chrome add-on for debugging
add a comment |
Is that an average bounce rate over different pages/sources?
Usually if it drops to zero it is due to double pageview events firing but since you are showing a consistent 12% I imagine that the tracking issue is only affecting some pages.
I like to use Tag Assistant Chrome add-on for debugging
add a comment |
Is that an average bounce rate over different pages/sources?
Usually if it drops to zero it is due to double pageview events firing but since you are showing a consistent 12% I imagine that the tracking issue is only affecting some pages.
I like to use Tag Assistant Chrome add-on for debugging
Is that an average bounce rate over different pages/sources?
Usually if it drops to zero it is due to double pageview events firing but since you are showing a consistent 12% I imagine that the tracking issue is only affecting some pages.
I like to use Tag Assistant Chrome add-on for debugging
answered yesterday
Rob TRob T
563
563
add a comment |
add a comment |
Those all are good things, and of course all of us want data to look like that, no doubt :) , but do not forget that there is "other" side of medal. This can be result based on intercepted script/wrongly setup or double tracking, if someone accidentally implemented code twice, or if you have Both GTM and GA scripts on website code. Check those as well. I hope i am wrong but...
I would expect the bounce rate to be lower (almost zero) if GA is being called twice. If that were true there should also be a corresponding big jump in the page views. Certainly worth checking.
– Stephen Ostermiller♦
16 hours ago
IF it is GTM over GA, not quite, i know odd thing, but that actually happened, bounce rate dropped on 5,6% avg.
– Filozof666
13 mins ago
add a comment |
Those all are good things, and of course all of us want data to look like that, no doubt :) , but do not forget that there is "other" side of medal. This can be result based on intercepted script/wrongly setup or double tracking, if someone accidentally implemented code twice, or if you have Both GTM and GA scripts on website code. Check those as well. I hope i am wrong but...
I would expect the bounce rate to be lower (almost zero) if GA is being called twice. If that were true there should also be a corresponding big jump in the page views. Certainly worth checking.
– Stephen Ostermiller♦
16 hours ago
IF it is GTM over GA, not quite, i know odd thing, but that actually happened, bounce rate dropped on 5,6% avg.
– Filozof666
13 mins ago
add a comment |
Those all are good things, and of course all of us want data to look like that, no doubt :) , but do not forget that there is "other" side of medal. This can be result based on intercepted script/wrongly setup or double tracking, if someone accidentally implemented code twice, or if you have Both GTM and GA scripts on website code. Check those as well. I hope i am wrong but...
Those all are good things, and of course all of us want data to look like that, no doubt :) , but do not forget that there is "other" side of medal. This can be result based on intercepted script/wrongly setup or double tracking, if someone accidentally implemented code twice, or if you have Both GTM and GA scripts on website code. Check those as well. I hope i am wrong but...
answered 17 hours ago
Filozof666Filozof666
1365
1365
I would expect the bounce rate to be lower (almost zero) if GA is being called twice. If that were true there should also be a corresponding big jump in the page views. Certainly worth checking.
– Stephen Ostermiller♦
16 hours ago
IF it is GTM over GA, not quite, i know odd thing, but that actually happened, bounce rate dropped on 5,6% avg.
– Filozof666
13 mins ago
add a comment |
I would expect the bounce rate to be lower (almost zero) if GA is being called twice. If that were true there should also be a corresponding big jump in the page views. Certainly worth checking.
– Stephen Ostermiller♦
16 hours ago
IF it is GTM over GA, not quite, i know odd thing, but that actually happened, bounce rate dropped on 5,6% avg.
– Filozof666
13 mins ago
I would expect the bounce rate to be lower (almost zero) if GA is being called twice. If that were true there should also be a corresponding big jump in the page views. Certainly worth checking.
– Stephen Ostermiller♦
16 hours ago
I would expect the bounce rate to be lower (almost zero) if GA is being called twice. If that were true there should also be a corresponding big jump in the page views. Certainly worth checking.
– Stephen Ostermiller♦
16 hours ago
IF it is GTM over GA, not quite, i know odd thing, but that actually happened, bounce rate dropped on 5,6% avg.
– Filozof666
13 mins ago
IF it is GTM over GA, not quite, i know odd thing, but that actually happened, bounce rate dropped on 5,6% avg.
– Filozof666
13 mins ago
add a comment |
J. Shi is a new contributor. Be nice, and check out our Code of Conduct.
J. Shi is a new contributor. Be nice, and check out our Code of Conduct.
J. Shi is a new contributor. Be nice, and check out our Code of Conduct.
J. Shi is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Webmasters Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwebmasters.stackexchange.com%2fquestions%2f121360%2fwhy-might-google-analytics-report-a-sudden-but-persistent-drop-in-bounce-rate%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown