Parameter Forwarding for Deep Links, Universal Links, App Stores, and Web
Keep campaign attribution and in-app context intact as one smart link routes each visitor to a different destination.
One click, several destinations, the same context
A smart link may open an installed app, send a new user to an app store, use an HTTPS Universal Link or App Link, or fall back to the web. Without parameter forwarding, the route works but the campaign and content context attached to the original click disappears.
Parameter forwarding copies eligible query parameters from the incoming Appy URL to the destination selected for that device. It keeps one campaign link useful across every branch of the journey.
Where parameters are forwarded
Custom-scheme deep links
Values such as product_id, coupon, referrer, and UTM tags reach the installed app through a URL such as myapp://.
Universal Links and App Links
The same values are merged into an HTTPS app-opening URL while preserving its path, existing query, and fragment.
App Store and Google Play
Campaign context follows the platform-specific store URL. Existing store identifiers such as Google Play id remain protected.
Normal links and web fallbacks
Desktop and unsupported-device traffic keeps the same campaign values on the final landing page.
The merge rules that prevent broken links
- Destination-defined query keys win. An incoming value can never replace a fixed app ID, content ID, or signed token.
- New keys are appended and repeated incoming values are preserved.
- The destination path and URL fragment stay unchanged.
- Forwarding is opt-in per link and available on the Business plan. If the entitlement is removed, forwarding stops at click time.
A concrete example
https://appy.to/summer?utm_source=qr&campaign=launch&coupon=SUMMER → myapp://offer/42?utm_source=qr&campaign=launch&coupon=SUMMERHow to enable it in Appy
- 1Create or open a link in the dashboard.
- 2Configure the deeplink, Universal Link, store URLs, and web fallback you need.
- 3Enable “Forward incoming parameters,” save, and test each device branch with representative campaign values.
What not to put in a URL
- Do not forward passwords, access tokens, session IDs, or personal data.
- Use short opaque identifiers for sensitive business objects and resolve them securely inside your app.
- Keep allowlists in your app or landing page when only a known set of keys should affect behavior.
Frequently asked questions
Will incoming parameters overwrite a destination parameter?
No. Values configured on the destination URL take precedence; only missing keys are forwarded.
Does forwarding work when the redirect target is cached?
Yes. Appy caches the base destination and merges request-specific parameters after the cache lookup, so one visitor cannot leak parameters into another visitor’s redirect.
Continue exploring
Deferred Deep Linking: How It Works and When to Use It
Understand how deferred deep linking carries the original link intent across install so new users land on the right in-app screen, not a generic home tab.
Deep Linking vs Universal Links: Complete Comparison
Understand the key differences between deep links and universal links, when to use each, and how to implement them effectively.
Complete Guide to Universal Links for iOS and Android
Everything you need to know about universal links, deep links, and app links. Learn how to implement them and boost your mobile marketing.
Looking for something else? Browse all topics on the blog.
Keep campaign context through every redirect
Use one link for app, store, Universal Link, and web traffic without losing the values that explain where the click came from and what it should open.
Create a Business link