Thinglink automatically detects many types of links and presents them as link tags. This includes both media content, such as videos and images, and pages with "open graph" data, such as most news site articles.
Thinglink can handle redirect services that point to the final content. However, due to technical reasons, there are some limitations to detecting where links that contain redirects point at. These issues occur if there are multiple redirect links "chained together".
Imagine a case where application X uses a redirector service for their URLs. For example, a.b.com/123 is actually a redirect to prod.b.com/products.php?id=123. They submit the redirect URL as their application URL.
In such a case, if someone links to this URL using bit.ly, the URL redir goes like this:
bit.ly -> a.b.com -> prod.b.com.
Unfortunately, we match against either the start of the chain (bit.ly) or the end of the chain (prod.b.com).