I recently implemented firebase analytics tracking in MatHem’s native apps and in that process I discovered that the documentation about tracking e-commerce is very limited compared to how to implement it in Google Analytics. Also, the events and parameters in the documentation didn’t fit our needs for analyzing e-commerce interactions. Hence, I thought I would share our implementation of Firebase Analytics.
First, Firebase Analytics has a completely different data model than Google Analytics....
Are you planning to use Firebase Analytics in a WebView on Android or iOS? Beware if you want to log doubles (price for example) as event parameters.
Google is sunsetting the Analytics Services SDKs coming fall and promote the transition to tracking your apps with the Firebase SDKs. Firebase Analytics is awesome (BigQuery Export, User and Event based, etc.). However, there is an issue I’m certain many analysts will face when implementing Firebase Analytics in a WebView....
A strategic decision we’ve made at MatHem is to enable users to connect to or data warehous (BigQuery) with whatever tool (tableau, data studio, collab, etc.) they prefer and still be certain that they only can access data that they have permission to. That turned out to be a challenge in BigQuery with the current access management capabilities, since you give users/roles (or authorized views) access on the dataset-level and not views/table-level....
One of the announcements I liked the most from Google Cloud Next 18 was Google Cloud Build (former Google Container Builder). I’ve been missing easy and lightweight CI/CD for GCP, especially with focus on serverless. I thought I would give it a try before setting it up for CI/CD in the open source data/analytics/ML solution I’m working on - DataHem. Hence, I figured I use it to power this blog....