ZipQuantum Documentation

Everything you need to use Smart Links, Deferred Deep Linking, and QR Smart Codes — safely.

No proprietary SDK · No fingerprinting · Privacy-first

Create your first Smart Link in minutes

API integration, parameters, and error handling

Endpoints, parameters, and platform behavior.

Docs

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.

Get Started

Create your first ZipQuantum Smart Link in minutes — no proprietary SDK, no fingerprinting, and no attribution stack.

ZipQuantum links are install-aware by design.
They work before install, during install, and after install — using standard platform mechanisms only.

What You’ll Do Here

In this section, you’ll learn how to:

  • Create a Smart Link from the dashboard

  • Configure install-safe routing

  • Verify correct behavior across install states

  • Deploy links to production safely

No SDK integration is required.
No runtime interception.
No background services.

Prerequisites

Before you begin, make sure you have:

  • A ZipQuantum account

  • Access to your app’s App Store / Play Store listing

  • A destination URL or in-app route you want users to reach

That’s it.

Next Step

Create Your First Smart Link

This guide walks you through:

  • Creating a link

  • Testing install vs non-install behavior

  • Sharing it safely across channels