WriteKey being tracked in segment data

[nitinprakash96]

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:

{
  "context": {
    "library": {
      "name": "analytics-clj",
      "version": "0.8.0"
    }
  },
  "event": "EventType",
  "integrations": {},
  "messageId": "xxxxxxxxx",
  "originalTimestamp": "2019-10-01T06:33:31.593Z",
  "properties": {
       "key1": "value1"
  },
  "receivedAt": "2019-10-01T06:33:36.745Z",
  "sentAt": "2019-10-01T06:33:32.900Z",
  "timestamp": "2019-10-01T06:33:35.438Z",
  "type": "track",
  "userId": "abcdef",
  "writeKey": "123456789"
}

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?

[bostonaholic]

Thanks for asking about this. I'll take a look at this issue soon and get back to you.

[bostonaholic]

@nitinprakash96 I think this is expected behavior for a couple of reasons.

1. 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.
2. 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?