Supposed way to extract User Agent is through enrichment process. You can see ua in snowplow tracker protocol just because it is used by our server-side trackers - their correct UserAgent HTTP header would be something like snowplow-python-tracker 0.7.0 (obviously useless for analytics), therefore server-side tracker needs to first extract user’s UA and then send it using ua parameter, whereas in JavaScript tracker there’s no such need - tracker’s UA is always the same as user’s and sent using UserAgent HTTP header.
You can checkout our ua-parser and user agent utils enrichments to extract information about users’ browsers.
Almost same for connection type. JavaScript tracker simply cannot determine it and you can see it in tracker protocol just because it is reserved (I believe so) and therefore marked as not implemented. Supposed way to get it is through IP Lookup enrichment, which can determine user’s connection (DSL/Dialup/etc) based on his IP.
I know there is a UserAgent in HTTP header. I want to collect user interaction data in Amazon Kinesis, and then analysis. If JavaScript tracker don’t return ‘ua’ to me, can I have ways to get it through HTTP header in enrichment process?
About connection type , I have seen marked as not implemented. No other question about connection type.
Hey @YuxinChou! If understand your question correct - you need a Stream Enrich (instead of batch process which I linked above) it can enrich stream of events with either ua-parser or user agent utils enrichments same as in batch and write result to configured Kinesis Stream.
If for some reasons you need raw UserAgent header - you can use HTTP header extractor enrichment, but I highly recommend you to use specialized enrichments for this purpose.