Hi Aditya,
Matching is performed on the contents of the entities.urls array. When shortened URLs are posted as part of the tweet this metadata will only include the t.co shortened url, the display_url (as written in the Tweet body)… and in this case the expanded_url is essentially the same as the display_url. So in this case there would be no matching for terms in the non-shortened URL. (I included a JSON example below)
For what it is worth, Gnip (Twitter’s “enterprise data” provider) Activity Stream format includes a fully expanded URL. For more information, see http://support.gnip.com/enrichments/expanded_urls.html
"entities": {
"urls": [
{
"url": "http:\/\/t.co\/SoaTsqt47v",
"expanded_url": "http:\/\/goo.gl\/xYe5Qh",
"display_url": "goo.gl\/xYe5Qh",
"indices": [
36,
58
]
}
]
}