Sales enablement docs for error tracking, workflows, and logs#17014
Open
SaraMiteva wants to merge 8 commits into
Open
Sales enablement docs for error tracking, workflows, and logs#17014SaraMiteva wants to merge 8 commits into
SaraMiteva wants to merge 8 commits into
Conversation
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 0 errors, 193 warnings, 0 suggestions in your markdown Full report → Copy the linter results into an LLM to batch-fix issues. Linter being weird? Update the rules!
|
| Line | Severity | Message | Rule |
|---|---|---|---|
| 2:8 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'Error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 7:19 | warning | 'Miteva' is a possible misspelling. | PostHogBase.Spelling |
| 11:160 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 11:166 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 11:185 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 13:19 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 13:173 | warning | Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. | PostHogBase.ProductNames |
| 19:6 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 21:103 | warning | Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. | PostHogBase.ProductNames |
| 25:61 | warning | 'Bugsnag' is a possible misspelling. | PostHogBase.Spelling |
| 25:73 | warning | 'Rollbar' is a possible misspelling. | PostHogBase.Spelling |
| 30:35 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 35:35 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 35:100 | warning | 'symbolicate' is a possible misspelling. | PostHogBase.Spelling |
| 42:19 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 42:233 | warning | 'triaging' is a possible misspelling. | PostHogBase.Spelling |
| 44:117 | warning | Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. | PostHogBase.ProductNames |
| 48:38 | warning | Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. | PostHogBase.ProductNames |
| 53:5 | warning | 'Message 2: Drop Sentry, Bugsnag, or Rollbar' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 53:29 | warning | 'Bugsnag' is a possible misspelling. | PostHogBase.Spelling |
| 53:41 | warning | 'Rollbar' is a possible misspelling. | PostHogBase.Spelling |
| 55:69 | warning | 'Bugsnag' is a possible misspelling. | PostHogBase.Spelling |
| 55:78 | warning | 'Rollbar' is a possible misspelling. | PostHogBase.Spelling |
| 55:148 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 55:163 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 61:25 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 61:33 | warning | Use 'CLI' instead of 'cli'. | Vale.Terms |
| 61:42 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 62:31 | warning | 'Bugsnag' is a possible misspelling. | PostHogBase.Spelling |
| 62:43 | warning | 'Rollbar' is a possible misspelling. | PostHogBase.Spelling |
| 68:20 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 81:5 | warning | 'vs Sentry' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 83:259 | warning | 'Autofix' is a possible misspelling. | PostHogBase.Spelling |
| 86:40 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 86:59 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 86:78 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 86:157 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 87:12 | warning | 'triages' is a possible misspelling. | PostHogBase.Spelling |
| 89:40 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 89:92 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 95:5 | warning | 'vs Bugsnag and Rollbar' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 95:8 | warning | 'Bugsnag' is a possible misspelling. | PostHogBase.Spelling |
| 95:20 | warning | 'Rollbar' is a possible misspelling. | PostHogBase.Spelling |
| 97:32 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 97:60 | warning | 'Rollbar' is a possible misspelling. | PostHogBase.Spelling |
| 97:169 | warning | Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. | PostHogBase.ProductNames |
| 97:262 | warning | 'Rollbar' is a possible misspelling. | PostHogBase.Spelling |
| 97:390 | warning | 'Bugsnag' is a possible misspelling. | PostHogBase.Spelling |
| 100:105 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 100:118 | warning | Capitalize 'Surveys' for PostHog's product. Use 'surveys' for the general industry concept. | PostHogBase.ProductNames |
| 100:127 | warning | 'Rollbar' is a possible misspelling. | PostHogBase.Spelling |
| 100:139 | warning | 'Bugsnag' is a possible misspelling. | PostHogBase.Spelling |
| 101:45 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 101:82 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 102:18 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 102:73 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 105:5 | warning | 'vs Datadog' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 110:96 | warning | 'SREs' is a possible misspelling. | PostHogBase.Spelling |
| 111:38 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 111:77 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 111:134 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 113:40 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 113:95 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 117:5 | warning | '"Sentry has deeper SDK coverage, more mature grouping, and now ships session replay, logs, tracing, AI, and MCP too. What's actually different?"' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 117:74 | warning | Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. | PostHogBase.ProductNames |
| 117:90 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 121:58 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 121:83 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 121:448 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 121:512 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 121:525 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 121:633 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 123:5 | warning | '"We're a mobile-first app. PostHog's iOS error tracking has documented gaps."' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 123:46 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 127:78 | warning | 'symbolicated' is a possible misspelling. | PostHogBase.Spelling |
| 127:418 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 127:460 | warning | Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. | PostHogBase.ProductNames |
| 127:476 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 127:491 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 129:5 | warning | '"Sentry is cheaper than PostHog at high volume – their volume discounts drop errors to $0.000150 each at 20M+."' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 133:327 | warning | 'reframe' is a possible misspelling. | PostHogBase.Spelling |
contents/handbook/marketing/how-we-position-and-sell/logs.md — 0 errors, 68 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 7:19 | warning | 'Miteva' is a possible misspelling. | PostHogBase.Spelling |
| 11:71 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 11:251 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 13:116 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 17:215 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 19:96 | warning | Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. | PostHogBase.ProductNames |
| 19:209 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 25:74 | warning | 'OTel' is a possible misspelling. | PostHogBase.Spelling |
| 26:47 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 39:178 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 41:154 | warning | Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. | PostHogBase.ProductNames |
| 44:48 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 47:10 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 48:50 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 52:116 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 52:141 | warning | Use 'Fullstory' instead of 'FullStory'. | Vale.Terms |
| 54:63 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 54:96 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 54:115 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 59:36 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 61:19 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 65:51 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 74:67 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 78:5 | warning | 'vs Datadog (and New Relic)' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 80:124 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 83:69 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 83:121 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 84:18 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 88:5 | warning | 'vs Grafana Loki and Grafana Cloud Logs' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 90:259 | warning | 'queryless' is a possible misspelling. | PostHogBase.Spelling |
| 94:18 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 94:43 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 94:102 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 98:5 | warning | 'vs Better Stack' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 100:72 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 100:93 | warning | 'OTel' is a possible misspelling. | PostHogBase.Spelling |
| 100:114 | warning | Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. | PostHogBase.ProductNames |
| 100:144 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 103:29 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 103:101 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 104:18 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 104:36 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 104:129 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 105:114 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 106:50 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 106:63 | warning | Capitalize 'Surveys' for PostHog's product. Use 'surveys' for the general industry concept. | PostHogBase.ProductNames |
| 106:78 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 110:5 | warning | '"You don't have distributed tracing or metrics. We need full observability."' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 112:82 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 114:172 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 114:316 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 114:334 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 114:353 | warning | Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. | PostHogBase.ProductNames |
| 114:369 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 114:389 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 116:90 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 118:5 | warning | '"Better Stack claims 30x cheaper than Datadog and has MCP, AI SRE, and a full observability + IRM bundle. What makes PostHog different?"' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 122:389 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 122:436 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 122:562 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 124:43 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 128:222 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 128:295 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 130:61 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 130:155 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 132:5 | warning | '"PostHog feels like a web/frontend/analytics company. Can you handle our backend logs?"' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 132:86 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 136:485 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
contents/handbook/marketing/how-we-position-and-sell/workflows.md — 0 errors, 44 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 7:19 | warning | 'Miteva' is a possible misspelling. | PostHogBase.Spelling |
| 11:180 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 11:265 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 13:247 | warning | 'Grantable' is a possible misspelling. | PostHogBase.Spelling |
| 17:245 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 19:301 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 29:185 | warning | 'Suped' is a possible misspelling. | PostHogBase.Spelling |
| 30:124 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 40:45 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 44:99 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 63:51 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 67:280 | warning | Use 'RudderStack' instead of 'Rudderstack'. | Vale.Terms |
| 69:199 | warning | 'Grantable' is a possible misspelling. | PostHogBase.Spelling |
| 69:314 | warning | 'Suped' is a possible misspelling. | PostHogBase.Spelling |
| 79:5 | warning | 'vs Zapier (and Make)' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 86:38 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 87:47 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 88:3 | warning | 'Grantable' is a possible misspelling. | PostHogBase.Spelling |
| 90:5 | warning | 'vs Customer.io' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 97:27 | warning | Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. | PostHogBase.ProductNames |
| 97:47 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 98:4 | warning | 'Suped' is a possible misspelling. | PostHogBase.Spelling |
| 101:5 | warning | 'vs Brevo (and ActiveCampaign, Mailchimp)' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 107:38 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 107:56 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 111:5 | warning | 'vs Iterable / Braze' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 113:183 | warning | 'decisioning' is a possible misspelling. | PostHogBase.Spelling |
| 113:260 | warning | 'Gartner' is a possible misspelling. | PostHogBase.Spelling |
| 113:354 | warning | 'Wyndham' is a possible misspelling. | PostHogBase.Spelling |
| 113:375 | warning | 'Canva' is a possible misspelling. | PostHogBase.Spelling |
| 119:42 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 124:5 | warning | '"Customer.io / Brevo has more mature email features – open/click/bounce tracking, suppression lists, dedicated IPs. You don't."' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 124:116 | warning | 'IPs' is a possible misspelling. | PostHogBase.Spelling |
| 128:420 | warning | 'IPs' is a possible misspelling. | PostHogBase.Spelling |
| 130:19 | warning | 'Suped' is a possible misspelling. | PostHogBase.Spelling |
| 132:5 | warning | '"You don't have native mobile push or WhatsApp. Iterable and Braze do."' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 142:96 | warning | 'Calendly' is a possible misspelling. | PostHogBase.Spelling |
| 142:170 | warning | 'automations' is a possible misspelling. | PostHogBase.Spelling |
| 144:18 | warning | 'Grantable' is a possible misspelling. | PostHogBase.Spelling |
| 150:120 | warning | Capitalize 'Data Pipelines' for PostHog's product. Use 'data pipelines' for the general industry concept. | PostHogBase.ProductNames |
| 150:136 | warning | 'GA'd' is a possible misspelling. | PostHogBase.Spelling |
| 150:443 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 150:485 | warning | 'OAuth' is a possible misspelling. | PostHogBase.Spelling |
| 152:18 | warning | 'Grantable's' is a possible misspelling. | PostHogBase.Spelling |
joethreepwood
approved these changes
May 26, 2026
Contributor
joethreepwood
left a comment
joethreepwood
left a comment
There was a problem hiding this comment.
Some thoughts and notes to address, but nothing here that's a real blocker from me. Thanks, Sara!
|
|
||
| Most error tracking tools give you a stack trace, a frequency count, and a release tag. They don't tell you which user hit the error, what they were trying to do, or whether it matters to the business. So engineers triage by error count instead of by user impact, and waste cycles on noisy errors that don't affect anyone real. | ||
|
|
||
| Every PostHog exception is a product event with the user attached. Click an error to watch the user's session replay. Filter exceptions by feature flag variant, plan tier, or revenue cohort. See the business impact next to the stack trace. Sentry has the deeper SDK coverage but doesn't know your users, while Bugsnag and Rollbar are similar with good error capture, no product context. PostHog Error Tracking is the only place where every error already knows who hit it, what they were doing, and whether it matters. |
Contributor
There was a problem hiding this comment.
Soft steer, but I think our unique belief should exclude competitors. A unique belief is what WE believe, not how we differentiate from competitors (which is more elevator pitch). I think this should come from a place of opinion, principle, and vision. Not "Like Sentry, but"
Comment on lines
+95
to
+97
| ### vs Bugsnag and Rollbar | ||
|
|
||
| **Their approach:** Mid-market error tracking specialists. Rollbar positions as *"code-first observability that connects errors, replays, and releases in one place"* – session replay shipped, MCP integration, RQL query language, Root Cause Analysis AI shipped, Rollbar Resolve AI agent (opens PRs with fixes) coming soon. Free tier: 5K occurrences + 1K replays. SOC2 + ISO27001 certified. Bugsnag (SmartBear-owned) follows a similar mid-market specialist playbook, historically strong on mobile crash reporting. |
Contributor
There was a problem hiding this comment.
Don't think this is wrong, but curious on why you've grouped these two?
Contributor
Author
There was a problem hiding this comment.
There are some competitors that have a similar approach to marketing and I think our response should be the same, so I figured it would be easier for the sales team. I did that for DDog and New Relic in another doc as well I think
|
|
||
| ## The unique belief | ||
|
|
||
| PostHog's vision is a self-driving product: software that watches itself for bugs and conversion drops, then ships the fix while you sleep. That loop needs three things – signals, action, and the *context* that tells which signals actually matter. Most observability tools generate plenty of signals (events, errors, latency, logs) without the product context that makes them actionable. |
Contributor
There was a problem hiding this comment.
We should probably avoid saying signals to avoid confusion with that as a team/system for us.
|
|
||
| PostHog's vision is a self-driving product: software that watches itself for bugs and conversion drops, then ships the fix while you sleep. That loop needs three things – signals, action, and the *context* that tells which signals actually matter. Most observability tools generate plenty of signals (events, errors, latency, logs) without the product context that makes them actionable. | ||
|
|
||
| Logs are the backend half of the signal layer. But most observability tools treat them as text – timestamps, severity, message, search. You find the right log, then bounce to another tool to figure out who was affected, which feature flag was on, or what they were trying to do when it broke. The signal is in the data; the *meaning* is somewhere else. |
Contributor
There was a problem hiding this comment.
Not sure I follow the final clause here. It feels a bit wishy-washy.
|
|
||
| PostHog's vision is a [self-driving product](https://posthog.com/blog/self-driving-product): software that watches itself for bugs and conversion drops, then ships the fix while you sleep. The signal layer is well-covered with errors, replays, logs, analytics. What closes the loop is what happens next. Knowing a checkout error hit your top customer doesn't matter if no one is paged. The systems that act on signals almost always live somewhere else, behind a CDP or homegrown glue. | ||
|
|
||
| Workflows is the act layer. Every event, cohort change, error spike, or ticket update can trigger a multi-step flow, including sending a message and updating a person property, without leaving the platform the signal came from. PostHog AI drafts email copy today; soon, agents will design and revise workflows through MCP. |
| - **Engineer-led teams building product-led growth motions.** They want to act on product events – onboarding milestones, activation drop-offs, feature usage – without a CDP in the middle. | ||
| - **B2B teams running intent-signal automation.** Triggering sales follow-ups, Slack alerts, or Linear tickets directly from product behavior, not delayed by CRM syncs. ([Croissant does this.](https://posthog.com/customers/croissant)) | ||
| - **Startups consolidating their messaging stack.** Workflows replaces Zapier + Customer.io + a CDP. | ||
| - **Customers on Customer.io, Iterable, Brevo, or ActiveCampaign for transactional and onboarding email.** Especially when most of the trigger logic already lives in product events. (Suped migrated off Customer.io.) |
Contributor
There was a problem hiding this comment.
Do we have a reference for suped?
|
|
||
| ## Battle cards | ||
|
|
||
| ### vs Zapier (and Make) |
Contributor
There was a problem hiding this comment.
I wonder if N8N is a better comparison here than Make?
Co-authored-by: Joe Martin <84011561+joethreepwood@users.noreply.github.com>
hpouillot
approved these changes
May 27, 2026
Contributor
hpouillot
left a comment
hpouillot
left a comment
There was a problem hiding this comment.
Few comments but It looks good for the ET part ! Some context on what is coming: Better issue grouping is planned for the coming weeks and also one feature that might interesting for large customer is: per-issue rate limiting. It is still a work in progress, but large customers could reduce drastically their bill at scale.
|
|
||
| PostHog's vision is a self-driving product: software that watches itself for bugs, ships the fixes, and prioritizes work by user impact, not error volume. That loop needs every error to know which user hit it. | ||
|
|
||
| Most error tracking tools give you a stack trace, a frequency count, and a release tag. They don't tell you which user hit the error, what they were trying to do, or whether it matters to the business. So engineers triage by error count instead of by user impact, and waste cycles on noisy errors that don't affect anyone real. |
Contributor
There was a problem hiding this comment.
Yes ! I think this part is really important. Right now priorities are mainly surfaced in signal inbox but we are working on something that can leverage the whole exception context to increase signal / noise ratio
| - **Engineering teams who want to triage by user impact, not error volume.** "This exception is breaking checkout for your top-paying customers" beats "this exception happened 200 times in 5 minutes." | ||
| - **Multi-language stacks running web + mobile + backend.** Native SDKs for Node, Python, Go, Ruby, Rails, Elixir, NestJS; iOS, Android, React Native, Flutter; plus every major frontend framework. | ||
| - **Founders and small engineering teams shipping production code.** Generous free tier; no contract negotiation to start. | ||
| - **Teams running rollouts behind feature flags.** Roll back the flag that caused the spike from the same dashboard. |
Contributor
There was a problem hiding this comment.
For now, this is one is not really obvious. We need to add a better integration with feature flags / experiments.
| ### Who this isn't for | ||
|
|
||
| - Teams that need full feature parity with Sentry – Sentry has deeper SDK coverage, more mature grouping, and a longer track record. | ||
| - Teams whose primary need is iOS error tracking at full fidelity – the iOS implementation doesn't symbolicate system frames yet, and Swift crashes appear as SIGTRAP. |
Contributor
There was a problem hiding this comment.
The swift crash symbolication has been fixed in recent release but not the system frames yet.
| **Solution:** PostHog Error Tracking replaces standalone error trackers – same SDK coverage on the languages that matter, with the user, session, replay, and flag context already attached. No CDP middleware, no identity stitching. | ||
|
|
||
| **Supporting features:** | ||
| - Native SDKs for Node, Python, Go, Ruby, Rails, Elixir, NestJS; iOS, Android, React Native, Flutter; plus every major frontend framework |
Contributor
There was a problem hiding this comment.
We added PHP recently as well
|
|
||
| **Supporting features:** | ||
| - Native SDKs for Node, Python, Go, Ruby, Rails, Elixir, NestJS; iOS, Android, React Native, Flutter; plus every major frontend framework | ||
| - Source map upload via posthog-cli and @posthog/nextjs-config |
Contributor
There was a problem hiding this comment.
via cli or bundlers plugin (support for nextjs, vite, rollup, webpack)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Created the sales enablement docs for error tracking, workflows, and logs based on Joe's template, as discussed during the offsite.