#How Pinterest opens a link
Tap the link behind a Pin and Pinterest opens the page in its own browser, inside the Pinterest app. On Android this is a system WebView, and developers have reported its user agent ending with a [Pinterest/Android] token; on iPhone it is an embedded web view rather than Safari. The link server reads that Android token and names Pinterest's browser. On iPhone it doesn't name Pinterest: it sees what the second card shows, a web view with no Safari in it.
Web views are where deep links most often stall. A Chrome tab knows how to pass an intent:// hand-off to Android; a web view only does it if the host app wrote code to allow it, and many show an error page instead. Developers have reported Pinterest-specific trouble for years: one public report on the Branch Android SDK describes links shared on Pinterest opening Google Play instead of the expected app, while the same links worked from WhatsApp, Facebook and Gmail.
#What a tap gets
On Android, the link server answers with the same page it gives Instagram or Facebook's browser instead of a redirect. Its Open in app button carries the same hand-off Chrome would get: your app opens at the deep link, or Google Play opens with the link attached so the first open after install lands on the product. The page also shows how to open the link in the phone's real browser, for the case where Pinterest's web view won't pass the button on. The card shows what the server sends; whether Pinterest lets the button through is up to Pinterest's app version, and we haven't recorded a Pinterest test on a real phone.
On iPhone, an embedded web view can't run our Get the app page, so the link server sends the tap directly to the App Store, which shows Open when the app is installed. Strait's Universal Links were tested on a real iPhone in October 2026, though not yet from inside Pinterest; install matching after an App Store install is opt-in.
The third card is Pinterest's crawler fetching your page to build the Pin's preview. It gets your title, description and image, never a redirect, and is never billed.
#Making Pinterest links work for you
- Point Pins at a page that is useful on its own. Some taps will stay in the web view, so the product page should still let people buy or save.
- Put
utm_source=pinterest and a utm_campaign on links you add to Pins. Android taps inside Pinterest are filed under Pinterest without tags, but iPhone taps aren't, and a campaign tag gives each campaign its own row.
- Pinterest is a planning and shopping channel, especially for home, fashion, food and beauty apps. Deep link to the exact product or collection, not the home screen.
- Test on the phones your shoppers use. Simulate the tap first, then try a real Pin on an Android phone and an iPhone before a campaign.
#Sources and how we checked
The cards are the link server's real decisions for each user agent. The [Pinterest/Android] token comes from user agents developers have published for Pinterest's Android browser, such as those in the whatismybrowser.com user agent database; it is the token the link server looks for. Without it the tap is a generic Android web view and gets the plain hand-off. The developer report is Branch Android SDK issue #599 (opened August 2018). Pinterest changes its app often, so treat the web view behaviour as something to test, not a promise.