Twitter and downstream services at times both add and strip URL redirects. (That's probably what the 'unwind' gnip process is doing: following redirects to find the real destination.)
Are you sure all clicks from all clients would have visited your shortener, as opposed to skipping it using metadata about its final destination?
(It might be worth testing with a unique, 200-returning terminal URL.)