Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Bitbucket Analytics Key will break July 1, 2023

johnrpeterson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 19, 2023

 

I've tried to report this elsewhere:

https://jira.atlassian.com/browse/BSERV-14067

 

The analytics tracking in bitbucket cloud will break on July 1, 2023, because google is transitioning from Universal Analytics to a G4 property tracking tag.  

 

See:

 

https://support.google.com/analytics/answer/12938611#zippy=%2Cin-this-article

 

But bitbucket cloud has not updated their interface to the tag, and switching the tag to the G4 tag doesn't do anything.  It should be a simple fix, but we need to make them aware of this issue.

 

As far as I can tell, they simply need to embed this into the html (where G-TAG is your tag from the g4 property).

 

<!-- Google tag (gtag.js) --> <script async src="https://www.googletagmanager.com/gtag/js?id=G-TAG"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'G-TAG'); </script>

 

1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 23, 2023

Hi @johnrpeterson,

Thank you for reaching out.

Your report in our issue tracker was created for Bitbucket Server instead. I went ahead and moved it to the Bitbucket Cloud project and brought this to the attention of the development team. I don't have an ETA to share at the moment, we will update the ticket in the issue tracker when there is an update.

Kind regards,
Theodora

johnrpeterson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 5, 2023

ok thanks!   It says the universal analytics key will no longer work (July 1st), but the new G4 property key still doesn't work.  I think it should be a simple fix to get it working, if you get the message to the right person on the team.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events