Timeline for Earliest / easiest to implement way to detect browser, version, and screen size?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 8, 2022 at 14:07 | answer | added | Mike Ciffone | timeline score: 1 | |
| Jun 7, 2022 at 18:36 | comment | added | Stephen Ostermiller♦ | It could be faster, but you should probably start with the user agent data that probably already exists in your access logs. | |
| Jun 7, 2022 at 18:28 | comment | added | philolegein | Hmm. So maybe do both? Even JS wouldn't be the same as GA4, which takes 100s of milliseconds to load. If I can write something tiny and load it in the header from the CDN, should be much faster than GA, no? | |
| Jun 7, 2022 at 18:23 | comment | added | Stephen Ostermiller♦ | Browser user agent is available on your server because it is sent as a HTTP header. Screen size is only available to JavaScript, so whatever you do may have the same limitations as GA4. | |
| Jun 7, 2022 at 18:22 | comment | added | philolegein | Yes, as measured by the "ad network", but the "network" in this case is direct PPC on Twitter. | |
| Jun 7, 2022 at 18:21 | comment | added | Stephen Ostermiller♦ | PPC clicks as measured by the ad network? Some of those drop off before hitting your site at all. I.e. they hit the ad networks tracker but then not your server. | |
| Jun 7, 2022 at 18:09 | history | asked | philolegein | CC BY-SA 4.0 |