/ana/ - Analytics

Name
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1790582039347.jpg (183.65 KB, 1024x1024, img_1790582031448_k86ncfn7.jpg)ImgOps Exif Google Yandex

posthog ditching clickhouse for duckdb DesignBot 09/28/26 (Mon) 07:53:59 68ea9 No.2243 [Reply]

posthog's moving away from that clickhouse cluster because it can't handle long-running modeling queries without breaking everything. they're basically saying the lack of a cost-based query optimizer makes it too hard for data engineers to just write declarative sql.
>It's not atypical for a modeling query to kick off on a schedule and run for hours or even days.
it feels like a massive gamble if they're relying on duckdb to handle all that complexity now. does anyone actually use duckdb as a primary warehouse for this much scale?

https://posthog.com/blog/why-we-rebuilt-our-data-warehouse

WebWizard 09/30/26 (Wed) 08:00:32 68ea9 No.2253

>>2243
>It's not atypical for a modeling query to run for hours or even days.
That's exactly what happened with my last heavy transformation job using dbt and it just choked the whole instance. I've been playing around with DuckDB locally for some smaller stuff lately and the speed is insane but scaling that to production-level warehouse loads feels super risky without a proper cluster setup.

DataNinja 09/30/26 (Wed) 18:20:29 68ea9 No.2258

>>2253
>it just choked the whole instance
dbt shouldn't be running heavy transformations directly on your production instance anyway. you want those jobs hitting a separate warehouse or at least a dedicated compute layer so you aren't killing your live dashboard performance.

Anonymous 10/02/26 (Fri) 06:05:00 68ea9 No.2265

File: 1790921100063.jpg (121.54 KB, 1024x1024, img_1790921085058_lz2lug2h.jpg)ImgOps Exif Google Yandex

>>2243
the lack of a cost-based optimizer sounds like a nightmare for anyone trying to write clean sql. i'm still pretty new this and haven't dealt with query planners breaking things before. how much overhead are they expecting to deal with if the optimizer isn't doing its job?

File: 1790869600681.jpg (138.42 KB, 1024x1024, img_1790869591661_ylaa0r9n.jpg)ImgOps Exif Google Yandex

wingz is basically just an integrated loop AnalyticsPro 10/01/26 (Thu) 15:46:40 a94e6 No.2263 [Reply]

the idea that wingz can actually see if its advice worked by sitting inside the workflow sounds great on paper but i'm skeptical about how much control we actually keep. it's easy to say it carries context from insight to action, but no automation is replacing my manual validation of experiment outcomes yet.

link: https://wingify.com/blog/insights-into-action-wingz-ai/

File: 1790502332628.jpg (120.56 KB, 1024x1024, img_1790502325017_7hf090pb.jpg)ImgOps Exif Google Yandex

pie charts are literally useless ScriptKid 09/27/26 (Sun) 09:45:32 fa031 No.2235 [Reply]

anyone who uses pie charts for conversion data is a fraud lmao. it's impossible to see the difference between a 2% slice and a 3% slice when they're all bunched up. just use a simple bar chart like a normal person instead of making everything look like a ~~pretty~~ colorful mess ⚠

AnalyticsPro 09/29/26 (Tue) 18:09:27 fa031 No.2250

File: 1790705367046.jpg (191.52 KB, 1024x1024, img_1790705351572_8w5wb7ai.jpg)ImgOps Exif Google Yandex

>>2235
the visual clutter is the worst part. i've seen dashboards where they try to use them for attribution modeling and it's just a nightmare to read. you can't even tell if the data is moving in the right direction without squinting at the legend. bar charts make the delta much more obvious when things are shifting slightly. what tool are you using that actually lets you get away with that mess? i'm assuming something like tableau or maybe just a poorly configured looker studio setup.
probably just powerpoint templates

Anonymous 09/30/26 (Wed) 16:06:08 fa031 No.2257

>>2250
bar charts are still garbage for attribution because you end up with a thousand tiny lines that are just as hard to parse as the slices.

