Link rules

A link's routes are rules. Each sends the visits that match its conditions to its own url; they are tried in order, the first that matches wins, and every other visit goes to the link's own url. Rules are free on every plan with an account, up to 20 a link. Send them when creating a link or in an update; null or [] removes them.

{
  "routes": [
    { "conditions": [{ "kind": "os", "values": ["ios"] }], "url": "https://apps.apple.com/app/id1234567890" },
    { "conditions": [{ "kind": "os", "values": ["android"] }], "url": "https://play.google.com/store/apps/details?id=com.example" },
    {
      "name": "Lunch menu",
      "when": "all",
      "conditions": [
        { "kind": "time", "from": "11:00", "to": "15:00", "tz": "America/New_York" },
        { "kind": "weekday", "values": [1, 2, 3, 4, 5], "tz": "America/New_York" }
      ],
      "url": "https://example.com/menus/lunch"
    }
  ]
}

• when is all (the default: every condition must hold) or any (one is enough). A rule holds 1 to 10 conditions, and any condition but split takes "negate": true to turn it around.
• Who: device (mobile, tablet, desktop), os (ios, android, windows, macos, linux, chromeos), browser (chrome, safari, firefox, edge, samsung, opera, and the in-app browsers instagram, facebook and tiktok) and language (the browser's first language, such as es), each with values.
• Where: country (ISO codes such as US, from the visitor's network), region (US-CA) and referrer (sites such as instagram.com; subdomains match), each with values.
• When: time (from and to as HH:MM; an end before the start runs past midnight), weekday (values 0 for Sunday to 6) and dates (from and/or to, such as 2026-11-01 or 2026-11-01T09:00, both inclusive). Each takes tz: visitor (the visit's own time zone, the default) or an IANA zone such as Europe/London.
• How: via (value qr for a scan of the link's QR code, link for a click), query (param and an optional value, read from the short link's own query string) and split (percent, 1 to 99).
• Shares of visitors come from one draw per visitor, per link, per day, with no cookie: the same person lands in the same place all day. Rules with a share next to each other split one draw, so 50 then 50 is an even A/B test; together they add up to at most 100.
• Fast. Rules read only what the visit already carries (headers, the network's country, region and time zone, the query string), so a link with rules redirects as fast as one without.
• Refusals are 400 validation_failed with the field in details, such as routes.2.conditions.0.values, and the rule's number in the message. The older shape, { match, countries, url }, is still accepted, and answers mirror it on rules that fit it.

The dashboard lists a link's rules in plain words and has a Test a visit tool: pick a device, place, language, time and how the visitor arrived, and see which rule fires and why. Assistants can set rules through the MCP tools shorten_link and update_link.