Create a new bouncer variable in Analytics

Reports and working with data
1

Hello team,

My problem is as follow : We developped some custom goals to properly track conversion rate in our ecommerce website (another URL than the main one) the downside of this is disabling the bouncer counter each time someone land on the website. Could you please help us creating another bouncer counter through the tag manager that we can then use in the Analytics platform?

Thanks in advance.

Alexandre Biton.

2

Hello Alexandre,
Thanks for reaching out. We are currently discussing possible solutions. Please expect to hear from us tomorrow.

Thank you!
Piotr

3

Hello @Alexandre,
Thank you for your patience. It seems that the easiest solution would be using custom events instead of using goal conversions to set up conversion rate tracking on the ecommerce website. Custom events doesn’t affect whether a session is considered bounced. Would you like me to assist you with this?

Thank you,
Piotr

4

Hi Piotr,

Thank you for reverting back to us. THat’s a shame we didn’t do it that way in the first place. Anyway, I will be happy If you help me create custom events. I also needed it to see the avg time on page and avg session duration working for unique URL of our websites.
Don’t hesitate to reach out If unclear.

Looking forward to hearing from you.

Best,

Alex.

5

Thank you @Alexandre. I’ll reach out to you through a support ticket since further discussion requires referring to certain mechanics in your setup. Please expect to hear from me shortly.

Thanks,
Piotr

6

Hi Piotr,

Your team adivsed us to not split the websites URL in the first place, we need some consistency and we can’t change everything from scratch every 3 months. Please propose a solution with custom event to track bouncer as I don’t see any other solution that wouldn’t affect our current settings.

Thanks in advance.

Regards,

Alex.

7

Dear Alexandre,
My apologies for the complications you are experiencing and thank you for providing more context.

The solution we recommended previously was viable for a set of TLDs that behave as a single entity. Now that we are aware of the per-TLD requirements, it’s clear that the trade-off that comes with it won’t work for your specific use case. Taking the above into account - one of the available solutions was in fact excluding two TLDs into separate entities. That said - now that we know it’s a no-go, we will pursue another approach.

Please let me know if I should continue the thread here or if we should move to the support ticket since further communication will refer to your analytics configuration.

Best,
Piotr

8

THanks Piotr for your feedback. I can’t really say It’s a no-go. I just need all my indicators to be working. On one hand, I would like to have the visibility of all my users through all the different URLs, on the other one, I would like to separate key metrics when It comes to usage consumption (eg : Bounce Rate, Average Time on Site etc etc…)
I would rather, not change our current structure as our web agency is not very helpful. So please investigate the other solution you were mentioning and don’t hesitate If you need to mve the ticket to a more consistent environment.

Best,

Alex.

9

Makes perfect sense and it’s totally understandable. Thank you. I’ll be back with an update on Monday.

Best,
Piotr

11

Hello @Fivie.22,
The case described in this thread was very specific and it’s more than unlikely that you are facing the very same issue. Would you mind describing the problem you’ve stumbled upon in a separate thread?

Thank you!
Piotr