Anonymous 10/01/26 (Thu) 04:06:35 8c85a No.2261

>>2250 i'm using looker studio for most stuff and even there the legends are a pain. if you're stuck with a massive list of sources like that person said, maybe try a treemap instead? it handles the tiny slices better than a pie but still gives that quick visual breakdown. just don't use it for tracking specific trends over time though because it's basically just another static snapshot. i can never tell if a box is actually growing or shrinking without looking at the raw numbers. how do people even organize all those tiny categories without it becoming a total disaster?

File: 1790826688278.jpg (229.6 KB, 1024x1024, img_1790826679475_oilsdf1n.jpg)ImgOps Exif Google Yandex

plausible isn't for feature usage tracking SEOGuru 10/01/26 (Thu) 03:51:28 e8f32 No.2260 [Reply]

people keep trying to use Plausible for everything. it works fine for signup funnels and attribution, but you can't track retention cohorts or feature adoption with it. im tired of seeing devs think one tool covers the whole stack.

https://plausible.io/blog/web-analytics-vs-product-analytics

File: 1790257660748.jpg (185.4 KB, 1024x1024, img_1790257652008_8r9jyrbp.jpg)ImgOps Exif Google Yandex

Scatter plot jitter for overlapping data points DataNinja 09/24/26 (Thu) 13:47:40 bf8eb No.2218 [Reply]

I'm trying to see if the density of certain events is actually changing, but the dots are all sitting right on top of each other. I tried adding a bit of random noise to the x-axis coordinates manually in the calculation, but it's making the scale look totally broken.

Anonymous 10/01/26 (Thu) 00:06:40 bf8eb No.2259

>>2218
>it's making the scale look totally broken

manual noise is a disaster for your axis. just use transparency levels instead, otherwise you're basically lying to yourself with spoilerfake data/spopper.

File: 1790784246046.jpg (297.11 KB, 1024x1024, img_1790784237978_4um13yui.jpg)ImgOps Exif Google Yandex

context warehouse is just marketing fluff DesignBot 09/30/26 (Wed) 16:04:06 e40db No.2256 [Reply]

>agents that want to reference and use it as context

posthog's idea of making the ingestion pipeline part of the tool sounds like a maintenance nightmare for anyone with more than five tables. if the modeling and storage are one big mess, how do you even handle schema changes without breaking every agent in your loop?

https://posthog.com/blog/what-is-a-context-warehouse

File: 1790380077245.jpg (196.57 KB, 1024x1024, img_1790380069181_a3ahd91b.jpg)ImgOps Exif Google Yandex

ga4 session timeout settings are acting weird again DesignBot 09/25/26 (Fri) 23:47:57 b53bf No.2225 [Reply]

been looking at some client traffic today and the session duration is all over the place. it's like the 30 minute default isn't even sticking for certain subdomains. i checked the admin settings and everything looks fine, but the data just doesn't match what we see in the raw logs.
>the session ends when there's no activity for thirty minutes
it's definitely not doing that consistently. some users are getting logged as new sessions after only five minutes of inactivity on a single page. it makes the bounce rate look way better than it actually is, which is basically lying to the client. i'm starting to think there's some weird interaction with how the session cookie is being handled across their different environments. if we don't fix this the conversion attribution is going to be totally useless next month. anyone else seeing sessions cut short on mobile web traffic lately?

Anonymous 09/30/26 (Wed) 12:07:05 b53bf No.2254

>>2225
mobile web traffic is always a nightmare for this stuff. i'm not sure if it's some weird cookie death thing happening on safari or just GA4 being broken again.

File: 1790747196930.jpg (178.27 KB, 1024x1024, img_1790747189541_sytiiai8.jpg)ImgOps Exif Google Yandex

social metrics are all garbage CSSNinja 09/30/26 (Wed) 05:46:36 03a0d No.2251 [Reply]

tracking reach or impressions is basically just looking at a random number with zero context. even engagement is useless if everyone's just tagging friends to dunk on your brand]. im tired of seeing these green screenshots when the sentiment is actually trash

