Smart App Banners: Sending Website Visitors to Your App
Short answer: On iPhone, Safari can display a banner for your app once you add one line to your website's markup. The banner appears for visitors who lack the app, and for those who have it, the banner can open the app at the matching page through a deep link. On Android, Chrome can show an install prompt for a progressive web app, and an app-install banner can also link to the store listing. Keep the prompt small, let visitors dismiss it for a set period, and track each click with a campaign link so you know whether the banner earns installs.
What the banner does
A visitor on a phone is already in a browsing mindset. A banner that says "Get the app" at the top of the page works when it makes the app's benefit clear, such as "Book faster in the app" or "Your loyalty card is in the app". It fails when it covers the menu or appears before the visitor has read anything.
The purpose is to offer an easy route to the app, not to replace the website. Keep the site fully usable without the app, because some visitors will never install anything, and a broken page is a far bigger problem than a missed download.
Setting up the iPhone banner
The iPhone banner is driven by a meta tag placed inside the head section of the page. It needs your app's numeric identifier, which the developer portal lists for each app. A basic version looks like this:
<meta name="apple-itunes-app" content="app-id=1234567890">
The number shown is an example. Replace it with your app's ID. You can add an argument that passes the current page to the app:
<meta name="apple-itunes-app" content="app-id=1234567890, app-argument=https://example.com/menu/lunch">
When a visitor who has the app opens the page in Safari, the banner offers to open the app at that location, provided your app handles the link. The app must be set up to read the argument and show the matching screen. If it does not, the visitor lands on the app's home screen, which is less helpful.
Check the Apple developer documentation for the current behaviour and the supported options, since banner details can change between iOS versions.
Setting up the Android prompt
On Android, the install prompt usually comes from the progressive web app mechanism. If your site has a valid web app manifest and meets the browser's install criteria, Chrome can offer to add the site to the home screen. Some sites capture the browser's install event and show their own button at a moment they choose, such as after a visitor has viewed two product pages.
For a native Android app, a simple approach is a banner that links to the store listing, plus a deep link to the page the visitor was reading if your app supports it. Keep the wording clear and the placement consistent with your iPhone banner, so the experience feels the same.
Placement that works
Place the banner where it does not block the content or the navigation:
- Along the upper edge, above the header, on the first visit only.
- Or as a slim bar at the bottom, above any cookie or chat widget.
- Never over the checkout button, the menu toggle or a form field.
A worked example: an online bakery sees that most of its mobile visitors come from search results for cake ordering. It adds a Smart App Banner that says "Order your cake in the app" and links to the cake order screen. A visitor who already has the app goes straight to the order screen. A visitor without it sees the banner, can dismiss it and still order through the website.
The dismiss rule
Visitors who close the banner should not see it again for a set period. A seven-day gap is a common starting point, though the right number depends on how often people visit. Store the dismissal in a small cookie or local storage value on the visitor's device. The Apple banner handles its own dismissal, but a custom prompt must respect the choice you record.
Also cap how often the prompt appears. Showing a prompt on every page view annoys people and drives them away from the site.
Measuring the results
Use campaign links on the banner's destination so the app store or analytics tool can tell you where installs came from. For example, a store link with campaign parameters for "site-banner" lets you compare installs from the banner with installs from other sources. Track banner views, clicks and dismissals separately, so you know whether the banner is seen and whether it is ignored.
Give the banner two weeks before you judge it. Early numbers often reflect people who were already interested in the app.
Checklist before you launch
- Confirm the app ID and test the iPhone banner on a real phone with and without the app.
- Check that the deep link opens the right screen, or that the app falls back gracefully.
- Set the dismissal period and confirm it works after a page refresh.
- Make sure the banner does not cover key controls on small screens.
- Add campaign tracking to the store link.
- Check the page's accessibility, including the size and contrast of the banner text.
FAQ
Will the banner show to people who already have the app?
On iPhone, the visitor sees an open button instead of the install option when the app is installed. Test this on a device that has the app and one that does not.
Does a banner hurt search rankings?
A small, dismissible banner is generally fine. Problems arise with intrusive interstitials that cover the content, so keep the banner small and the content visible.
Can I show the same banner on desktop?
Desktop browsers do not show the iPhone banner, so use a separate call to action for desktop visitors, such as a QR code pointing to the app listing on a phone.
What if the banner does not appear?
Check the meta tag syntax, the App Store ID and that the page is served over HTTPS. Clear your test browser's data between attempts, because a dismissed banner may stay hidden.
If you would like help adding an app banner and tracking it properly, tell us which platforms your app is on and we will set it up with you: send us a message.