Implement Google analytics stats field in Article

[MrOrz]

Article should provide a field that returns analytics data for trend charts using Google Analytics Reporting API

• Chatbot visit per day
• Chatbot user count per day
• Chatbot total visit in 30 days
• Chatbot total user in 30 days
• All above stats, but using Cofacts production site as target

Related:

• https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO?node-id=889:306#25950845

[MrOrz]

Alternative:

we can deploy a super-proxy in Google app engine instead. https://github.com/googleanalytics/google-analytics-super-proxy#readme

Pros

• It has cache that helps keep usage below quota
• Allows rumors-site to fetch data directly, don't put burden on API server

Cons

• All API queries must be provided using admin panel, and each queries cannot include arguments. This means that we cannot create a query that takes articleId as a parameter.
  • Even if we modify the code to attach articleId, many its inner workings (such as cache) relies on query IDs, which means that supporting articleId may take a lot of effort.
• GAE may incur additional cost (needs testing)
• Super proxy is no longer maintained, may need to fork to get timezone / CORS right

[MrOrz]

Spec: https://g0v.hackmd.io/0kjaVlFASSyddkltqGR6Nw

[ztsai]

Server side todo list

• [x] update schema https://github.com/cofacts/rumors-db/pull/44

• [x] fetch data from google analytics and store in elasticsearch https://github.com/cofacts/rumors-api/issues/181

• [x] data loader: (article ids) -> stats https://github.com/cofacts/rumors-api/issues/182

• [x] new API endpoint to query for stats of a particular article https://github.com/cofacts/rumors-api/issues/183

Client side todo list

• [x] Implement chart

[ztsai]

closing this issue as the feature is completed additional UI/UX enhancement will be tracked here: https://github.com/cofacts/rumors-site/issues/332