Wp-calypso: Google Analytics: change "Tracking ID" to "Measurement ID"

[simison]

Let's update the label for Google Analytics ID?

Via p58i-9Dr-p2#comment-47915

Todo:

• [ ] Update label
• [ ] Wait for translations
• [ ] Update docs:
  
  
  
  • [ ] https://jetpack.com/support/google-analytics/
  
  
  • [ ] https://wordpress.com/support/google-analytics/
  
  

Our UI — "Tracking ID":

Google Analytics UI — "Measurement ID":

[tyxla]

Happy to tinker with this quickly, but just in case, I'd like to cc @Automattic/dotcom-manage-design - are there any other changes you'd like to see here to make sure everything remains to be intuitive and makes sense?

[sixhours]

It definitely makes sense to update the label to reflect the new wording on Google's end.

I also agree this section would benefit from an audit; there are so many links and a lot of explanatory text. There are probably opportunities to simplify without losing context.

I'm adding this to the Dotcom Manage Design board so @lcollette can prioritize against our backlog.

[simison]

Related https://github.com/Automattic/wp-calypso/issues/36332

[simison]

@sixhours does the copy change make sense independently from an audit?

[sixhours]

@sixhours does the copy change make sense independently from an audit?

Yep!

[davemart-in]

@sixhours once you're happy with the design exploration, if you'd like help implementing this, please feel free to add this back to the Manage backlog. Thanks!

[getdave]

@sixhours Note also that Google's own docs which we reference in the UI still don't reflect the terminology change.

Searching the Google docs I came across this which explains the difference between Tracking ID and Measurement ID. Perhaps a useful link to include?

Probably one for a follow up Issues/PR though when we actually tackle the UX/Design of this section.

[getdave]

@sixhours Could you possibly review https://github.com/Automattic/wp-calypso/pull/47617. Thanks.

[getdave]

Wait for translations

@simison If we ship this change English speakers will see the change but it will fallback to the existing translation for all other languages. Given that the existing translation is the existing experience on WordPress.com does it make sense just to push this out and let the EN customers have the benefit of correct terminology and then the translations will catch up?

At what point is it appropriate to update the docs?

[simison]

There is a special i18n function for that kind of fallback behaviour. Good idea to ship English earlier!

Search for repo with "docs" and you can open an issue there.