Routing & Resolution
Follow the exact order ZipQuantum uses to select a destination.
Lifecycle first
A future, expired, or click-limited link is blocked before device routing. Its expiration redirect is preferred, followed by its fallback and then its primary destination.
Active-link routing
- Android with a package: a configured Android device target or generated intent, plus the explicit fallback or derived Google Play URL.
- iOS with a Store URL: a configured iOS device target or primary destination, plus the explicit fallback or Store URL.
- Other devices: a matching device target, otherwise the primary destination, otherwise the fallback.
Device keys
Supported keys include Android, iPhone, iPad, iOS, Windows, macOS, Linux, Ubuntu, and other. Matching is normalized to lowercase.