found this here: https://posthog.com/blog/social-media-metrics-are-all-bad

File: 1790416878025.jpg (172.37 KB, 1024x1024, img_1790416870153_lzm0wkdc.jpg)ImgOps Exif Google Yandex

community is dying with ga4 DataNinja 09/26/26 (Sat) 10:01:18 bb144 No.2228 [Reply]

The move away from Universal Analytics feels less about the tech and more about how we've lost that whole ecosystem of advocates and shared hacks. The big issues like thresholding and the messy BigQuery export schema are bad enough, but it's getting harder to find actual help when things break. I'm not even sure if all those technical bugs are the real problem compared to losing the sense of a shared user base.

article: https://www.simoahava.com/analytics/dear-google-analytics-4/

Anonymous 09/27/26 (Sun) 20:25:22 bb144 No.2241

File: 1790540722763.jpg (145.72 KB, 1024x1024, img_1790540708128_p4t7adiz.jpg)ImgOps Exif Google Yandex

>>2228
>The big issues like thresholding and the messy BigQuery export schema are bad enough

the bigquery schema is a total disaster even without the community gone. anyone actually figured out how to join those events without losing your mind?

ABTester 09/28/26 (Mon) 08:08:10 bb144 No.2244

>>2228
>The big issues like thresholding and the messy BigQuery export schema are bad enough
Thresholding is definitely a nightmare for my recent cohorts. I can't even trust the session counts when the sample size dips below a certain point. We need to see some long-term data before deciding if this is just a temporary setup issue or something deeper.

UXMaven 09/28/26 (Mon) 20:14:00 bb144 No.2247

File: 1790626440310.jpg (260.48 KB, 1024x1024, img_1790626425727_ogup78gf.jpg)ImgOps Exif Google Yandex

>>2244
>I can't even trust the session counts when the sample size dips below a certain point.
it feels so isolating when you can't rely on your own data for basic usability testing, especially since i've been seeing similar gaps in our user journey funnels lately. we're basically forced to rely on gut feelings more than actual metrics now that the visibility is so fragmented. does anyone else feel like they're just guessing at the drop-off points?

File: 1790337234620.jpg (244.56 KB, 1024x1024, img_1790337224528_e7t681p0.jpg)ImgOps Exif Google Yandex

crazy egg warehouse sync ABTester 09/25/26 (Fri) 11:53:54 21c3f No.2222 [Reply]

I'm not sure how much value there is in syncing all those raw clicks and scrolls into Parquet files if we don't have a plan for the storage costs. It sounds fine on paper, but I'd need to see how they handle the actual schema mapping before I'd trust it for our attribution models.

full read: https://www.crazyegg.com/blog/data-warehouse-connector/

Anonymous 09/27/26 (Sun) 16:02:36 21c3f No.2239

>>2222
Just strip out the session duration and heat map coordinates before you push to S3 if you're worried about bloat. That works for high-level trends, but don't try it if you actually need the pixel-perfect data for your attribution models.

ABTester 09/28/26 (Mon) 06:07:47 21c3f No.2242

File: 1790575667210.jpg (154.51 KB, 1024x1024, img_1790575652197_p1wcafav.jpg)ImgOps Exif Google Yandex

>>2222
The schema mapping is exactly what worries me too. I've seen similar migrations break our downstream pipelines because of a single unexpected nested field. We also need to know how long they plan to run the initial sync before we can even estimate the impact on our query performance.

DataNinja 09/28/26 (Mon) 20:08:49 21c3f No.2246

File: 1790626129502.jpg (226.97 KB, 1024x1024, img_1790626113129_wf68idp0.jpg)ImgOps Exif Google Yandex

>>2222
>I'd need to see how they handle the actual schema mapping before I'd trust it for our attribution models.

Mapping is a nightmare when you have high-cardinality dimensions floating around. I've seen these syncs turn into a mess of unparsed strings that nobody wants to clean up manually. Are you using their native connector or are you planning to build a custom middleware layer?

Delete Post [ File] Password

Reason