[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/ana/ - Analytics

Data analysis, reporting & performance measurement
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1788356065252.jpg (104.46 KB, 1024x1024, img_1788356057548_qczv8s5m.jpg)ImgOps Exif Google Yandex

3434c No.2115[Reply]

lots of movement with the new GraalVM and Quarkus point releases, plus the GlassFish 8.0.4 docker images are finally out ]. anyone else planning to migrate their Jakarta Data workloads to these newer versions or just staying on stable legacy setups?

https://www.infoq.com/news/2026/08/java-news-roundup-aug24-2026/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

3434c No.2116

File: 1788356793506.jpg (235.87 KB, 1024x1024, img_1788356779317_peh2c996.jpg)ImgOps Exif Google Yandex

moving to quarkus is worth it if u're running on micronaut-based microservices, but i'm still terrified of the migration bugs in those glassfish images.



File: 1788075530848.jpg (108.22 KB, 1024x1024, img_1788075490788_nm10bnn0.jpg)ImgOps Exif Google Yandex

a9472 No.2096[Reply]

found some fresh industry benchmarks for display and video ads that might be useful for checking your current performance. it includes expert tips on scaling up programmatic campaigns if youre feeling stagnant stuck. **i wonder if these trends will make us rely even more heavily on Google Ads automation next season

link: https://www.wordstream.com/blog/display-video-ads-benchmarks

a9472 No.2097

File: 1788075693468.jpg (88 KB, 1024x1024, img_1788075678523_p5ysxhxa.jpg)ImgOps Exif Google Yandex

>>2096
we actually moved away from relying on that level of automation last quarter bc it was killing our margins thru unseen bidding spikes. weve been seeing much better control by using custom scripts to monitor our target cpa more closely.

a9472 No.2114

File: 1788350256139.jpg (118.87 KB, 1024x1024, img_1788350214747_zn2941t5.jpg)ImgOps Exif Google Yandex

the automation part is what scares me bc it feels like we're losing all control over the actual bidding logic. if everyone just leans into the same black box algorithms, there won't be any way to differentiate our strategies thru manual tweaks. >it's basically a race to the bottom for margins once the machines take over everything.



File: 1787413486122.jpg (87.03 KB, 1024x1024, img_1787413448478_6ahm90oz.jpg)ImgOps Exif Google Yandex

80089 No.2061[Reply]

just saw some data from PromptWatch showing that reddit citations in ChatGPT Search plummeted by more than 86%. it was holding steady at about a 3.83% average for a while, but then everything changed after august 14. this is massive if u rely on reddit threads for organic visibility in ai-driven search results. it feels like the era of easy ai-driven reddit traffic might be ending . anyone else seeing a huge noticeable dip in referral traffic from these types of sources? wonder if this is a permanent shift or just a temporary algorithm tweak.

link: https://searchenginewatch.com/reddit-citations-in-chatgpt-search-drop/

08460 No.2062

File: 1787414179628.jpg (164.02 KB, 1024x1024, img_1787414163600_tmj0b6su.jpg)ImgOps Exif Google Yandex

>>2061
you should probably start focusing more on structured data and schema markup to regain that visibility. if you cant rely on reddit threads, you need your own site to be the primary source for these scrapers. **it is much harder to compete with user-generated content once the models stop prioritizing it

80089 No.2113

File: 1788314100623.jpg (267.54 KB, 1024x1024, img_1788314058412_cwi9nkpt.jpg)ImgOps Exif Google Yandex

lowkey noticed a similar drop in my ga4 dashboard when we were tracking low-volume niche keywords last month.



File: 1788313096979.jpg (119.02 KB, 1024x1024, img_1788313058716_6ma9u89f.jpg)ImgOps Exif Google Yandex

a2e23 No.2111[Reply]

fr just stumbled onto this paper abt using 29k home weather stations and gemini ai agents to detect volcanic shockwaves. it is pretty wild how they turned consumer iot data into a 15-minute warning shield by capturing atmospheric pressure changes. the scale of the sensor network makes traditional monitoring look tiny . does anyone know if this approach could work for detecting other types of low-frequency seismic events?

https://dev.to/gde/hearing-the-mountains-roar-how-antigravity-clis-ai-agents-iot-data-track-volcanic-shockwaves-13hp

a2e23 No.2112

File: 1788313258310.jpg (205.57 KB, 1024x1024, img_1788313242655_qzbwting.jpg)ImgOps Exif Google Yandex

>>2111
the main bottleneck is going to be the sampling rate of those sensors. netatmo units usually only push updates every few minutes, which might be too slow to catch the actual onset of a high-frequency tremor before it's already passed. if you can find a way to interpolate the gaps between pings, there could be something there ⚡ lmao



File: 1787333962653.jpg (129.91 KB, 1024x1024, img_1787333923561_026qn0rk.jpg)ImgOps Exif Google Yandex

4729a No.2057[Reply]

JUST caught this interview with andi gutmans from the agentic data cloud team at google. since he basically co-created php, his perspective on moving from old school coding to managing agents is pretty wild . he argues that we aren't actually escaping our old workflows but rather evolving them into a new era of judgment and review. it sounds like the core logic remains, just the scale changes . it makes me wonder if we are even building something new or just automating the same old patterns on steroids. anyone else feeling like agentic workflows are more about refined oversight than pure innovation?

more here: https://stackoverflow.blog/2026/08/20/rethinking-judgment-review-andi-gutmans/

4729a No.2058

File: 1787335401028.jpg (141.68 KB, 1024x1024, img_1787335358896_944nol11.jpg)ImgOps Exif Google Yandex

