[ 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.)

File: 1792198819143.jpg (128.86 KB, 1024x1024, img_1792198810134_to1md6j5.jpg)ImgOps Exif Google Yandex

3e2b8 No.2336

been looking at our recent migration to bigquery for session stitching and it's driving me nuts. we set the default 30 minute window but that's clearly too short for anyone actually reading long-form content. i noticed a massive spike in fragmented sessions yesterday because people were just leaving tabs open overnight.
>it's basically double counting conversions
if you don't adjust the timeout for your high ltv segment, your attribution is going to look like a complete mess. every time someone comes back from a lunch break it registers as a new session with zero way to link it to the original landing page. i tried increasing it to 12 hours but now the session count is useless because it's just grouping unrelated clicks together. trying to find a middle ground in ga4 without breaking our dayparting reports is impossible. honestly might just move to server-side tracking for these specific events so we can control the lifecycle ourselves. messy as hell to set up though.


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]