-
Notifications
You must be signed in to change notification settings - Fork 402
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
Default to 100% person profiles ON, notice for cheaper analytics in slider #8823
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
return ( | ||
<> | ||
<SideModal open={modalOpen} setOpen={setModalOpen}> | ||
<h3 className="mb-2">Save money if you don't need PII</h3> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shouldn't use the term PII here as it has a specific connotation for privacy/security regulations and we mean something different. I think the key feature here is merges in terms of helping people qualify/disqualify this feature as buyers.
<h3 className="mb-2">Save money if you don't need PII</h3> | |
<h3 className="mb-2">Save money if you don't need to merge user identities across time</h3> | |
<p className="font-semibold opacity-70 text-[15px]">Merging users across cookies/devices/codebases is more expensive for us to process.</p> | |
<p>For most use cases with anonymous traffic (eg traditional Web Analytics, landing pages, Ecommerce), it costs us less to process events, so we pass that savings along to you.</p> | |
<p>If you are a traditional logged-in or b2b SaaS product, you probably need Person Profiles</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair, but I also think "merge user identities across time" is a bit high-brow, especially at this stage. (Unless you think this is a commonly-understood term from web analytics buyers? I don't have that context - just a hunch.)
Save money if you don't need to... track individual users(?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not think we should default this to 100%. That doesn't reflect any use-case we are trying to meet here.
How is this not the expected config for almost every b2b saas / standard "Product Analytics" use case? (think about what percentage of people are coming from competitors to get an apples to apples comparison) @raquelmsmith |
Why don't we get this in for now to avoid current confusion CS is hearing from potential customers, then we can address the root of it in whatever we decide in https://github.com/PostHog/company-internal/issues/1421? But regardless, we set the threshold pretty low so it will trigger for pretty much anyone who interacts with it, thus revealing how to get it cheaper. |
Every b2b saas company has a website that they are probably tracking with GA or something else, ya? |
Yes, definitely, they need personless even though they might not know it. And the buying decision for the website and internal product are rarely (in my experience selling here) made at the same time, or given the same weight in choosing amongst competitors. For small teams or startups, that may well be considered early on, but for any company > 10 or 20 people, there is one team driving the decision, usually a product or eng team. And given that Product Analytics is our flagship product, those buyers are the most qualified and, unfortunately, stand to be the most confused / misled by the current framing. |
Closing in lieu of #8844 |
Replaced by #8929 |
Move the slider and you'll see a notice about how to get cheaper analytics.
Click it and you'll get a panel explaining the use cases and if you're able to get cheaper analytics.
The messaging in this callout can be consolidated with the "help me calculate this" language, but we can clean this all up after we figure out what we're doing with the blog post. And I'm also planning an add-ons section of the pricing tab where we go into detail about how each of the add-ons work, this being one of them (with visualizations and all).