mirror of
https://github.com/BillyOutlast/posthog.com.git
synced 2026-02-04 03:11:21 +01:00
fixing 115 broken links (#12148)
This commit is contained in:
Edwin Lim
@@ -31,7 +31,7 @@ import { ComparisonRow } from 'components/ComparisonTable/row'
|
||||
|
||||
### What is PostHog?
|
||||
|
||||
[PostHog](/) (that's us 👋) is an open-source platform combining web and product analytics, session replay, heatmaps, A/B testing, feature flags, and user surveys into one product. This means it's not only an alternative to Adobe Analytics but also tools like [Hotjar](/blog/posthog-vs-hotjar) and [VWO](/blog/posthog-vs-vwo).
|
||||
[PostHog](/) (that's us 👋) is an open-source platform combining web and product analytics, session replay, heatmaps, A/B testing, feature flags, and user surveys into one product. This means it's not only an alternative to Adobe Analytics but also tools like [Hotjar](/blog/posthog-vs-hotjar) and [VWO](/blog/best-vwo-alternatives).
|
||||
|
||||
According to [BuiltWith](https://trends.builtwith.com/analytics/PostHog), as of October 2024, 5,330 of the top 1 million websites deploy PostHog. This is significantly more than the 3,259 who use Adobe Analytics.
|
||||
|
||||
|
||||
@@ -31,7 +31,7 @@ A/B tests are a great way to confirm that your product changes have the intended
|
||||
|
||||
### What is PostHog?
|
||||
|
||||
[PostHog](https://posthog.com) (that's us!) is an all-in-one platform built to help engineers create better products. It includes A/B testing **and** a whole bunch more, such as [product analytics](/product-analytics), [session replays](/session-replay), [feature flags](/feature-flags), and [surveys](/survey).
|
||||
[PostHog](https://posthog.com) (that's us!) is an all-in-one platform built to help engineers create better products. It includes A/B testing **and** a whole bunch more, such as [product analytics](/product-analytics), [session replays](/session-replay), [feature flags](/feature-flags), and [surveys](/surveys).
|
||||
|
||||
It's designed for product-minded engineers, growth teams, and product managers who need to move fast and iterate based on reliable, actionable insights.
|
||||
|
||||
|
||||
@@ -159,7 +159,7 @@ According to [reviews on G2](https://www.g2.com/products/microsoft-microsoft-cla
|
||||
|
||||
### What is PostHog?
|
||||
|
||||
[PostHog](https://posthog.com) (that's us 👋) is an all-in-one platform built to help engineers create better products. It includes [session replays](/session-replay) **and** a whole bunch more, such as [product analytics](/analytics), [A/B testing](/experiments), and [feature flags](/feature-flags).
|
||||
[PostHog](https://posthog.com) (that's us 👋) is an all-in-one platform built to help engineers create better products. It includes [session replays](/session-replay) **and** a whole bunch more, such as [product analytics](/product-analytics), [A/B testing](/experiments), and [feature flags](/feature-flags).
|
||||
|
||||
It's designed for product-minded engineers, growth teams, and product managers who need to move fast and iterate based on reliable, actionable insights.
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ Why would you want to get non-product data into PostHog? So you can do things li
|
||||
- [Sync Hubspot data](/tutorials/hubspot-reports) to identify leads based on their actions, pageviews, and churn-risk.
|
||||
- [Sync Zendesk data](/tutorials/zendesk-reports) to see how ticket volume and SLA metrics impact usage and churn.
|
||||
|
||||
All that is just using our pre-built connectors. You can also bring data into PostHog from almost anywhere using [Snowflake, Cloudflare R2, Amazon S3, Google Cloud Storage](/docs/data-warehouse/setup), or [custom sources](/docs/data-warehouse/setup#linking-a-custom-source) — and we’re fascinated to see what further use cases teams will come up with.
|
||||
All that is just using our pre-built connectors. You can also bring data into PostHog from almost anywhere using [Snowflake, Cloudflare R2, Amazon S3, Google Cloud Storage](/docs/cdp/sources), or [custom sources](/docs/cdp/sources#linking-a-custom-source) — and we’re fascinated to see what further use cases teams will come up with.
|
||||
|
||||
Over the beta we’ve already seen teams sync everything from their bank data (for analyzing P&L without an accountant) to CRMs (for monitoring sales team performance). Teams like [Headshot Pro, for example, have synced Google Adwords](/customers/headshot-pro), so they can analyze marketing data in detail and attribute it to sign-ups and usage.
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ We’re biased, but PostHog is a great one. When [compared with Google Analytics
|
||||
|
||||
This post will go over the basics you must know to make the transition from Google Analytics to PostHog.
|
||||
|
||||
> **Want to track website visitors in PostHog?** Find out [how to migrate from Google Analytics to PostHog](/migrate/google-analytics) and start using [our new web analytics tool](/web-analytics).
|
||||
> **Want to track website visitors in PostHog?** Find out [how to migrate from Google Analytics to PostHog](/docs/migrate/google-analytics) and start using [our new web analytics tool](/web-analytics).
|
||||
|
||||
## Initial PostHog setup
|
||||
|
||||
|
||||
@@ -184,7 +184,7 @@ According to [reviews on G2](https://www.g2.com/products/microsoft-microsoft-cla
|
||||
|
||||
### What is PostHog?
|
||||
|
||||
[PostHog](https://posthog.com) (that's us 👋) is an all-in-one platform built to help engineers create better products. It includes [session replays](/session-replay) **and** a whole bunch more, such as [product analytics](/analytics), [A/B testing](/experiments), and [feature flags](/feature-flags).
|
||||
[PostHog](https://posthog.com) (that's us 👋) is an all-in-one platform built to help engineers create better products. It includes [session replays](/session-replay) **and** a whole bunch more, such as [product analytics](/product-analytics), [A/B testing](/experiments), and [feature flags](/feature-flags).
|
||||
|
||||
It's designed for product-minded engineers, growth teams, and product managers who need to move fast and iterate based on reliable, actionable insights.
|
||||
|
||||
|
||||
@@ -125,7 +125,7 @@ Improving reliability, integrations, and UX is critical for success here. Being
|
||||
|
||||
To go one better, we are also working on making PostHog a data warehouse. This means storing and using arbitrary data from many different sources, scaling this up to users needs, and integrating with traditional data warehousing tools. Our team [built this](https://github.com/PostHog/posthog/pull/14915) at our last Hackathon.
|
||||
|
||||
It consists of custom tables that are created and queried through the PostHog UI and API. These tables provide a way to store and query data from sources like [Stripe](/tutorials/stripe-reports), [Hubspot](/tutorials/hubspot-reports), [Intercom](/tutorials/intercom-reports), and more along with data from PostHog.
|
||||
It consists of custom tables that are created and queried through the PostHog UI and API. These tables provide a way to store and query data from sources like [Stripe](/tutorials/stripe-reports), [Hubspot](/tutorials/hubspot-reports), Intercom, and more along with data from PostHog.
|
||||
|
||||
This improves data accuracy and reporting flexibility. It also enables teams to continue using PostHog (which they are familiar with), as they scale. This replaces many of the tools of the modern data stack, which means they don't have to set up or maintain it. They can spend their time and resources building a great product.
|
||||
|
||||
|
||||
@@ -37,7 +37,7 @@ We're committed to [sustainably low pricing](/pricing/philosophy), and every cus
|
||||
|
||||
Use our [built-in data warehouse](/data-warehouse) and SQL insight builder to analyze data from [Stripe](/tutorials/stripe-reports), [Hubspot](/tutorials/hubspot-reports), Salesforce, and [Zendesk](/tutorials/stripe-reports).
|
||||
|
||||
Already have a warehouse? You can [link it with ours](/docs/data-warehouse/setup) to analyze your data in PostHog, and [batch export event and person data](/docs/cdp/batch-exports) from PostHog to your data warehouse.
|
||||
Already have a warehouse? You can [link it with ours](/docs/data-warehouse) to analyze your data in PostHog, and [batch export event and person data](/docs/cdp/batch-exports) from PostHog to your data warehouse.
|
||||
|
||||
## Product comparison
|
||||
|
||||
|
||||
@@ -94,7 +94,7 @@ It's hard to import data into Google Analytics because:
|
||||
|
||||
In contrast, PostHog is built to be your single source of truth, so it's simple to import data from other sources using our [built-in data warehouse](/docs/data-warehouse), or send PostHog data to other tools using our [realtime destinations](/docs/cdp/destinations).
|
||||
|
||||
Below is a comparison of some of the most popular apps – see our [data pipeline](/docs/cdp/airbyte-export) and [warehouse docs](/docs/data-warehouse/setup) for a complete list of integrations.
|
||||
Below is a comparison of some of the most popular apps – see our [data pipeline](/docs/cdp) and [warehouse docs](/docs/data-warehouse) for a complete list of integrations.
|
||||
|
||||
<ComparisonTable column1="PostHog" column2="Google Analytics">
|
||||
<ComparisonRow column1={true} column2={true} feature="Stripe" description="Import charges, customers, invoices, subscriptions, and more" />
|
||||
|
||||
@@ -37,7 +37,7 @@ PostHog is built with transparency at its core. Not only do we work in the open
|
||||
|
||||
### 3. PostHog constantly ships new features
|
||||
|
||||
We ship weirdly fast. We update [our changelog](/changlog) every week and often there’s even more features in beta testing. And that’s without counting all the apps and integrations submitted by our community! We work hard to keep PostHog on the cutting edge and we’re transparent about the ways we do that.
|
||||
We ship weirdly fast. We update [our changelog](/changelog) every week and often there’s even more features in beta testing. And that’s without counting all the apps and integrations submitted by our community! We work hard to keep PostHog on the cutting edge and we’re transparent about the ways we do that.
|
||||
|
||||
## Comparing PostHog and LogRocket
|
||||
|
||||
|
||||
@@ -322,7 +322,7 @@ See our docs for full lists of [destinations](/docs/cdp) and [data warehouse sou
|
||||
<ComparisonRow column1="Enterprise" column2="Enterprise" feature="SAML/SSO" description="Use SAML or single sign-on authentication" />
|
||||
</ComparisonTable>
|
||||
|
||||
> **Good to know:** A Business Associate Agreement for HIPAA compliance is available for customers with our [platforms add-ons](/platforms-addons). The add-on also includes our managed reverse proxy, priority support, SSO and 2FA enforcement, numerous collaboration features, and support multiple environments within projects so you can separate dev and production data, but use the same insights and dashboards across them all.
|
||||
> **Good to know:** A Business Associate Agreement for HIPAA compliance is available for customers with our [platforms add-ons](/platform-addons). The add-on also includes our managed reverse proxy, priority support, SSO and 2FA enforcement, numerous collaboration features, and support multiple environments within projects so you can separate dev and production data, but use the same insights and dashboards across them all.
|
||||
|
||||
<br />
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@ tags:
|
||||
---
|
||||
|
||||
<blockquote class='warning-note'>
|
||||
<b>IMPORTANT!</b> Do not upgrade to this version if you have deployed PostHog using Postgres. PostHog no longer supports a Postgres-based installation (last version supported is <code>1.30.0</code>) and now requires Clickhouse. To use this version, you must <a href="/docs/migrate/migrate-between-posthog-instances" target="_blank">upgrade to ClickHouse</a> first.
|
||||
<b>IMPORTANT!</b> Do not upgrade to this version if you have deployed PostHog using Postgres. PostHog no longer supports a Postgres-based installation (last version supported is <code>1.30.0</code>) and now requires Clickhouse.
|
||||
</blockquote>
|
||||
|
||||
## PostHog 1.32.0 release notes
|
||||
@@ -86,7 +86,7 @@ Funnels with breakdowns just got a lot better. This new view enables you to quic
|
||||
|
||||
### Deprecation & removal notices
|
||||
|
||||
1. Since the previous version (1.31.0), we no longer support a Postgres-only deployment of PostHog. Read [our migration guide](/docs/migrate/migrate-between-posthog-instances) for instructions on moving over to a ClickHouse version. ClickHouse provides faster queries and is optimized for very large volumes of data, and you will also get a new lot of features.
|
||||
1. Since the previous version (1.31.0), we no longer support a Postgres-only deployment of PostHog. ClickHouse provides faster queries and is optimized for very large volumes of data, and you will also get a new lot of features.
|
||||
2. We're removing support for insights with "Minute" intervals. From user feedback, these insights were hard to parse and could lead to significant performance issues in self-hosted instances. Please [reach out](/support) if you have any feedback on this. More details on the [PR](https://github.com/PostHog/posthog/pull/7847).
|
||||
|
||||
## Share your feedback
|
||||
|
||||
@@ -29,7 +29,7 @@ Recognizing the need for a self-serve solution, Kedar Page, a Data Scientist at
|
||||
|
||||
“PMs, designers and strategists wanted insights at their fingertips, but it invariably required an analyst and the turnaround time wasn’t quick enough to facilitate data driven decision making,” explained Kedar. “So, I started exploring tools that would enable non-analysts to get the information they needed.”
|
||||
|
||||
“We tried [Mixpanel](/customers/why-i-ditched-mixpanel-for-posthog) and Segment, but you’re totally bound by how they’ve set up the ETL pipeline,” added Vendasta Staff Engineer Jesse Redl. “Our senior engineering team didn’t like the [GDPR compliance](/blog/best-gdpr-compliant-analytics-tools) aspect either because you don’t own your own data. They say you do, but you don’t really. That’s when we decided to deploy PostHog.”
|
||||
“We tried Mixpanel and Segment, but you’re totally bound by how they’ve set up the ETL pipeline,” added Vendasta Staff Engineer Jesse Redl. “Our senior engineering team didn’t like the [GDPR compliance](/blog/best-gdpr-compliant-analytics-tools) aspect either because you don’t own your own data. They say you do, but you don’t really. That’s when we decided to deploy PostHog.”
|
||||
|
||||
## Cutting onboarding drop-off by 50% with a self-serve solution
|
||||
|
||||
|
||||
@@ -71,7 +71,7 @@ Responding to these BugSnag alerts caused a lot of friction, however. Brandon an
|
||||
|
||||
A major reason Brandon was willing to make this switch was due to the way PostHog tools are interoperable and can be seamlessly used in combination.
|
||||
|
||||
You can, for example, get an [alert](/docs/alerts) about an [error](/error-tracking), view a linked [session replay](/replay), and jump from there to a view of [the individual person](/docs/data/persons) or [the organization they belong to].
|
||||
You can, for example, get an [alert](/docs/alerts) about an [error](/error-tracking), view a linked [session replay](/session-replay), and jump from there to a view of [the individual person](/docs/data/persons) or [the organization they belong to].
|
||||
|
||||
You can even use [Max AI](/docs/max-ai), the in-app AI agent, to search for similar errors and recordings using natural language.
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ You'll be able to capture more usage data without having to self-host PostHog, e
|
||||
|
||||
Using our [managed reverse proxy](/docs/advanced/proxy/managed-reverse-proxy) is the easiest way to do this.
|
||||
|
||||
It's available as part of our [platforms add-ons](/platforms-addons), which includes automatic provisioning, SSO and 2FA enforcement, priority support, and additional collaboration features.
|
||||
It's available as part of our [platforms add-ons](/platform-addons), which includes automatic provisioning, SSO and 2FA enforcement, priority support, and additional collaboration features.
|
||||
|
||||
Other documented options for deploying a reverse proxy include:
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ Browse all the **Destinations** listed in the sidenav to integrate with well-kno
|
||||
<details>
|
||||
<summary>Want to bring your data into PostHog?</summary>
|
||||
|
||||
Check out [Sources](/docs/cdp/sources/overview) to learn how to connect your systems like CRM, payment processor, or database with PostHog data for all-in-one analytics.
|
||||
Check out [Sources](/docs/cdp/sources) to learn how to connect your systems like CRM, payment processor, or database with PostHog data for all-in-one analytics.
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
@@ -256,7 +256,7 @@ Product Qualified Lead. A PQL is a user who has expressed interest in your produ
|
||||
Analytics services which focus on tracking identified _and_ anonymous users and how they interact with your product. Product analytics services, such as PostHog, typically involve more detailed analysis tools than [web analytics](/manual/glossary#web-analytics) tools as a result of being able to focus on idenfitied users.
|
||||
|
||||
#### PR
|
||||
Sometimes this means Public Relations and refers to working with journalists and members of the media. But when *we* say PR, we usually mean a [pull request](/manual/glossary#pull-request), because [we don't really do the other sort of PR outside of major announcements](/handbook/growth/marketing/press).
|
||||
Sometimes this means Public Relations and refers to working with journalists and members of the media. But when *we* say PR, we usually mean a [pull request](/manual/glossary#pull-request), because [we don't really do the other sort of PR outside of major announcements](/handbook/growth/marketing).
|
||||
|
||||
#### Property
|
||||
In PostHog, [events](/manual/glossary#events) and [persons](/manual/glossary#persons) contain additional information, called Properties. A property can be any information stored on the object, such as which device they are using or their geographic location. [Find out more about using properties in PostHog](/docs/how-posthog-works/queries).
|
||||
|
||||
@@ -69,7 +69,7 @@ Giving other teams the data they want becomes much easier with PostHog in the mi
|
||||
|
||||
We also care about the technical details of switching over.
|
||||
|
||||
No matter your stack or existing tools, **complete integration and [migration docs](/docs/migration)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
|
||||
No matter your stack or existing tools, **complete integration and [migration docs](/docs/migrate)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
|
||||
|
||||
***
|
||||
|
||||
@@ -135,4 +135,4 @@ We’ve published [customer stories](/customers) with loads of companies who hav
|
||||
|
||||
You can use these points to start the conversation. No matter who you're talking to, remember: it's easy to try this out with no risk, fees, or commitment.
|
||||
|
||||
Check out our [pilot planning guide](/docs/new-to-posthog/switch-guide/pilot-planning) for some ideas on how to quickly get your team to experience PostHog.
|
||||
Check out our [pilot planning guide](/docs/new-to-posthog/switch-guide/planning-your-pilot) for some ideas on how to quickly get your team to experience PostHog.
|
||||
@@ -220,7 +220,7 @@ Some features depend on [cohorts](/docs/data/cohorts) to work well. Some informa
|
||||
|
||||
- [Feature flags](/docs/feature-flags) - target specific user segments in experiments
|
||||
- [Surveys](/docs/surveys) - Enable for specific cohorts of users
|
||||
- [Insights](/docs/data/insights) - filter and breakdown by user characteristics
|
||||
- [Insights](/docs/product-analytics/insights) - filter and breakdown by user characteristics
|
||||
|
||||
import IdentifyFrontendCode from "../_snippets/identify-frontend-code.mdx"
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ If you require GDPR compliance, there are [specific guidelines](docs/privacy/gdp
|
||||
|
||||
## Processing data before storage
|
||||
|
||||
PostHog supports [realtime transformations](/docs/transformations/realtime-transformations) of data **before it's stored in PostHog**. These transformations are applied to all events captured in realtime, so you can use them to:
|
||||
PostHog supports [realtime transformations](/docs/cdp/transformations) of data **before it's stored in PostHog**. These transformations are applied to all events captured in realtime, so you can use them to:
|
||||
|
||||
- [Redacting PII data](https://posthog.com/tutorials/property-filter) before it's stored in PostHog
|
||||
- Disabling default [GeoIP enrichment transformations](https://us.posthog.com/pipeline/transformations)
|
||||
|
||||
@@ -61,7 +61,7 @@ We strongly recommend teams which need HIPAA compliance use PostHog Cloud under
|
||||
|
||||
</CalloutBox>
|
||||
|
||||
The best way to use PostHog in a way which is HIPAA compliant is with a BAA covering a PostHog Cloud instance. This ensures that PostHog remains scalable and that you have access to all premium features and security enhancements. BAAs are only available to users with a [platform add-on for our standard BAA, or the Enterprise plan for a custom BAA](/platforms-addons).
|
||||
The best way to use PostHog in a way which is HIPAA compliant is with a BAA covering a PostHog Cloud instance. This ensures that PostHog remains scalable and that you have access to all premium features and security enhancements. BAAs are only available to users with a [platform add-on for our standard BAA, or the Enterprise plan for a custom BAA](/platform-addons).
|
||||
|
||||
However, it is possible to host PostHog yourself using our open-source hobby deployment. It is important to note that the hobby deployment is **only suitable for smaller event volumes** and provided without guarantee. It also lacks many of the advanced features available under PostHog Cloud.
|
||||
|
||||
|
||||
@@ -105,7 +105,7 @@ You can use text cards to annotate your dashboard – useful for adding context
|
||||
|
||||
By clicking 'Share' in the top right corner you can:
|
||||
|
||||
- Restrict edit access to certain members within a project. Dashboards can be shared either by members with administrator privileges or by the dashboard creator ([platforms add-ons](/platforms-addons) required).
|
||||
- Restrict edit access to certain members within a project. Dashboards can be shared either by members with administrator privileges or by the dashboard creator ([platforms add-ons](/platform-addons) required).
|
||||
|
||||
- Create a link to share your dashboard publicly, or embed your dashboard on a website. Read more about this in our [sharing and embedding docs](/docs/product-analytics/sharing).
|
||||
|
||||
|
||||
@@ -126,7 +126,7 @@ Annoyingly, dealing with stock options is one of those slightly manual things yo
|
||||
Congrats, you have hopefully saved a bunch of precious time and mental energy that can now be used on building the product, talking to customers, recruiting and creating (presumably) massive hype in the AI chatbot space.
|
||||
|
||||
- You should probably document all this stuff in your handbook! Don't have one yet? Feel free to [copy ours](/handbook).
|
||||
- We've written a step-by-step [guide to startup finance](/founders/startup-finance-without-finance in detail – without hiring a finance person.
|
||||
- We've written a step-by-step [guide to startup finance](/founders/startup-finance-without-finance) in detail – without hiring a finance person.
|
||||
- At some point you'll want to [make your first ops hire](/founders/first-ops-hire).
|
||||
|
||||
<NewsletterForm />
|
||||
|
||||
@@ -22,7 +22,7 @@ If a customer contacts us about migrating data into PostHog we should first refe
|
||||
- [Migrating from LaunchDarkly to PostHog](/docs/migrate/launchdarkly)
|
||||
- [Migrating from Statsig to PostHog](/docs/migrate/statsig)
|
||||
- [Migrating from a self-hosted deployment to PostHog Cloud](/docs/migrate/migrate-to-cloud#between-cloud-instances-eg-us-cloud-to-eu-cloud)
|
||||
- [Syncing other platforms to our data warehouse](/docs/data-warehouse/setup)
|
||||
- [Syncing other platforms to our data warehouse](/docs/data-warehouse)
|
||||
|
||||
### Implementation help
|
||||
Sometimes teams want help or advice on their event taxonomy, or creating specific insights. Users who look like they have the potential to pay >$20k should generally be referred to the Sales & CS team, otherwise they should go through the regular support flow. We also have [a wide variety of dashboard templates](/templates) and tutorials to help teams get started.
|
||||
|
||||
@@ -54,7 +54,7 @@ For new product announcements we generally apply the following best practices:
|
||||
Comms should also be aware of [the engineering best practices for product launches](/handbook/engineering/development-process#best-practices-for-full-releases), so we can be sure that features launch well.
|
||||
|
||||
### PR announcements
|
||||
We do not typically do public relations for anything other than company-level news. We have separate [processes and guides for managing press announcements](/handbook/growth/brand/press).
|
||||
We do not typically do public relations for anything other than company-level news. We have separate [processes and guides for managing press announcements](/handbook/brand/press).
|
||||
|
||||
## Maintenance communications
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ This is shared across multiple teams and people - we (deliberately) do not have
|
||||
|
||||
- The [Content team](/teams/content) doesn't 'run community' in the traditional sense, but is instead responsible for ensuring that the content hubs in particular have a steady stream of engaging content and replying to users when they engage. They also proactively respond to questions and use feedback to create new types of content such as tutorials and docs.
|
||||
|
||||
> Support should not considered part of community at PostHog. [Support](/growth/customer-support#how-we-ensure-amazing-customer-support-at-posthog) is driven by the Customer Success team, primarily using in-app support and decdicated Slack channels. Good customer support helps build positive word of mouth, but replying to support queries is not an engaging or scalable way to build a thriving community.
|
||||
> Support should not considered part of community at PostHog. [Support](/handbook/support/customer-support) is driven by the Customer Success team, primarily using in-app support and decdicated Slack channels. Good customer support helps build positive word of mouth, but replying to support queries is not an engaging or scalable way to build a thriving community.
|
||||
|
||||
## Content hubs
|
||||
|
||||
|
||||
@@ -51,7 +51,7 @@ New posts should be:
|
||||
- Linked to the corresponding issue (so the issue is closed when the PR is merged)
|
||||
|
||||
> **Useful resources:**
|
||||
> - [List of tags for each section](/handbook/growth/marketing/tags-and-categories)
|
||||
> - [List of tags for each section](/handbook/content/tags-and-categories)
|
||||
> - [Embeddable components you can use](/handbook/growth/marketing/components) (tables, CTAs, etc.)
|
||||
> - [Andy's guide to SEO best practices](/handbook/growth/marketing/seo-guide)
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ Health scores are a great way to assess whether your customer is at risk of chur
|
||||
|
||||
Health score metrics are divided into two categories: Customer Engagement (20%) and Product Engagement (80%).
|
||||
|
||||
[**Customer engagement**](/contents/handbook/cs-and-onboarding/health-tracking#customer-engagement)
|
||||
[**Customer engagement**](/handbook/cs-and-onboarding/health-tracking#customer-engagement)
|
||||
|
||||
| Score Name | Measuring | Weighting |
|
||||
|---------------------------|--------------------------------------------------|--------------|
|
||||
@@ -22,7 +22,7 @@ Health score metrics are divided into two categories: Customer Engagement (20%)
|
||||
| Product experience | Are there negative experiences with the product? | 5% |
|
||||
| Company engagement | Are they engaging with PostHog humans? | 5% |
|
||||
|
||||
[**Product engagement**](/contents/handbook/cs-and-onboarding/health-tracking#product-engagement)
|
||||
[**Product engagement**](/handbook/cs-and-onboarding/health-tracking#product-engagement)
|
||||
|
||||
| Score Name | Measuring | Weighting |
|
||||
|-----------------------------|--------------------------------------------------------------------------------------|--------------|
|
||||
|
||||
@@ -35,7 +35,7 @@ Brian runs monthly marketing growth reviews, which cover:
|
||||
|
||||
A lead is someone who has either:
|
||||
|
||||
- **Signed up** for PostHog ([we score these](/growth/sales/lead-scoring) to prioritize follow-up)
|
||||
- **Signed up** for PostHog ([we score these](/handbook/growth/sales/lead-scoring) to prioritize follow-up)
|
||||
- **Requested a demo** through the site
|
||||
|
||||
We don’t gate content or the product. We don’t rely on shady tactics or clickbait. If someone wants to try the product or talk to us, we make it easy.
|
||||
|
||||
@@ -48,7 +48,7 @@ getting live **production** data through our pipeline and available for analysis
|
||||
1. A [blog post](/blog/aarrr-pirate-funnel) on getting started with the framework.
|
||||
2. A sample AARRR [tracking plan](https://docs.google.com/spreadsheets/d/12uV5aKAhU_wygUQl3YXZU2J_QN_AZi4nPFj-9WIKhlY/edit#gid=0) which we can give to customers to fill in. It shows how we do things at PostHog and may help inspire people who don't know how to get started.
|
||||
1. Encourage them to create dashboards for them to show off PostHog in the wider organization.
|
||||
1. Keep on top of any [support](/handbook/growth/customer-support) requests / blockers they may have.
|
||||
1. Keep on top of any [support](/handbook/support/customer-support) requests / blockers they may have.
|
||||
|
||||
|
||||
## Free trials?
|
||||
@@ -73,7 +73,7 @@ By contrast, paid has premium features around collaboration - such as user permi
|
||||
|
||||
Congratulations, this is the best part! Now we focus on making customers successful at unlocking insights into their product.
|
||||
|
||||
Read about how we do this in the dedicated handbook section, [Ensuring Customer Delight at PostHog](/handbook/growth/customer-support).
|
||||
Read about how we do this in the dedicated handbook section, [Ensuring Customer Delight at PostHog](/handbook/support/customer-support).
|
||||
|
||||
## How we measure revenue
|
||||
|
||||
|
||||
@@ -181,12 +181,12 @@ All new hires should schedule a 30 minute session with the [support engineer clo
|
||||
|
||||
In this call the support engineer will be able to answer any questions, as well as demonstrate how we deal with support at PostHog. In particular, the support engineer should cover:
|
||||
|
||||
- [ ] [What the role of a support hero is](/handbook/growth/customer-support#engineers-are-support-heroes) and how they can expect to receive tickets/escalations
|
||||
- [ ] [An overview of where tickets come from](/handbook/growth/customer-support#its-easy-for-customers-to-reach-us) and how to differentiate between paying/free users
|
||||
- [ ] [What the role of a support hero is](/handbook/support/customer-support#support-is-done-by-actual-engineers) and how they can expect to receive tickets/escalations
|
||||
- [ ] [An overview of where tickets come from](/handbook/support/customer-support#its-easy-for-customers-to-reach-us) and how to differentiate between paying/free users
|
||||
- [ ] [How to create tickets from Slack threads](/handbook/engineering/support-hero#pylon-to-create-zendesk-tickets-from-slack-posts) and [reassign tickets to other teams](https://support.zendesk.com/hc/en-us/articles/4408887127450-Manually-assigning-a-ticket)
|
||||
- [ ] [Advice on how to communicate with customers](/handbook/engineering/support-hero#how-do-i-communicate) and [prioritize tickets](/handbook/engineering/support-hero#how-do-i-prioritize)
|
||||
- [ ] [How and when to mark tickets as 'On Hold' or 'Pending'](/handbook/engineering/support-hero#ticket-status)
|
||||
- [ ] [What our SLAs](/handbook/growth/customer-support#response-targets) are and [what ticket severity indicates](/docs/support-options#severity-levels)
|
||||
- [ ] [What our SLAs](/handbook/support/customer-support#response-targets) are and [what ticket severity indicates](/docs/support-options#severity-levels)
|
||||
- [ ] How to deal with bug reports and feature requests
|
||||
- [ ] [How to use macros to answer questions quickly](https://support.zendesk.com/hc/en-us/articles/4408887656602-Using-macros-to-update-tickets)
|
||||
- [ ] How to avoid duplication of effort in ZenDesk
|
||||
|
||||
@@ -13,7 +13,7 @@ Ops provide all the tools, literally and metaphorically, needed for our team to
|
||||
- A small ops team covering a wide range of disciplines that can react to any incoming items to allow the rest of the business to focus on what they do best - building products.
|
||||
- Nailing the basics of working at a start-up for our team members. Making sure things like payroll, onboarding, offboarding etc. all work smoothly and are on autopilot as much as possible.
|
||||
- Thinking slightly further ahead than the “here and now" to predict when we may need to make changes like hiring new team members, changing our spending patterns to manage cash, managing our comp structure, implementing a new tool etc.
|
||||
- Setting a very high bar for bringing people on board. We are always looking for the best people in their field, or people on their way to becoming exceptional at their jobs. This is so important to us, it's enshrined in our company [values](/values).
|
||||
- Setting a very high bar for bringing people on board. We are always looking for the best people in their field, or people on their way to becoming exceptional at their jobs. This is so important to us, it's enshrined in our company [values](/handbook/values).
|
||||
- Manage compliance projects like SOC 2 or HIPAA to help us land larger customers. These projects require input from some small team members, but Ops will make sure everybody knows who and what is needed.
|
||||
- Partnering with the Exec team to work on people initiatives to build a diverse and inclusive culture at PostHog. We want to put a strong sense of belonging at the heart of everything we do.
|
||||
- Running any disciplinary or grievance [process](/handbook/people/grievances) that may occasionally arise.
|
||||
|
||||
@@ -137,7 +137,7 @@ When someone gives you feedback about your product, respond with something usefu
|
||||
|
||||
Failing to do so will teach them not to share more feedback in the future. If and when you do ship a fix, or the new feature they wanted, let them know.
|
||||
|
||||
> **What we’ve learned:** Don’t outsource this to a specific team – make it everyone’s responsibility. Reward helpful users with merch store discounts (also, have [a merch store](/merch!)) and early access to new features. We pull all feedback into a single Slack channel, so everyone sees it.
|
||||
> **What we’ve learned:** Don’t outsource this to a specific team – make it everyone’s responsibility. Reward helpful users with merch store discounts (also, have [a merch store](/merch)) and early access to new features. We pull all feedback into a single Slack channel, so everyone sees it.
|
||||
|
||||
## 8. Obsessing over competitors
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ crosspost:
|
||||
|
||||
Over the past 12 months, we have:
|
||||
|
||||
- Expanded our usage of [Temporal](/blog/temporal-exports) to power [warehouse syncs](/docs/data-warehouse/setup).
|
||||
- Expanded our usage of [Temporal](/blog/temporal-exports) to power [warehouse syncs](/docs/data-warehouse).
|
||||
|
||||
- Moved destinations and transformations away from Node virtual machines to our home-built HogVM in our own language, Hog.
|
||||
|
||||
@@ -114,7 +114,7 @@ An RFC outlines the "why" behind a technology decision and helps facilitate inpu
|
||||
|
||||
This isn't just a box to tick, it’s a core part of helping us choose the right technologies and [how we work asynchronously](https://newsletter.posthog.com/p/how-we-work-asynchronously).
|
||||
|
||||
Our RFC for adopting [Temporal at PostHog](https://github.com/PostHog/meta/pull/99) had 2,594 words, roughly 1/4 of the company as reviewers, 46 comments, and quite a bit of debate before finally being adopted. It's now happily in use for [batch exports](/blog/temporal-exports) and [warehouse syncs](/docs/data-warehouse/setup).
|
||||
Our RFC for adopting [Temporal at PostHog](https://github.com/PostHog/meta/pull/99) had 2,594 words, roughly 1/4 of the company as reviewers, 46 comments, and quite a bit of debate before finally being adopted. It's now happily in use for [batch exports](/blog/temporal-exports) and [warehouse syncs](/docs/data-warehouse).
|
||||
|
||||
|
||||
<Caption>The intro to James Greenhill’s RFC on adopting Temporal</Caption>
|
||||
|
||||
@@ -64,7 +64,7 @@ This brings us to our next point…
|
||||
|
||||
At a lower level, individual teams also have an idea of what all the potential features they can build are. To discover these, they use [user feedback](/product-engineers/10x-engineers-do-user-interviews), metrics, experience, product principles, and personal opinions.
|
||||
|
||||
Our small teams use their offsites to map these options. Below is an example of a [Team Replay](/small-teams/replay) 2x2 grid from a recent offsite (notes in the top right are high effort and high impact):
|
||||
Our small teams use their offsites to map these options. Below is an example of a [Team Replay](/teams/replay) 2x2 grid from a recent offsite (notes in the top right are high effort and high impact):
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -196,7 +196,7 @@ Even now, five years and 100+ people later, [our strategy](/handbook/why-does-po
|
||||
2. Build all the tools they need in one platform
|
||||
3. Get in first
|
||||
|
||||
Finally, early-stage companies often fall apart because the founders break up, so I'd recommend asking: "How do you and the other founders avoid falling out?" See [How to not break up with your cofounder](/newsletter/how-to-not-break-up-with-your-cofounder) for what to look for here.
|
||||
Finally, early-stage companies often fall apart because the founders break up, so I'd recommend asking: "How do you and the other founders avoid falling out?" See [How to not break up with your cofounder](/newsletter/how-to-not-breakup-with-your-cofounder) for what to look for here.
|
||||
|
||||
> **Remember:** The success of the company over the long run is a product of its vision now. Joining a team that knows where they want to go helps both them and you be successful.
|
||||
|
||||
|
||||
@@ -296,7 +296,7 @@ This one is hard to benchmark as the variation between features and companies is
|
||||
|
||||
## Further reading 📖
|
||||
|
||||
- [The most useful metrics for mobile apps](/blog/mobile-app-metrics-kpis)
|
||||
- [The most useful metrics for mobile apps](/product-engineers/mobile-app-metrics-kpis)
|
||||
- [An engineer’s guide to talking to users](/newsletter/talk-to-users)
|
||||
- [A software engineer's guide to A/B testing](/product-engineers/ab-testing-guide-for-engineers)
|
||||
|
||||
|
||||
@@ -148,6 +148,6 @@ Ultimately, using product health metrics should help you understand the well-bei
|
||||
|
||||
- [The most useful B2B SaaS product metrics](/blog/b2b-saas-product-metrics)
|
||||
- [Finding your North Star metric and why it matters](/blog/north-star-metrics)
|
||||
- [Actionable mobile app metrics you should track](/blog/mobile-app-metrics-kpis)
|
||||
- [Actionable mobile app metrics you should track](/product-engineers/mobile-app-metrics-kpis)
|
||||
|
||||
<NewsletterForm />
|
||||
|
||||
@@ -426,7 +426,7 @@ That's it! Feel free to play around in your dashboard and explore the different
|
||||
## Further reading
|
||||
|
||||
- [How to run A/B tests in Android](/tutorials/android-ab-tests)
|
||||
- [How to set up feature flags in Android](/tutorials/android-feaure-flags)
|
||||
- [How to set up feature flags in Android](/tutorials/android-feature-flags)
|
||||
- [How to set up session replays in Android](/tutorials/android-session-replay)
|
||||
|
||||
<NewsletterForm />
|
||||
@@ -173,5 +173,5 @@ You can also edit and save the remote config in PostHog and then press the **ref
|
||||
## Further reading
|
||||
|
||||
- [How to set up analytics in Android](/tutorials/android-analytics)
|
||||
- [How to run A/B tests in Android](/tutorials/android-ab-testing)
|
||||
- [How to run A/B tests in Android](/tutorials/android-ab-tests)
|
||||
- [Feature flags vs configuration: Which should you choose?](/product-engineers/feature-flags-vs-configuration)
|
||||
|
||||
@@ -230,7 +230,7 @@ Notice that when you refresh the page, the button text flickers between `Click m
|
||||
|
||||
Server-side rendering is a way to avoid this. This fetches the feature flag before the page loads on the client.
|
||||
|
||||
To set this up, we must install and use [PostHog’s Node library](/libraries/node) (because we are making server-side requests).
|
||||
To set this up, we must install and use [PostHog’s Node library](/docs/libraries/node) (because we are making server-side requests).
|
||||
|
||||
```bash
|
||||
npm install posthog-node
|
||||
|
||||
@@ -106,7 +106,7 @@ Press **F5** and run the app in any emulator (we chose Android) to see your app
|
||||
|
||||
With our app set up, it’s time to install and set up PostHog. If you don't have a PostHog instance, you can [sign up for free](https://us.posthog.com/signup).
|
||||
|
||||
To start, install [PostHog’s Flutter SDK](/libraries/flutter) by adding `posthog_flutter` to your `pubspec.yaml`:
|
||||
To start, install [PostHog’s Flutter SDK](/docs/libraries/flutter) by adding `posthog_flutter` to your `pubspec.yaml`:
|
||||
|
||||
```yaml file=pubspec.yaml
|
||||
# rest of your code
|
||||
|
||||
@@ -222,7 +222,7 @@ Our basic set up is now complete. Build and run your app to see it in action.
|
||||
|
||||
With our app set up, it’s time to install and set up PostHog. If you don't have a PostHog instance, you can [sign up for free](https://us.posthog.com/signup).
|
||||
|
||||
To start, install [PostHog’s Flutter SDK](/libraries/flutter) by adding `posthog_flutter` to your `pubspec.yaml`:
|
||||
To start, install [PostHog’s Flutter SDK](/docs/libraries/flutter) by adding `posthog_flutter` to your `pubspec.yaml`:
|
||||
|
||||
```yaml file=pubspec.yaml
|
||||
# rest of your code
|
||||
|
||||
@@ -152,7 +152,7 @@ All steps of the LLM chain are now tracked in Langfuse and you can view them in
|
||||
|
||||
## 4. Integrate Langfuse with PostHog
|
||||
|
||||
Next we [connect Langfuse to PostHog](/docs/ai-engineering/langfuse-posthog so that you can combine your LLM trace data with your PostHog analytics. This enables you to answer product questions such as:
|
||||
Next we [connect Langfuse to PostHog](/docs/ai-engineering/langfuse-posthog) so that you can combine your LLM trace data with your PostHog analytics. This enables you to answer product questions such as:
|
||||
|
||||
- What are my LLM costs by customer, model, and in total?
|
||||
- How many of my users are interacting with my LLM features?
|
||||
|
||||
@@ -61,7 +61,7 @@ Run `node server.js` and navigate to `http://localhost:3000` to see your app in
|
||||
|
||||
With our app set up, it’s time to install and set up PostHog. If you don't have a PostHog instance, you can [sign up for free](https://us.posthog.com/signup).
|
||||
|
||||
To start, install [PostHog’s Node library](/libraries/node):
|
||||
To start, install [PostHog’s Node library](/docs/libraries/node):
|
||||
|
||||
```bash
|
||||
npm install posthog-node
|
||||
|
||||
@@ -213,7 +213,7 @@ Notice that when you refresh the page, the button text flickers between `No vari
|
||||
|
||||
Server-side rendering is a way to avoid this. This fetches the feature flag before the page loads on the client.
|
||||
|
||||
To set this up, we must install and use [PostHog’s Node library](/libraries/node) (because we are making server-side requests).
|
||||
To set this up, we must install and use [PostHog’s Node library](/docs/libraries/node) (because we are making server-side requests).
|
||||
|
||||
```bash
|
||||
npm install posthog-node
|
||||
|
||||
@@ -189,4 +189,4 @@ Finally, we can test our app by reloading or running `npx expo start` again and
|
||||
|
||||
- [Feature flags vs configuration: Which should you choose?](/product-engineers/feature-flags-vs-configuration)
|
||||
- [How to set up analytics in React Native](/tutorials/react-native-analytics)
|
||||
- [How to set up A/B tests in React Native](/react-native-ab-tests)
|
||||
- [How to set up A/B tests in React Native](/tutorials/react-native-ab-tests)
|
||||
@@ -186,7 +186,7 @@ Notice that when you refresh the page, the button text flickers between `No vari
|
||||
|
||||
Server-side rendering is a way to avoid this. This fetches the feature flag before the page loads on the client.
|
||||
|
||||
To set this up, we must install and use [PostHog’s Node library](/libraries/node) (because we are making server-side requests).
|
||||
To set this up, we must install and use [PostHog’s Node library](/docs/libraries/node) (because we are making server-side requests).
|
||||
|
||||
```bash
|
||||
npm install posthog-node
|
||||
|
||||
@@ -179,7 +179,7 @@ Notice that when you refresh the page, the button text flickers between `No vari
|
||||
|
||||
Server-side rendering is a way to avoid this. This fetches the feature flag before the page loads on the client.
|
||||
|
||||
To set this up, we must install and use [PostHog’s Ruby SDK](/libraries/ruby) (because we are making server-side requests). Add `posthog-ruby` to your `Gemfile`:
|
||||
To set this up, we must install and use [PostHog’s Ruby SDK](/docs/libraries/ruby) (because we are making server-side requests). Add `posthog-ruby` to your `Gemfile`:
|
||||
|
||||
```Gemfile
|
||||
gem "posthog-ruby"
|
||||
|
||||
@@ -176,7 +176,7 @@ Notice that when you refresh the page, the button text flickers between `No vari
|
||||
|
||||
Server-side rendering is a way to avoid this. This fetches the feature flag before the page loads on the client.
|
||||
|
||||
To set this up, we must install and use [PostHog’s Node library](/libraries/node) (because we are making server-side requests).
|
||||
To set this up, we must install and use [PostHog’s Node library](/docs/libraries/node) (because we are making server-side requests).
|
||||
|
||||
```bash
|
||||
npm install posthog-node
|
||||
|
||||
48
vercel.json
48
vercel.json
@@ -1471,6 +1471,54 @@
|
||||
{
|
||||
"source": "/docs/privacy/data-deletion",
|
||||
"destination": "/docs/privacy/data-storage#data-deletion"
|
||||
},
|
||||
{
|
||||
"source": "/manual/funnels",
|
||||
"destination": "/docs/product-analytics/funnels"
|
||||
},
|
||||
{
|
||||
"source": "/manual/lifecycle",
|
||||
"destination": "/docs/product-analytics/lifecycle"
|
||||
},
|
||||
{
|
||||
"source": "/manual/paths",
|
||||
"destination": "/docs/product-analytics/paths"
|
||||
},
|
||||
{
|
||||
"source": "/manual/correlation",
|
||||
"destination": "/docs/product-analytics/correlation"
|
||||
},
|
||||
{
|
||||
"source": "/manual/experimentation",
|
||||
"destination": "/docs/experiments"
|
||||
},
|
||||
{
|
||||
"source": "/manual/retention",
|
||||
"destination": "/docs/product-analytics/retention"
|
||||
},
|
||||
{
|
||||
"source": "/manual/feature-flags",
|
||||
"destination": "/docs/feature-flags"
|
||||
},
|
||||
{
|
||||
"source": "/manual/annotations",
|
||||
"destination": "/docs/data/annotations"
|
||||
},
|
||||
{
|
||||
"source": "/manual/dashboards",
|
||||
"destination": "/docs/product-analytics/dashboards"
|
||||
},
|
||||
{
|
||||
"source": "/manual/stickiness",
|
||||
"destination": "/docs/product-analytics/stickiness"
|
||||
},
|
||||
{
|
||||
"source": "/manual/insights",
|
||||
"destination": "/docs/product-analytics/insights"
|
||||
},
|
||||
{
|
||||
"source": "/manual/trends",
|
||||
"destination": "/docs/product-analytics/trends"
|
||||
}
|
||||
],
|
||||
"headers": [
|
||||
|
||||
Reference in New Issue
Block a user