Counting does not seem to work with other URL shortening services



This used to work, I am sure (but could be wrong), but when requesting a count of a tweeted URL, which is URL shortened, it is no longer counting. (Possibly related to your ongoing count issues, if so, that’s fine, just like to know :slight_smile: )

For example:

The top 3 do not count, yet the bottom one does, but all 3 shortened URLs point to the same URL as the 4th (well, technically the 1st points to another URL, that then gets 302’d to the final URL). Something else I’ve noticed, is that on your response, you seem to strip out some utm_ parameters from the query string? I don’t think it’s having any effect, just curious why you do it. I.e, the end URL in full is:, yet the response from your counter is:



Are you using the Tweet Button for these counts or are you actually making API calls to these endpoints? The general counting issues are still a thing and likely at least partially to blame here. We strip out utm_* parameters as a common “meaningless” params for the purpose of counting (they’re used by analytics trackers). However, we do consider most other query parameters as significant in a URL. Are you declaring these tinyurls in your Tweet Button markup?


We’re directly calling the API, we’re not using the tweet buttons as such (we create our own, rather than use the “SDK” provided by you), and not using the url, but, both URL types provide the same behaviour though.


You are not permitted to request from – it’s not a public API.


I tried this and it works:

Tweets {amin}


It may work, but you’re not allowed to do it.

closed #7