Create Your First Smart Link
Create and activate a ZipQuantum Smart Link in three steps: paste a destination, configure routing, then preview and activate.
Purpose
This guide creates a shareable Smart Link from an existing web or in-app destination. The same link can include app-store fallbacks and a social preview.
Prerequisites
- A destination URL that begins with
https://. - Optional: the App Store and Google Play URLs for your app.
- Optional: a title, description, and image URL for the social share card.
Step 1 — Paste Link
- Open the ZipQuantum creation form.
- In Your link, paste the destination URL. The corresponding field is
original_url. - Choose the Smart Subdomain that will appear before
.zq.tn. The corresponding field issubdomain. - Select Continue.
Step 2 — Link Settings
Configure only the options required by your use case:
- iOS App Store URL (
ios_app_store_url): used as the iOS fallback when the app is not installed. - Android Play Store URL (
android_play_store_url): used as the Android fallback when the app is not installed. - Meta Title (
meta_title): headline displayed when the link is shared. - Meta Description (
meta_description): short supporting text for the share card. - Image URL (
meta_image): optional preview image.
The store and social-preview fields are optional and can be updated later from the dashboard.
Step 3 — Preview & Activate
- Review the generated Smart Link and its preview.
- Confirm the destination, subdomain, store fallbacks, and social metadata.
- Select Activate My Smart Link.
- When Setup complete appears, copy the live link or select Go to Dashboard.
Expected Result
The Smart Link is live and ready to share. Activating it does not install code in your application.
Verification
- Open the link in a private browser window and confirm the web destination.
- Test on iOS and Android if store fallbacks were configured.
- Paste the link into a private message or preview tool and confirm the social title, description, and image.
Troubleshooting
- Continue is unavailable: verify that the destination is a complete HTTPS URL.
- The subdomain is rejected: choose another available value using letters, numbers, or hyphens.
- The wrong store opens: verify the two store URLs and test again on the corresponding platform.
- The share preview is outdated: update the metadata, then allow the destination platform to refresh its cached preview.