collective / collective/collective.googleanalytics
Handle upgrade to "Universal Analytics"
- Dominant language
- Python
- Stars
- 4
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Google is changing their analytics platform to what they're calling "Universal Analytics" (UA).
https://support.google.com/analytics/answer/2790010?hl=en
Although they don't give dates in their timeline, at some point all Google Analytics properties will need to be using UA.
https://developers.google.com/analytics/devguides/collection/upgrade/
The upgrade to UA involves changing the script included on each page.
https://developers.google.com/analytics/devguides/collection/upgrade/guide
Unfortunately, we can't just change the script within this product because the web "property" must first be transferred within the Google Analytics Admin page. (See above link.)
Not sure what the best way to handle this is. A couple ideas:
-A Generic Setup upgrade step that could be run to change the included script after the site has been transferred
-A Control Panel widget to flip over to the new script once the site has been transferred
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Google Analytics upgrade guide and the linked Universal Analytics documentation to understand the required property transfer and script change. Compare the proposed Generic Setup upgrade step and Control Panel widget approaches; done means the product can switch a transferred site to the Universal Analytics script.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100