You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is the right forum for this but when we track events on the server side and forward the data to segment, along with common fields and defined metadata even the writekey is being forwarded.
Eg:
@nitinprakash96 I think this is expected behavior for a couple of reasons.
This library is a simple wrapper around analytics-java. There is nothing this library is doing with the writeKey other than passing it directly to the underlying Java implementation.
I would suspect that this "secret" key is required to send to Segment so they know from where the data is coming from.
Is there a reason you think this library shouldn't be behaving in this way?
I'm not sure if this is the right forum for this but when we track events on the server side and forward the data to segment, along with common fields and defined metadata even the writekey is being forwarded.
Eg:
I don't think this is the right behaviour. Or is there something that I'm supposed to do in order to handle write key explicitly?
The text was updated successfully, but these errors were encountered: