add basic site analytics + check for which posts to update after bulk import #36
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds the ability to make a simple Google Analytics report request using the reporting API v4.
Adds a `posts_to_update` module, which constructs a dataframe of the OWID pages that should be checked for textual inconsistencies following the approval of suggested chart revisions as part of a bulk dataset update. Each row is an OWID page, including the number of chart updated on the page and the number of page views (from Google Analytics) over the past 90 days.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements basic versions of two new utilities:
(1) A request_report utility that makes it easy to request a simple Google Analytics report (using the reporting API v4).
Note: this is implemented as an installed application, as opposed to a service application (which means that every time you use the utility, it opens a web browser and you have to sign in with an OWID google account). This should be implemented as a service application in the future, but I don't have admin access to Google Analytics in order to add the service account address.
(2) A posts_to_update utility that is intended to make it easy to see which public OWID pages need to be checked for textual inconsistencies after one or more suggested chart revisions have been approved as part of a bulk dataset update (ordered by number of page views in the past 90 days).
These two utilities are in the same PR b/c (2) is dependent on (1).