FloatMessage

Device Targeting

Show your floating messages and chat widget only on the devices that matter - desktop, tablet, or mobile. Pair it with URL or geo targeting to build precise visitor segments without writing code.

Available Device Types

  • Desktop - laptops and desktop computers (no touch UA, large viewport)
  • Tablet - iPad, Android tablets, Kindle Fire, Surface, etc.
  • Mobile - phones (iOS, Android, Windows Phone)

How It Works

Device detection runs client-side in the embed script - there is nothing to install on your server. The script reads the visitor's user-agent first (which is the most reliable signal) and falls back to viewport size and touch capabilities for edge cases such as desktop-mode browsers on tablets.

Evaluation Flow

  1. Embed script loads on the visitor's page
  2. It reads the message or chat config including the targetDevices array
  3. It detects the visitor's device type from the user-agent and viewport
  4. If the detected device is not in the allowed list, the message or widget is silently skipped

Configuration

Open any message in Dashboard → Messages → Targeting, or open Dashboard → Live Chat → Settings → Visibility. Click the device buttons to toggle which devices see the message or chat.

  • No devices selected = show on every device (default)
  • One or more selected = show only on those devices
  • Selecting all three is equivalent to selecting none - both mean “show everywhere”

Common Use Cases

  • Run an “install our app” banner only on mobile
  • Show a desktop-only popup that links to a downloadable PDF
  • Hide chat on mobile while you build a phone-friendly support flow
  • Promote a tablet-optimised landing experience to iPad visitors

Notes

  • Detection is client-side; visitors that spoof their user-agent will be classified by the spoofed value
  • Device targeting stacks with URL, geo, and schedule rules - every rule must pass for the message or chat to appear
  • Tablet detection treats iPad with desktop-mode Safari as a tablet via touch + viewport heuristics
  • The setting takes effect on the next page view - no redeploy of your embed script is needed