Hello, long-time lurker, first-time poster. I do not have a read-only link to share so I will try and type out my questions as best I can. I wasn’t able to see or find any answers in the Webflow forum or blog, but happy to look into anything if someone can point me in the right direction.
I should also say I am a Project Manager for a web development company with limited dev experience, but this question came to me after watching the Ryan Renolds Landing page course.
I have a client who currently creates landing pages through WordPress … it’s a bear, and I would love to try and convert them after watching that course. The one thing they have currently that I can’t find an answer to is the integration of a persistent URL parameter. They currently drive traffic to these landing pages, but the URL parameter stays with the user even if they don’t fill out the LP form.
As an example, a user would land on the page from a Google ad banner but immediately click on the logo to take them to the homepage vs engage in the landing page form. The same URL parameter that was appended to the landing page URL to track them from the Google Ad banner stays with them on the homepage and/or any proceeding page after. Is that something that can be done through Webflow?
Again, happy to review any source or provide more info if people have questions.
Thanks so much
Typically on Webflow I handle referrer tracking by capturing the URL parameter on the landing page and storing it in sessionStorage. Then it’s available when needed, e.g. to submit with a form.
If you really want it to appear on the querystring throughout, you need to capture that param from the querystring and then apply it to every other link on the page using script, so that it gets carried through navigations.
The Sygnal Attributes library does that-
Thanks, Michael. Super helpful!
Hello Michael, I began using the Sygnal Attributes library to do it. I can get the $url.search but how do i parse it to the next page and append the url to have the param too? I can’t seems to understand the library or know about the script. Any help will be great. Thanks!
Good question- and yes this has changed. In Aug 2023, SA5’s URL querystring feature pivoted to focus & expand on the data-binding aspects, e.g. querystring value to form select field binding.
The SA5 community elected to remove the page-wide link-update mechanism, as it’s a bit ugly to have the tracking querystring on the URL. Most users preferred more elegant localStorage implementations instead.
So, it depends on what you’re trying to do. Each client build is a bit different.
Thanks a lot! I see…How does the localStorage implementations work? Very new to parsing UTM links
Hi Z, you can google localStorage to learn all the basics, but if you’re not familiar with coding, you may not be able to create what you need.
I build systems like this often, drop me a message if you need some dev work done.