centralized server for event tracking instead of using segment.io directly?

I'm facing a design problem:

We are trying to implement events so that users' behavior can be analyzed. Here are the two ways we might take, and I'd like to ask what problems each method might cause

1) we use segment.io on clients directly. thus when user clicks a button, the data sends to segment's server 2) we implement an endpoint for our clients to send data to our server first, then server sends the data to segment.io

for 2, I can see the advantages are

1. the clients doesnt need to worry about integrating any sdk
2. server can send data to segment.io too (i.e. how long each request takes etc. server side actions)
3. we can store the events data on our server as well without asking client to make two calls (when clients send data to our server, we store it in our db first, then send it to segment.io)

2 seems reasonable, but 1 seems to be what everyone else is doing

any suggestion?