andyvan-ph
commented
1 month ago
- Data warehouse vs CDP (50/m)
This a great one. There's a fair bit of competition, but worth doing. Perhaps we can work something into the benefits of having CDP and warehouse under one roof?
- Data warehouse benefits (1900/m)
I think pass on this. The likes of Oracle and IBM rank for this, so it would be tough and it feels a bit too high-level. Maybe something more specific like "When do I need a data warehouse?" might be good? Less search = less competition, and I think this would be the kind of prompt we'd want to appear in too.
- How we use the data warehouse at PostHog
100% this. I think we should probably start here, tbh.
- Tinybird alternatives (90/m)
How much overlap is there really, here? Maybe this will be more relevant if we go big on user-facing analytics.
- WTF is a materialized view and why do they matter (18k/m)
Too high level imo for us to add value.
- open source business intelligence tools (1900/m)
yes.
- Stripe data pipeline (480/m)
This refers to Stripe's own integration. If we were targeting this term, I think we'd want to optimize the docs page for our Stripe source, rather than do a tutorial. I think it would be hard to outrank Stripe and Snowflake here.
- Postgres analytics (210/m)
Unsure of the value of this one, but don't feel strongly.
Enhancing/linking persons with external data in PostHog
- Basically how to connect various sources and join them on users in PostHog
- Could be a good tutorial to send as part of data warehouse onboarding email flow
- https://posthog.com/questions/how-to-link-stripe-customer-to-a-user-in-posthog
- https://posthog.com/questions/connecting-hubspot-data-to-accounts-and-users
- Show off multiple sources
I think we should explore more stuff like this. We really need to dig into the problems people can solve using data warehouse and write about them. I'd see stuff like this as a resource to help existing users, rather than a top-of-funnel opportunity.
Would be good explore this a bit more by talking to the warehouse team + pm + sales about the kinds of problems people want to solve for here.
Docs
Figure out and match name of “data warehouse” in product and docs. Is it SQL editor or is it data warehouse?
- If we do this, we need to roll SQL insights into it: https://posthog.com/docs/product-analytics/sql
100%. I get the sense there's a bit of uncertainty here and I'd like to know exactly what the direction of travel is before we commit a bunch of time to it as a product.
“Run in PostHog” button for SQL examples like we have for Max AI
Nice.
SQL dictionary:
- There are a ton of SQL questions we could answer. People have a lot of questions about this and although we are sort of different, we can answer some of them.
- This seems to be Hightouch’s full SEO strategy: https://hightouch.com/sql-dictionary
- Also, there is ClickHouse functions we should be documenting better for us: https://clickhouse.com/docs/sql-reference/functions/array-functions
- An upgrade to https://posthog.com/docs/product-analytics/sql
- Adding materializing views to end user/customer facing analytics
This feels like a good place to focus to me. Would be cool if we could work toward a kind of "Complete guide to using SQL in PostHog" where people can start with the basics, then build up to more complex queries + understand how to use Max AI.
Having better references should help Max do a better job too, I imagine?
Summary
We want to push the data warehouse more. It is underutilized, mostly because people don't know about it or don't know how to use it. It's our responsibility in marketing to change this.
I fully expect doing a deep enough dive here will take multiple weeks, so I might not be the right person to do it.
Content progress
Content ideas
SEO blogs
Tutorials
Docs