What the engine resolves

Each ZipQuantum link combines a hostname, a reference, a primary destination, optional device targets, mobile fallbacks, campaign parameters, lifecycle rules, and social-preview metadata.

Resolution order

1. Find the link by its normalized reference.
2. Confirm that the request host is the link’s managed ZipQuantum host, a verified custom domain, or a supported legacy host.
3. Apply activation date, expiration date, and click-limit rules.
4. Detect the device category from request headers.
5. Select an Android, iOS, device-specific, or default destination.
6. Insert configured parameters and record an aggregate session for non-automated visitors.

Privacy boundary

Normal redirects do not persist raw IP addresses or user-agent strings. Deferred recovery is deterministic: Android uses Play Install Referrer, while iOS uses a short-lived, signed, user-initiated handoff. Neither path uses fingerprinting or probabilistic device matching. Optional device context is stored only with consent.