A sudden drop in bounce rate | Community
Skip to main content
N
nbendov
Level 2
June 20, 2023
Solved

A sudden drop in bounce rate

  • June 20, 2023
  • 1 reply
  • 2540 views

Hi there,

I have noticed an unexplained sudden drop in bounce rate for (see image attached):

https://www.blackberry.com/us/en/solutions/endpoint-security/zero-trust-security

We had bounce rate at about 80% for this page. On April 12, 2023 the bounced rate drop to 2.10% and even hit 0% on April 14, 2023. After April 12 the bounce rate for this page stayed has been about 2% or lower.

There were no updates / changes made to our site around April 12. There is only one tracking script on the page. There are no redirects on this page.

Any thoughts on what is causing this issue? 

Thanks

Neil 

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by leocwlau

You have two  AA hits just on the page load, so it is not a bounce. You need to check what is the second hit and if it should be there. One common trick is to calculate another version of the bounce rate using "Single Page Visit" / "Visit".

1 reply

leocwlau
Community Advisor and Adobe Champion
leocwlauCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
June 20, 2023

You have two  AA hits just on the page load, so it is not a bounce. You need to check what is the second hit and if it should be there. One common trick is to calculate another version of the bounce rate using "Single Page Visit" / "Visit".

    N
    nbendovAuthor
    Level 2
    June 20, 2023

    Hi there,

     

    Thank you for the help. 

     

    The dev said that there was no updated to the site. Was it there before and suddenly started tracking? 

    How did you find it (how did you get to the screen grab)? How do I know which script to remove?   

     

    Thanks

    Neil

    Jennifer_Dungan
    Community Advisor and Adobe Champion
    Jennifer_DunganCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    June 20, 2023

    I recognize the tool @leocwlau used, it's called Omnibug... but you can detect multiple calls with any tool really... Omnibug, Adobe's Experience League Debugger, or looking straight at the Network calls in your browser's Dev Tools.

     

    Now, identifying what rule is firing twice... you can try using the Satellite Debug mode... in your console you can turn debugging on and off using:

    // Turn on debugging _satellite.setDebug(true); // Turn off debugging _satellite.setDebug(false);

     

    This will give you logs in your console about what rules are running (including which rules are not meeting conditions, if you have any such rules). This will be very handy for identifying if one of your rules is triggering twice, or if two different tracking rules are being triggered...

     

    Once you identify the problem, you will have to understand what trigger the rule is using to try and determine the best way to fix it.

    Terms & ConditionsAccessibility statement

    Loading footer...