I have some pages on my web app which are public and therefore when I identify and track on the server there is rarely a cookie for me to use for anonymous id (it's the first time the user has reached the site). I can create an ID on the fly on the server but then I have to guess segments cookie config for dev and production otherwise the client side library sets a second anonymous cookie itself leading to tracking being lost between the server and client. It would be great if there was an exposed function that returned the cookie config segment uses for users of this package to use to set a cookie on the server for the client to use. This would prevent manual cookie setting from breaking whenever Segment changes their config.
I have some pages on my web app which are public and therefore when I identify and track on the server there is rarely a cookie for me to use for anonymous id (it's the first time the user has reached the site). I can create an ID on the fly on the server but then I have to guess segments cookie config for dev and production otherwise the client side library sets a second anonymous cookie itself leading to tracking being lost between the server and client. It would be great if there was an exposed function that returned the cookie config segment uses for users of this package to use to set a cookie on the server for the client to use. This would prevent manual cookie setting from breaking whenever Segment changes their config.