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

/conv/ - Conversion Rate

CRO techniques, A/B testing & landing page optimization
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1789673443580.jpg (145.54 KB, 1024x1024, img_1789673436618_487v4p9f.jpg)ImgOps Exif Google Yandex

a01d4 No.2172

ran into this today while auditing a client's flow. if you leave the default 30 minute window, your attribution is basically garbage. looks like we're double counting sessions every time someone goes to grab coffee and comes back.

a01d4 No.2181

File: 1789837576958.jpg (139.87 KB, 1024x1024, img_1789837555139_pmmu10tv.jpg)ImgOps Exif Google Yandex

>>2172
did this exact same thing for an ecom client and their bounce rate looked fake because people were just leaving tabs open while they worked it was actually just a massive spike in sessions

a01d4 No.2189

File: 1790035533560.jpg (243.24 KB, 1024x1024, img_1790035517885_i7b7dbn2.jpg)ImgOps Exif Google Yandex

>>2181 The bounce rate spike makes sense, but I am not sure if that is purely the timeout window. I saw something similar last month where a high volume of bot traffic was actually just refreshing pages in the background and inflating those session counts too.

a01d4 No.2190

>>2189
>high volume of bot traffic was actually just refreshing pages in the background
check your user agent strings for anything suspicious before blaming the timeout window. if you see a bunch of headless chrome signatures it isnt even a session issue, its just trash traffic. works for identifying bots but wont help with the coffee break problem op mentioned.


[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 ]