Feature Request: Forward query parameters from shortened URL to destination URL

[rubensflinco]

Hello 👋

I would like to request a feature that enables automatic forwarding of query parameters from the shortened URL to the original destination URL.

✅ Expected Behavior

When accessing a shortened URL with query parameters like:

https://myzipline.io/r/abc123?utm_source=instagram&ref=partner

If the destination URL is:

https://example.com/landing

The final redirection should be:

https://example.com/landing?utm_source=instagram&ref=partner

That is: all query parameters from the shortened URL should be appended to the destination URL before redirecting.

💡 Optional Config

This behavior could be controlled via an environment variable or a config flag, such as:

forward_query_parameters: true

Or:

ZIPLINE_FORWARD_QUERY_PARAMS=true

🔒 Notes

• Existing query parameters in the destination URL should not be overwritten unless explicitly configured.
• Security and encoding must be handled properly to avoid injection or malformed URLs.

📦 Use Cases

• Marketing campaigns using UTM parameters
• Partner referral tracking
• Dynamic tracking without hardcoding parameters into destination URLs

---

Let me know if this feature makes sense for the roadmap. I’d be happy to contribute or test it! 🚀

Thanks for the awesome project! 🙏

— Rubens Flinco

[philskillz-coder]

I'd like to add:

Statistics per ref parameter (Counting the visits of shortened url per ref parameter)

Example:

?ref=web: 100x
?ref=email: 53x