Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pushing experiment 3 blog post #361

Merged
merged 4 commits into from
May 25, 2023
Merged

pushing experiment 3 blog post #361

merged 4 commits into from
May 25, 2023

Conversation

rahuljo
Copy link
Contributor

@rahuljo rahuljo commented May 25, 2023

No description provided.

@rahuljo rahuljo requested a review from TyDunn May 25, 2023 09:09
@netlify
Copy link

netlify bot commented May 25, 2023

Deploy Preview for dlt-hub-docs ready!

Name Link
🔨 Latest commit 75d5ebe
🔍 Latest deploy log https://app.netlify.com/sites/dlt-hub-docs/deploys/646f2fc9e66f7a00085f96b6
😎 Deploy Preview https://deploy-preview-361--dlt-hub-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

Copy link
Collaborator

@TyDunn TyDunn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rahuljo Just a couple things. Once you address them, we can merge!

---
# Using Google BigQuery and Metabase to understand product usage

TL;DR: Trying to become more user-centric and make data driven decisions? Get started with the SQL source pipeline + BigQuery + Metabase
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please use usual callout block


## When you have a web and / or mobile app but no data yet

If you're a startup without a dedicated data team but a sizeable number of users on your website or mobile app, then chances are that you are collecting and storing all your product data in OLTP databases like MySQL, Postgres, etc. As you have grown, you have likely been aiming to become more user-centric, yet you find that no one at your company has information on what the users do or what their experience is like. Stakeholders should be making data-driven decisions, but they are not yet because they are unable to use the existing data to understand user behavior and experience. This is usually the point when folks realize they need a data warehouse.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you're a startup without a dedicated data team but a sizeable number of users on your website or mobile app, then chances are that you are collecting and storing all your product data in OLTP databases like MySQL, Postgres, etc. As you have grown, you have likely been aiming to become more user-centric, yet you find that no one at your company has information on what the users do or what their experience is like. Stakeholders should be making data-driven decisions, but they are not yet because they are unable to use the existing data to understand user behavior and experience. This is usually the point when folks realize they need a data warehouse.
If you're a startup without a dedicated data team but a sizeable number of users on your website or mobile app, then chances are that you are collecting and storing all your product data in OLTP databases like MySQL, Postgres, etc. As you have grown, you have likely been aiming to become more user-centric, yet you find that no one at your company has information on what your users do or what their experience is like. Stakeholders should be making data-driven decisions, but they are not yet because they are unable to use the existing data to understand user behavior and experience. This is usually the point when folks realize they need a data warehouse.

![orders_chart.png](/img/experiment3_dashboard_orders_chart.png) ![top_selling_tables.png](/img/experiment3_dashboard_top_selling_tables.png)
In addition to this, we were also able to set up email alerts to get notified whenever the stock of a DVD was either empty or close to emptying.

![low_stock_email_alert.png](/img/experiment3_low_stock_email_alert.png) ![low_stock_file_csv.png](/img/experiment3_low_stock_file_csv.png)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand why we are showing a spreadsheet here

@TyDunn TyDunn merged commit 0154413 into devel May 25, 2023
@rudolfix rudolfix deleted the experiment3_blog branch June 6, 2023 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants