{"id":633,"date":"2026-03-30T13:00:00","date_gmt":"2026-03-30T18:00:00","guid":{"rendered":"https:\/\/tolinku.com\/blog\/?p=633"},"modified":"2026-03-07T03:33:09","modified_gmt":"2026-03-07T08:33:09","slug":"custom-smart-banners","status":"publish","type":"post","link":"https:\/\/tolinku.com\/blog\/custom-smart-banners\/","title":{"rendered":"Custom Smart Banners: Design and Implementation Guide"},"content":{"rendered":"\n

Smart banners are small, dismissible strips at the top or bottom of a web page that invite mobile visitors to open or install your app. The Apple meta tag approach<\/a> has been around since iOS 6, but it gives you almost no control. You get a fixed design, no analytics, and no ability to target specific user segments.<\/p>\n\n\n\n

Custom smart banners fix all of that. By building your own, you control exactly how the banner looks, when it appears, how long it waits, and where it sends users. This guide covers the full implementation: HTML structure, CSS styling, JavaScript behavior, responsive layout, animation, and integration with Tolinku's smart banner platform<\/a>.<\/p>\n\n\n\n

\"a
Photo by Nangialai Stoman<\/a> on Unsplash<\/a><\/figcaption><\/figure>\n\n\n\n

The Core HTML Structure<\/h2>\n\n\n\n

A smart banner needs to be lightweight. It should load fast, sit above your page content, and not cause layout shifts that hurt your Core Web Vitals<\/a> scores. Here is a solid starting structure:<\/p>\n\n\n\n

<div id="tolk-banner" class="tolk-banner tolk-banner--top" role="banner" aria-label="Download our app">\n  <div class="tolk-banner__inner">\n    <button class="tolk-banner__close" aria-label="Dismiss banner" type="button">\n      <svg width="16" height="16" viewBox="0 0 16 16" fill="none" aria-hidden="true">\n        <path d="M12 4L4 12M4 4l8 8" stroke="currentColor" stroke-width="2" stroke-linecap="round"\/>\n      <\/svg>\n    <\/button>\n    <img class="tolk-banner__icon" src="\/images\/app-icon.png" alt="" width="40" height="40" loading="lazy">\n    <div class="tolk-banner__text">\n      <span class="tolk-banner__title">MyApp<\/span>\n      <span class="tolk-banner__subtitle">Open in the app for a better experience<\/span>\n    <\/div>\n    <a class="tolk-banner__cta" href="#" id="tolk-banner-link">Open App<\/a>\n  <\/div>\n<\/div>\n<\/code><\/pre>\n\n\n\n
A few things matter here. The role="banner"<\/code> attribute helps screen readers understand the element's purpose. The close button has an aria-label<\/code> so keyboard users know what it does. The app icon uses loading="lazy"<\/code> because it is not critical for the initial render.<\/p>\n\n\n\n
CSS: Mobile-First Layout<\/h2>\n\n\n\n
The banner should render cleanly on a 320px screen first, then adapt upward. Avoid fixed widths. Use safe-area-inset-*<\/code> CSS environment variables for devices with notches or home indicators:<\/p>\n\n\n\n
.tolk-banner {\n  position: fixed;\n  left: 0;\n  right: 0;\n  z-index: 9999;\n  background: #ffffff;\n  box-shadow: 0 2px 8px rgba(0, 0, 0, 0.12);\n  padding: env(safe-area-inset-top, 0) env(safe-area-inset-right, 0) 0 env(safe-area-inset-left, 0);\n  transform: translateY(-100%);\n  transition: transform 0.3s ease;\n}\n\n.tolk-banner--top {\n  top: 0;\n}\n\n.tolk-banner--bottom {\n  bottom: 0;\n  top: auto;\n  transform: translateY(100%);\n  padding: 0 env(safe-area-inset-right, 0) env(safe-area-inset-bottom, 0) env(safe-area-inset-left, 0);\n  box-shadow: 0 -2px 8px rgba(0, 0, 0, 0.12);\n}\n\n.tolk-banner--visible {\n  transform: translateY(0);\n}\n\n.tolk-banner__inner {\n  display: flex;\n  align-items: center;\n  gap: 10px;\n  padding: 10px 14px;\n  max-width: 680px;\n  margin: 0 auto;\n}\n\n.tolk-banner__icon {\n  width: 40px;\n  height: 40px;\n  border-radius: 9px;\n  flex-shrink: 0;\n}\n\n.tolk-banner__text {\n  flex: 1;\n  min-width: 0;\n  display: flex;\n  flex-direction: column;\n}\n\n.tolk-banner__title {\n  font-weight: 600;\n  font-size: 14px;\n  white-space: nowrap;\n  overflow: hidden;\n  text-overflow: ellipsis;\n}\n\n.tolk-banner__subtitle {\n  font-size: 12px;\n  color: #666;\n  white-space: nowrap;\n  overflow: hidden;\n  text-overflow: ellipsis;\n}\n\n.tolk-banner__cta {\n  background: #007aff;\n  color: #fff;\n  border-radius: 20px;\n  padding: 7px 16px;\n  font-size: 13px;\n  font-weight: 600;\n  text-decoration: none;\n  white-space: nowrap;\n  flex-shrink: 0;\n}\n\n.tolk-banner__close {\n  background: none;\n  border: none;\n  cursor: pointer;\n  color: #999;\n  padding: 4px;\n  flex-shrink: 0;\n  line-height: 0;\n}\n<\/code><\/pre>\n\n\n\n
The transform: translateY(-100%)<\/code> default state keeps the banner off screen until you add the tolk-banner--visible<\/code> class. This approach avoids layout shifts because the banner starts outside the viewport rather than collapsing in the document flow.<\/p>\n\n\n\n
Using env(safe-area-inset-*)<\/code> is important for iPhones with a notch or Dynamic Island. Without it, the banner content can sit under the status bar. The CSS environment variables spec<\/a> is well-supported across all modern mobile browsers.<\/p>\n\n\n\n
JavaScript: Show, Dismiss, and Persist Decisions<\/h2>\n\n\n\n
The JavaScript layer handles three things: deciding whether to show the banner, building the correct deep link URL, and persisting the dismiss state so the banner does not reappear immediately.<\/p>\n\n\n\n
(function () {\n  const STORAGE_KEY = 'tolk_banner_dismissed';\n  const DISMISS_DURATION_DAYS = 7;\n\n  function isDismissed() {\n    try {\n      const raw = localStorage.getItem(STORAGE_KEY);\n      if (!raw) return false;\n      const { timestamp } = JSON.parse(raw);\n      const age = Date.now() - timestamp;\n      return age < DISMISS_DURATION_DAYS * 24 * 60 * 60 * 1000;\n    } catch {\n      return false;\n    }\n  }\n\n  function dismiss() {\n    try {\n      localStorage.setItem(STORAGE_KEY, JSON.stringify({ timestamp: Date.now() }));\n    } catch {}\n    const banner = document.getElementById('tolk-banner');\n    if (banner) {\n      banner.classList.remove('tolk-banner--visible');\n      setTimeout(() => banner.remove(), 300);\n    }\n  }\n\n  function isMobile() {\n    return \/Android|iPhone|iPad|iPod\/i.test(navigator.userAgent);\n  }\n\n  function init() {\n    if (!isMobile()) return;\n    if (isDismissed()) return;\n\n    const banner = document.getElementById('tolk-banner');\n    if (!banner) return;\n\n    \/\/ Wire up close button\n    const closeBtn = banner.querySelector('.tolk-banner__close');\n    if (closeBtn) closeBtn.addEventListener('click', dismiss);\n\n    \/\/ Show the banner after a short delay\n    setTimeout(() => {\n      banner.classList.add('tolk-banner--visible');\n    }, 1500);\n  }\n\n  if (document.readyState === 'loading') {\n    document.addEventListener('DOMContentLoaded', init);\n  } else {\n    init();\n  }\n})();\n<\/code><\/pre>\n\n\n\n
The isMobile()<\/code> check prevents the banner from appearing on desktop browsers where it would not be useful. The dismiss state is stored in localStorage<\/code> with a timestamp so users who dismissed the banner seven days ago see it again. You can tune that duration based on your audience.<\/p>\n\n\n\n
Integrating the Tolinku SDK<\/h2>\n\n\n\n
The Tolinku SDK handles the most important part: generating the correct deep link for each platform and tracking the click. Without attribution, you cannot tell whether the banner is actually driving installs.<\/p>\n\n\n\n
\"Tolinku<\/p>\n\n\n\n
<script src="https:\/\/cdn.tolinku.com\/sdk\/v1\/banner.js" async><\/script>\n<\/code><\/pre>\n\n\n\n
Once the SDK loads, update the CTA link dynamically:<\/p>\n\n\n\n
window.tolinkuReady = function (tolinku) {\n  const link = tolinku.createLink({\n    campaign: 'smart-banner',\n    channel: 'web',\n    feature: 'banner',\n    data: {\n      \/\/ Pass the current page path so the app can open the right screen\n      $deeplink_path: window.location.pathname,\n    },\n  });\n\n  const cta = document.getElementById('tolk-banner-link');\n  if (cta) cta.href = link;\n};\n<\/code><\/pre>\n\n\n\n
The SDK detects whether the user is on iOS or Android and routes them to the correct store if the app is not installed, or opens the app directly if it is. The $deeplink_path<\/code> parameter carries the current page context into the app so users land in the right place rather than the app's home screen. Read more in the Tolinku smart banners documentation<\/a>.<\/p>\n\n\n\n
Responsive Design Considerations<\/h2>\n\n\n\n
On very small screens (under 360px), the subtitle and app name can overlap the CTA button. Add a media query to hide the subtitle in that case:<\/p>\n\n\n\n
@media (max-width: 359px) {\n  .tolk-banner__subtitle {\n    display: none;\n  }\n}\n<\/code><\/pre>\n\n\n\n
For tablets, you might not want the banner at all. Tablets often have better screen real estate for web content, and users are less likely to prefer an app experience on a 10-inch screen. Add a tablet exclusion to your isMobile()<\/code> check:<\/p>\n\n\n\n
function isMobile() {\n  const ua = navigator.userAgent;\n  if (\/iPad\/i.test(ua)) return false; \/\/ exclude iPads\n  return \/Android|iPhone|iPod\/i.test(ua);\n}\n<\/code><\/pre>\n\n\n\n
This respects the Apple Human Interface Guidelines<\/a> principle of not interrupting tablet users with mobile-oriented prompts.<\/p>\n\n\n\n
Animation and Performance<\/h2>\n\n\n\n
The slide-in animation uses CSS transforms, which run on the compositor thread and avoid triggering layout or paint. Never animate top<\/code>, height<\/code>, or margin<\/code> for a banner. Those properties force the browser to recalculate layout on every frame, which tanks performance on mid-range Android devices.<\/p>\n\n\n\n
If you want a fade combined with the slide:<\/p>\n\n\n\n
.tolk-banner {\n  opacity: 0;\n  transform: translateY(-100%);\n  transition: transform 0.3s ease, opacity 0.3s ease;\n}\n\n.tolk-banner--visible {\n  opacity: 1;\n  transform: translateY(0);\n}\n<\/code><\/pre>\n\n\n\n
Avoid will-change: transform<\/code> unless you have confirmed a performance issue. Overusing will-change<\/code> promotes every element to its own compositor layer, which increases memory usage on mobile.<\/p>\n\n\n\n
Positioning: Top vs. Bottom<\/h2>\n\n\n\n
Top banners are the convention on iOS, matching where Safari's address bar used to live. Bottom banners are more thumb-friendly on tall phones, and they do not collide with the iOS Dynamic Island or Android status bar notifications.<\/p>\n\n\n\n
If you go with a bottom banner, invert the transform:<\/p>\n\n\n\n
.tolk-banner--bottom {\n  bottom: 0;\n  top: auto;\n  transform: translateY(100%);\n}\n<\/code><\/pre>\n\n\n\n
The Tolinku display behavior documentation<\/a> covers how to configure position and timing without writing custom code.<\/p>\n\n\n\n
Connecting Design to Targeting<\/h2>\n\n\n\n
A custom banner is more useful when it knows who it is talking to. Tolinku's audience targeting<\/a> lets you show different banners to different users based on OS version, browser, geography, or custom attributes. You can build the banner in HTML\/CSS as described here and then use Tolinku's configuration layer to control which users see it and when.<\/p>\n\n\n\n
For example, you might show a banner with "Update your app" copy to existing users who have an older app version, and "Get the app" copy to first-time visitors. Both banners share the same HTML\/CSS structure but pull different copy from the Tolinku dashboard.<\/p>\n\n\n\n
See the targeting and scheduling documentation<\/a> for the full rule syntax.<\/p>\n\n\n\n
Testing Your Banner<\/h2>\n\n\n\n
Before deploying, test on real devices. Chrome DevTools device emulation is useful for layout but does not accurately simulate mobile browser chrome or safe area insets.<\/p>\n\n\n\n
Checklist:<\/p>\n\n\n\n