URL Parameters and Merge Fields in Sparkforge Websites and Funnels

By Sparkforge Support Team ·Last reviewed May 3, 2026

Sparkforge websites and funnels resolve {{keyword}} placeholders against merge fields first, then URL parameters. That lets every visitor see content tailored to them — name, location, or anything else you pass in the URL.

Sparkforge websites and funnels look for {{keyword}} placeholders on every page load and replace them with dynamic content. The replacement source can be a merge field from the database or a parameter pulled straight from the URL.

The Three Building Blocks

URL Parameters

Anything appended to the URL as key=value pairs after a ?. Example: https://example.com?first_name=Yolonda. Use them to display per-visitor content or jump to a specific page section.

UTM Parameters

A standardized type of URL parameter for marketing tracking — utm_source, utm_medium, utm_campaign, and so on. They feed reporting but do not render on the page.

Merge Fields

Placeholders Sparkforge resolves from the database, like {{contact.email}} or {{location.full_address}}. Sparkforge swaps the tag for the live value when the page (or email) renders.

Merge Fields Already in Templates

Many Sparkforge templates ship with merge fields wired in. Common examples:

  • {{location.full_address}} — sub-account business address
  • {{location.phone}} — sub-account business phone
  • {{location.name}} — sub-account business name

Using Custom URL Parameters

You can invent your own parameters and reference them with the same {{keyword}} syntax. To test:

  1. Edit a heading or text block. Replace Welcome to {{location.name}} with Hi {{first_name}}, Welcome to {{location.name}}.
  2. Save the page.
  3. Open the page preview. The placeholder shows blank because no parameter is in the URL yet.
  4. Append ?first_name=Yolonda to the URL bar and reload. The page now reads "Hi Yolonda, Welcome to ...".

Pass Parameters Through Links

Once your page reads URL parameters, every link pointing at that page should include them. In an email you can hard-code values, but a contact's name should come from a merge field so the link populates per recipient.

Reuse Dynamic URLs With Custom Values

If you need the same dynamic URL in several places, store it as a custom value:

  • Custom value holds only the URL: https://app.sparkforge.com/v2/preview/Gqzf1j5aVuAsZbEQEo79. Build the link as {{ custom_values.yoga_page }}?first_name={{contact.first_name}}.
  • Custom value holds the URL and the parameter: https://app.sparkforge.com/v2/preview/Gqzf1j5aVuAsZbEQEo79?first_name={{contact.first_name}}. Reference it directly as {{ custom_values.yoga_page_with_params }}.

Frequently Asked Questions

What is the difference between a merge field and a URL parameter?
Merge fields pull from the Sparkforge database (contact, location, custom value). URL parameters are key=value pairs you append to the link itself.
Do UTM parameters render on the page?
No. UTMs feed reporting and tracking only. They do not display content.
What if a parameter is missing from the URL?
The placeholder renders empty. Plan copy so the page still reads cleanly when no value is passed.
Can I nest merge fields inside a URL stored in a custom value?
Yes. Either keep the URL static and add the merge field at the link level, or bake the merge field into the custom value itself.
Can I use parameters to scroll to a section?
URL parameters are most often used for content swaps; section anchors use the standard #anchor syntax in the URL.

Was this article helpful?