When and why to use Link Param Propagator

What problem does it solve?

Many marketing, referral, and analytics campaigns rely on query parameters (like utm_source, utm_medium, utm_campaign, or affiliate codes) to measure the source and success of visits.

When a visitor clicks through to your site from a campaign link, those parameters appear in the URL of the first page they visit — but if the visitor clicks an internal link, those parameters are lost unless your site is built to carry them forward.

Losing them breaks attribution in analytics tools, which means your reports are incomplete or inaccurate.

How does this module help?

Link Param Propagator automatically:

1. Detects incoming query parameters you have configured.

2. Appends them to all matching internal links within targeted DOM elements.

3. Preserves the values as the visitor moves between pages.

This happens client-side, without altering stored URLs in your content or menus.

Benefits

• Consistent campaign attribution

  Keep tracking data intact from the first visit to the final conversion.

• No content edits required

  You don’t need to manually add parameters to every internal link.

• Flexible targeting

  Only append parameters to specific sections of your site, using CSS selectors.

• Support for multiple campaigns

  Configure multiple rules to handle different parameter sets and page areas.

Typical use cases

• Marketing Campaign Landing Pages

  You’ve shared a landing page link with UTM codes in ads, newsletters, or social media. You want those UTMs to follow the visitor into the checkout or form pages.

• Affiliate / Partner Referrals

  Your partners send visitors with a ref or partner_id parameter. You want to track this through the entire session.

• Multi-step Forms

  A visitor starts a multi-page form with tracking data in the URL — you want to pass it along until submission.

• Donation Funnels

  For non-profits, preserve campaign tags from the landing page all the way to the payment gateway.

When you don’t need it

• If you only need to capture parameters on the first page load (e.g., via server-side logging or analytics).

• If your site already uses a server-side query persistence mechanism that covers all internal links.

• If the parameters are sensitive and should not be exposed in subsequent page URLs.