THIS WEEK GoTo.now vs. TinyURL: An In-Depth URL Shortener Showdown Read this week's article →

Make one link respond to visitor context and campaign timing

Route by location, device, referrer, schedule, or experiment, then stop automatically by date or measured click volume.

Configure smart routing All features
Illustration of one incoming short link being routed by location, device, schedule, experiment, and fallback rules

What you can do

Each capability below is available in the current GoTo.now application.

Country and region routing

Send visitors to localized storefronts, languages, offers, or compliance pages using edge-provided country and region codes.

Device and app routing

Choose browser fallbacks for iOS, Android, mobile, and desktop, plus app URI schemes that open an installed mobile app directly.

Recurring active hours

Publish weekly windows in an IANA timezone. Outside those windows, visitors receive the fallback destination.

Click-count expiration

Stop after a maximum total count, a maximum human count, or the first human visit for a one-time link.

Weighted experiments

Split traffic across two to five destinations with explicit weights and deterministic repeat-visitor assignment.

Date expiration and fallback

Set a launch time, an expiration time, and a useful fallback so an ended campaign never becomes a dead end.

One event link before, during, and after a launch

An event organizer keeps registration as the default, opens a check-in destination only during venue hours in Asia/Singapore, routes iPhone and Android visitors to their respective app experiences, and sets the post-event recording as the expiration fallback.

What this changes: The printed URL never changes, yet visitors receive a destination appropriate to their device and the event's current phase.

Is this the right tool?

Use it when

  • A campaign needs localized or device-specific destinations
  • A link should stop after a date or measured audience size
  • Two or more destinations need a controlled traffic split

Choose another approach when

  • Every visitor should always receive the same destination
  • You cannot provide a safe fallback for limits or expiration

How it works

1

Keep a safe default

Every smart link begins with a normal public HTTP or HTTPS destination.

2

Add higher-priority rules

Configure only the context, schedule, limits, password, or experiment rules the campaign needs.

3

Measure matched rules

The dashboard records privacy-safe human routing totals and the rule selected for each smart-link visit.

Configure smart routing

Behavior worth knowing

  • Click limits and one-time links require a fallback destination.
  • App deep links accept registered schemes such as myapp:// and intent://; web fallbacks remain separately configurable.
  • Automated crawlers do not consume a one-time human visit.

Routing & Expiration FAQs

What happens when a click limit is reached?
The smart link uses its configured fallback. Without a valid fallback, an unavailable page is returned rather than guessing a destination.
Which timezone controls recurring hours?
You choose an IANA timezone such as Asia/Singapore or America/New_York, so daylight-saving changes are handled by the timezone database.
Can a deep link fall back to an app store?
Yes. Use the app URI for installed-app opening and the iOS or Android web destination for the store or mobile landing page.

Explore the complete platform

See how link management, routing, analytics, QR, branded domains, automation, and workspace controls fit together.

View all features