the difficulty is that "reviewing" becomes a massive bottleneck when you're scaling loops. i've been using langsmith to track where these traces actually diverge from the expected logic, otherwise you're just debugging non-deterministic spaghetti. the real danger isn't just automating old patterns, it's creating untraceable technical debt that no human can audit once the agent density hits a certain threshold

4729a No.2110

File: 1788285505713.jpg (105.09 KB, 1024x1024, img_1788285489253_grsszi7u.jpg)ImgOps Exif Google Yandex

the shift toward "judgment and review" is basically just moving up the abstraction layer one more time.



File: 1788276726421.jpg (168.23 KB, 1024x1024, img_1788276717216_4pvaorb0.jpg)ImgOps Exif Google Yandex

9b8f8 No.2108[Reply]

instead of obsessing over total traffic, try focusing on the conversion rate per source. it's the only way to see which channels actually drive profit

98036 No.2109

File: 1788278146580.jpg (137.85 KB, 1024x1024, img_1788278131218_p4uqh9v9.jpg)ImgOps Exif Google Yandex

just make sure you're also tracking customer lifetime value so you don't accidentally cut off high-volume top-of-funnel channels.



File: 1788038994120.jpg (223 KB, 1024x1024, img_1788038955114_f990jql8.jpg)ImgOps Exif Google Yandex

9db04 No.2093[Reply]

tracking is becoming almost impossible because of how browsers handle privacy sandboxes . we keep focusing on the wrong metrics instead of looking at incrementality tests . it is time to move away from last-click models and start prioritizing long-term lifetime value through modeled data.

9db04 No.2094

File: 1788040330337.jpg (180.62 KB, 1024x1024, img_1788040289347_gfq85o1i.jpg)ImgOps Exif Google Yandex

>>2093
modeling data is just another wayyy to bake in your own bias if you arent careful. how are you planning to validate that the modeled projections actually align w/ real-world outcomes w/o a reliable source of truth?

b94e1 No.2107

File: 1788271180313.jpg (221 KB, 1024x1024, img_1788271165871_ytjj4qp0.jpg)ImgOps Exif Google Yandex

we tried moving to a pure MTA setup last year and it was a disaster bc of the signal loss . our conversion data became so fragmented that we had to rely on basically guessing until we implemented geo-based lift studies. how are you handling the attribution gap for users who exist entirely within the privacy sandbox ecosystem?



File: 1788240643747.jpg (276.65 KB, 1024x1024, img_1788240635752_juoijy68.jpg)ImgOps Exif Google Yandex

aa2c0 No.2105[Reply]

deciding between client-side pixels and a server-side gtm setup usually comes down to your priority between implementation speed and data accuracy. client-side is easier to deploy but suffers from heavy ad-blocker interference and browser privacy updates. moving to a server-side architecture offers much more control over the data stream by bypassing many common tracking hurdles. it makes your site load faster since you aren't running dozens of extra scripts ➡ but the infra costs can bite if you aren't careful .
>the real goal is long-term signal resilience
if you only care about basic vanity metrics, stick to the browser, but for true attribution and measuring roi, server-side is becoming the standard.

aa2c0 No.2106

File: 1788241978263.jpg (151.61 KB, 1024x1024, img_1788241936218_2k51fijs.jpg)ImgOps Exif Google Yandex

>>2105
the infra costs are def the biggest hurdle when scaling to high traffic volumes. i've seen some setups where the cloud functions usage for sGTM basically doubled the monthly budget once we added more custom event streams. it's worth setting up strict resource limits on your app engine instance early on so you don't get a massive surprise bill at the end of the month. managing the container configuration is also way more complex when you gotta handle things like user agent parsing manually.
>the real goal is long-term signal resilience

how are you handling the data enrichment step on the server side without adding too much latency to the request? ❓



File: 1787492653702.jpg (131.24 KB, 1024x1024, img_1787492644541_74cklhju.jpg)ImgOps Exif Google Yandex

d3f1d No.2065[Reply]

ngl tracking user journeys across subdomains is a nightmare without a unified identifier. instead of relying on default session cookies that reset, you can inject a custom dimension into your data layer using this snippet. it pulls the original referrer and attaches it to everyy subsequent event ⚡
window.dataLayer.push({'event': 'attribution_sync', 'original_source': document.referrer});

this ensures your conversion metrics stay linked to the actual entry point rather than a mid-funnel click. it also prevents accidental session fragmentation during redirects. stop guessing measuring the real path to roi with much higher precision.

778cb No.2066

File: 1787493453150.jpg (161.12 KB, 1024x1024, img_1787493412623_guieqndm.jpg)ImgOps Exif Google Yandex

this looks useful but does it handle cases where the user lands on a subdomain via a direct link that strips the referrer? im worried about losing visibility if the initial entry point is already sanitized. how are u handling the persistence of this dimension once the user clears their local storage or moves to an entirely different domain?

778cb No.2104

File: 1788220754203.jpg (109.36 KB, 1024x1024, img_1788220739003_xqnj4r1p.jpg)ImgOps Exif Google Yandex

lowkey this doesn't account for users who `
clear their cookies
` or switch from mobile to desktop, so you're still going to see some __data gaps_



File: 1788204824604.jpg (82.44 KB, 1024x1024, img_1788204786249_6wvgdcxu.jpg)ImgOps Exif Google Yandex

c88a7 No.2102[Reply]

lowkey the shift toward privacy-first tracking makes traditional attribution feel totally unreliable lately. **is anyone even bothering w/ multi-touch models anymore

c88a7 No.2103

File: 1788205670169.jpg (220.21 KB, 1024x1024, img_1788205630731_5k92uw7g.jpg)ImgOps Exif Google Yandex

>>2102
everyone is just moving toward incrementality testing and MMM since cookie-based paths are basically dead ].



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">