Keeping a URL Parameter persistent across internal website pages

I have a Fillout.com form embedded on a page in Softr. Currently, I have it set up so that a URL parameter is passed to the form successfully, which is working as expected. You can check it out here:

However, I need help with ensuring the URL parameter remains persistent as a user navigates between different pages on my Softr site. Specifically, I want the parameter “gasummitspeaker” to be retained so that when a user explores other pages and then returns to the form, it still has access to that parameter.

I assume users will browse the site before submitting the form, so maintaining the parameter across page visits is crucial for tracking and attribution.

Has anyone implemented a solution for this in Softr? Any insights, best practices, or workarounds would be greatly appreciated!

Thanks in advance!

Keeping the param present won’t be an option, unfortunately. There may be some other ways to accomplish this though.

You can save that parameter via hidden fields from the URL parameter to the loggedin user, and then use that field on the user to properly define conditional logic and record filtering. Even user groups. Is that an option?

@Jjenglert unfortunately this is a tracking link that I want to give my speakers to promote a conference. When users register for the conference, following there link, I want to drop there custom URL Parm into a Fillout Form. So they aren’t yet a logged in user.

Also, I am counting on the user exploring other pages on the site before returning to the registration and filling it out with a purchase to the conference.

I think you will need to modify your experience a bit to get the result you’re looking for. Maybe you can build a one page landing that keeps them there, but also provides the info they are looking for to keep the URL present?

Also, why fillout and not our conditional forms?

I want a multi step form that is branded like all the other forms and that I can have a page on it that is conditional, pushing them to specific Stripe payment pages in the form. I am not aware that Softr, conditional forms can complete that.

Yeah, we can have that. We have conditional endings, and if they qualify, you can navigate them to a stripe checkout page. It would make it easier to save this data in your connected base, and maybe make tracking easier as well.

Maybe there is a way that you can accomplish this with custom code (to keep the param visible on all page loads). I’d personally try to find a more simple solution.

Thanks for your assistance.

I can see using a tracking link as a legit use case for Softr to consider. It is a bummer that I can’t do this and I have to use a landing page method. This kind of things seems to fit right on Softr’s use case.