Medium Interactive

Multi-Page Campaign Tracking automatically captures and persists specific URL parameters (like UTM tags and campaign data) across multiple page visits. This is essential for accurate marketing attribution and analytics tracking.
Persistent UTM Parameters for Accurate Marketing Attribution 
Are You Missing Attribution On Your Marketing Campaigns? 
You launch an ad campaign, post on social media, send an email blast, or invest in a press release. Traffic starts coming in—but when you look at your analytics or CRM, attribution is incomplete or missing altogether. Visitors arrive on your site with UTM parameters in the URL, click to another page, fill out a form, and the original source data disappears. This leads to unclear reporting, unreliable conversion data, and marketing decisions based on guesses instead of facts. This plugin solves that problem.
What This Plugin Does 
Persistent UTM Parameters ensures that UTM parameters—and other query parameters you define—persist as users navigate your website. 
If a visitor arrives on your site with tracking parameters in the URL, those parameters are automatically carried forward as they move from page to page. When the visitor eventually submits a form, requests a quote, or reaches a key conversion point, the original attribution data is still intact. 
This allows you to correctly attribute form submissions, lead sources, campaign performance, content engagement, and conversions with confidence.
Why This Matters 
Without persistent parameters, attribution is often lost after the first page view, forms submit without source data, analytics platforms misclassify traffic, and even high-cost campaigns can appear ineffective. 
With persistent parameters in place, source, medium, and campaign data remain accurate throughout the user journey. Marketing ROI becomes measurable, CRM records receive clean attribution data, and analytics reflect how users actually discover, engage with, and convert on your site. 
This is especially important for marketing teams, agencies, lead-generation websites, SaaS companies, service businesses, and anyone who relies on accurate attribution to make informed decisions.
Fully Customizable Parameter Support 
While UTMs are the most common use case, this plugin is not limited to them. You can choose which query parameters should persist, include custom parameters beyond standard UTMs, and adapt the plugin to your existing analytics, CRM, or form setup. This flexibility supports advanced marketing stacks, custom tracking needs, and non-standard attribution models.
Simple Setup — Expert Help Available 
The plugin is designed to work out of the box with minimal configuration. For more advanced setups—such as passing parameters into specific form fields, CRMs, or analytics platforms—expert help is available to ensure everything is configured correctly.
GET SUPPORT 
<a href="https://mediuminteractive.com/contact" rel="nofollow ugc">https://mediuminteractive.com/contact</a>

Multi-Page Campaign Tracking

Persist query string parameters across page visits for tracking and analytics purposes.

fculross

Page Guard uses a single URL parameter or POST variable as a means of providing a token to guard access to any page on which this plugin’s shortcode is placed. Output of alternative content can be made to occur when the token is missing or fails to match what is expected – if the token received matches the expected one, the controlled content can be revealed to the visitor.
For this version, an additional shortcode attribute “title” also allows the page title to be changed conditionally PROVIDED JAVASCRIPT IS ENABLED IN THE BROWSER (it has no effect if JavaScript is turned off!)
The shortcode to use is ‘pageguard’ – its attributes are:
<pre><code>tokenparam (required) -> a string value containing the name of the token URL param - e.g. 'mytoken'
eq (optional) -> a string value containing the expected value of the tokenparam - e.g. 'x34ggj45b'
ne (optional) -> as for "eq" but when used, shortcode will output content on non matching token
absent (optional) -> when absent="1", shortcode will output content on detection of missing token
title (optional) -> a string containing a page title to apply when the parent shortcode's criteria are met 
</code></pre>
Syntax examples:
<pre><code> show block on matching token -
 [pageguard param="token" eq="download"]
 Text to be output on matching token found
 [/pageguard]

 show block on non match + change title
 [pageguard tokenparam="token" ne="download" title="Downloads - invalid token"]
 Error text for output when token fails to match
 [/pageguard]

 show this on no token found + change title
 [pageguard tokenparam="token" absent="1" title="Downloads - missing token"]
 Error text for output when token is missing
 [/pageguard]
</code></pre>
<h3>Usage</h3>
A typical use scenario might be to control access to a downloads page. Suppose you have a PayPal “Buy Now” button on your site which allows visitors to make a payment for say, an eBook or audio recording. When setting up the button in your PayPal account you specify a URL on your site to which the visitor is returned after they’ve made payment. On this return page you’ve added a link the visitor can use to download their purchase – however, you don’t want any non paying visitors to have access to the download link(s) on the page! If you also want the page title to reflect any error conditions, you an use the “title” attribute to do this (please be aware however that this functionality depends on JavaScript being enable in the user’s browser – it disabled, “title” has no effect.)
Add a parameter to the end of the return URL (using any name and value you want) when you set up your button in PayPal e.g.
<pre><code>"http://your.wordpress.site/download/?dltoken=x34ggj45b"
</code></pre>
Next, add pageguard short codes for the cases you intend to handle to your return page in WordPress –
<pre><code>[pageguard param="token" eq="x34ggj45b" title="Title for matched token"]
Text to be output on matching token found
[/pageguard]

[pageguard tokenparam="token" ne="x34ggj45b" title="Title for failed match"]
Error text for output when token fails to match
[/pageguard]

[pageguard tokenparam="token" absent="1" title="Title for missing token"]
Error text for output when token is missing
[/pageguard]
</code></pre>
This will correctly display the main content for the page when Page Guard detects a matching token. It also provides for the possibility of providing different error content for the page in the event of the token being incorrect or missing.

Page Guard

Adds a short code which allows conditional output of page content and title based on the value of a token passed as a URL parameter or a POST variable

Multi-Page Campaign Tracking vs Page Guard