Segment properties

[aleczratiu]

Hi there, I've recently begun using @segment/analytics-node. It appears that the track method no longer includes segment properties such as userAgent, userAgentData, page details, and others.

When using this library on the client-side, these events are automatically populated by segment. However, I'm concerned that by switching to the node analytics SDK, we might lose access to these valuable pieces of information.

Any thoughts or ideas on how these properties can be sent further by using @segment/analytics-node?

[silesky]

@aleczratiu
You would need to send those properties explicitly; this is a server-side SDK, those are client side properties that can't be plucked out of the environment like they are in the browser.

[aleczratiu]

Thank you for your time and assistance @silesky ; it means a lot to me to have this confirmation. I'm sending now the IP and userAgent through Node.js and is working pretty well. Now, I'm contemplating moving the "identify" and "group" methods to the server-side, but I'm concerned about potentially losing the funnel. The script tag from Segment is placed on the "site page", "authentication page" and "application" where's the main app (game). If I move those methods to the server-side which were on the application page, are there any drawbacks like losing the funnel or causing Segment to merge identifiers? It's important to note that on the site page, the user is not logged in is just a simple presentation page where we have the segment script, and there are only limited details available. Only when the user logs in and reaches the app, some details about them are accessible; until then, they are merely marked as a unique visitor by Segment.