Skip to Content
GuidesAPI Reference
Smart RoutingTarget by Device

Redirect Mobile and Desktop Visitors to Different Pages

Device targeting lets you send mobile, desktop, and tablet visitors to different destinations — all from a single Brevr link. Share one URL everywhere and let Brevr handle the routing automatically.

What You’ll Learn

  • How device targeting works in Brevr
  • How to set up device rules on any link
  • The most effective use cases for device targeting

How Device Targeting Works

Brevr reads the visitor’s user agent when they click your link and identifies their device type: Mobile, Desktop, or Tablet. Brevr then checks your device rules and sends the visitor to the first destination that matches their device.

If you have not set a rule for a particular device type, those visitors go to your default URL. The default URL is your safety net — it always fires if no rule matches.

📸 Screenshot: [Link editor with device targeting panel open, showing Mobile, Desktop, and Tablet options with destination URL fields]

How to Set Up Device Targeting

  1. Open your link in the Brevr link editor.
  2. Navigate to the Smart Routing section.
  3. Click “Add Rule” and select “Device” as the rule type.
  4. Choose the device type: Mobile, Desktop, or Tablet.
  5. Enter the destination URL for that device type.
  6. Repeat steps 3–5 for any additional device types you want to target.
  7. Set your default URL to catch any device type you have not explicitly targeted.
  8. Save the link.

📸 Screenshot: [Completed device targeting setup showing a Mobile rule pointing to an App Store URL and a Desktop rule pointing to a product page]

Common Device Targeting Scenarios

DeviceDestinationUse Case
MobileApp Store / Google PlayApp install campaign
DesktopProduct websiteFull-feature product page
Tablet(same as desktop)Optional: dedicated tablet experience

The most common setup is a two-rule link: mobile goes to the app store, desktop goes to the website. Tablet visitors typically behave more like desktop users, so defaulting them to the desktop URL works well for most campaigns.

Use Cases for Device Targeting

App install campaigns. Share one link across all your marketing channels. Mobile visitors land directly on your App Store or Google Play listing. Desktop visitors see your product page or a prompt to text themselves the app link.

Mobile-first content. You have a page that only works well on mobile — a mobile game, an AR experience, or a click-to-call landing page. Device targeting keeps desktop users away from a broken experience.

SMS marketing. SMS links are opened almost exclusively on mobile. Use device targeting to send the rare desktop opener to a different page without affecting your mobile audience.

Responsive vs. native app. Your website is responsive, but your native app offers a better experience. Send mobile users to a smart app banner or directly to the app store, while desktop users get the full web experience.

Frequently Asked Questions

Can I target iOS and Android separately?

No — device targeting identifies device type (Mobile, Desktop, Tablet), not the operating system. To send iOS users to the Apple App Store and Android users to Google Play, create two separate links: one with your iOS App Store URL and one with your Google Play URL. Share the iOS link with Apple-specific channels and the Android link with Android-specific channels.

What counts as “Mobile” in Brevr’s detection?

Mobile includes smartphones — any handheld device with a phone-sized screen. Tablets are detected separately. Brevr identifies device type from the visitor’s user agent string.

What happens if a visitor is on a device I haven’t targeted?

They go to your default URL. Always set a default URL that works for any device. This guarantees every visitor reaches a valid destination.

Yes. You can combine device and country targeting on a single link. Brevr evaluates all active rules. A visitor from Germany on a mobile device will match whichever rule fires first — so order your rules intentionally.

Can I send tablet visitors to a unique page?

Yes. Add a separate Tablet rule with its own destination URL. If you do not add a Tablet rule, tablet visitors fall through to your default URL.


Watch the Full Walkthrough

🎬 Video walkthrough: [Device Targeting — ~2 min]

Walk through every step below with the screenshots to follow along at your own pace.

Open your Brevr link and navigate to the Smart Routing section. You will see the rules list and the default URL field where all device rules are configured.

📸 Screenshot: [Brevr link editor open with the Smart Routing section in focus, showing an empty rules list and the default URL input field]

Step 2: Add a Device Rule

Click “Add Rule” and select “Device” as the rule type. A device type selector and a destination URL field will appear, ready to configure.

📸 Screenshot: [The “Add Rule” dropdown open with “Device” highlighted as the selected rule type]

Step 3: Configure the Mobile Rule

Choose “Mobile” from the device type selector and enter the destination URL for mobile visitors — typically your App Store or Google Play listing for app install campaigns.

📸 Screenshot: [A device rule with “Mobile” selected and an App Store URL entered in the destination field]

Step 4: Add a Desktop Rule

Click “Add Rule” again, select “Device,” choose “Desktop,” and enter the destination URL for desktop visitors — such as your product page or full website.

📸 Screenshot: [Two device rules visible in the list: one Mobile rule pointing to an App Store URL and one Desktop rule pointing to a product website URL]

Step 5: Set the Default URL

Enter a default URL to catch any device type you have not explicitly targeted — for example, tablet visitors if you only added Mobile and Desktop rules.

📸 Screenshot: [The default URL field filled in below the two device rules, with a fallback URL that works on any device]

Click Save. Brevr immediately begins routing visitors based on their detected device type. Mobile and desktop users now reach their respective destinations from a single shared link.

Next Steps

Last updated on