A simple shortcode to get URL parameters from the Query String and display them as dynamic content on pages, posts and forms.
URL parameters are tags that are added to the end of your URL, usually for tracking purposes or for dynamic content insertion.
The most known type of URL parameters is UTM parameters, used by Google and Facebook ad links, in order to find out more about how your visitors interact with your ad.
With our Dynamic Text Replacement shortcode, you can access URL parameters in the Query String of the URL and display it on your pages, post or even use it to pre-fill forms.
Works with ACF, Beaver Builder, Visual Composer (WPBakery Page Builder) etc
You can do this if you want to use URL parameters on your page to dynamically display things like location or someone’s name if you already have that information.
Make sure the page’s URL includes the parameters you want to use, such as https://mylandingpage.domain.com/?location=Sydney&name=Chris
Then you can write the copy of any text element on the page to include those parameters, such as “Hello [URLParam param=’name’]! Welcome to [URLParam param=’location’]!”
This example would display as “Hello Hannes! Welcome to Sydney!”
[URLParam param='paramname']
Shows the value of GET named paramname (‘Hannes’ in the example URL), or “blank value” if none given.
Hello Hannes!
Shows the value of GET named paramname, or empty space if none
Easiest way:
If you cannot install from the WordPress plugins directory for any reason, and need to install from ZIP file:
/wp-content/plugins/
directory, or upload the ZIP file directly inThere is a known problem where the plugin shortcodes are used within URLs or other HTML attributes which are themselves inside quotes.
Starting in the WordPress 4.2.3 security auto-update, you can no longer include shortcodes in HTML attributes. Previous to this WordPress update, you could set a field value like this: . Now you have to set it like this: or [urlparam htmltag=”input” type=”text” name=”firstname” attr=”value” param=”FirstName” /]. If you are still using this shortcode the old way, unfortunately, WordPress simply won’t process the shortcode and will return back the full shortcode text unprocessed.
In short, no. To help protect your site against Reflected Cross Site Scripting, we sanitize output with esc_html() which prevents any HTML tags from being passed in and displayed. This would prevent someone from passing in javascript, for example, and having it execute on your site.
Please help each other on the public support forums.
Fixed error with http:// appearing before params on page.
First version