Brad Holly

<p>AdTrails UTM Grabber for CF7 will push UTM data into your form submissions for ROI purposes. Are you looking for Gravity Forms, WP Forms, and Ninja Forms compatability? We offer a premium version of the plugin at AdTrails.com.</p>
<p>For backwards compatibility, if this section is missing, the full length of the short description will be used, and<br />
Markdown parsed.</p>
<p>A few notes about the sections above:</p>
<ul>
<li>Actuate Media</li>
<li>UTM Grabber, UTM Tracker</li>
<li>“Requires at least” is the lowest version that the plugin will work on</li>
<li>“Tested up to” is the highest version that you’ve <em>successfully used to test the plugin</em>. Note that it might work on<br />
higher versions… this is just the highest one you’ve verified.</li>
<li>
<p>Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use <code>/trunk/</code> for<br />
stable.</p>
<p>Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so<br />
if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that’ll be used<br />
for displaying information about the plugin.  In this situation, the only thing considered from the trunk <code>readme.txt</code><br />
is the stable tag pointer.  Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in<br />
your in-development version, without having that information incorrectly disclosed about the current stable version<br />
that lacks those changes — as long as the trunk’s <code>readme.txt</code> points to the correct stable tag.</p>
<p>If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where<br />
you put the stable version, in order to eliminate any doubt.</p>
</li>
</ul>
<h3>Arbitrary section</h3>
<p>You may provide arbitrary sections, in the same format as the ones above.  This may be of use for extremely complicated<br />
plugins where more information needs to be conveyed that doesn’t fit into the categories of “description” or<br />
“installation.”  Arbitrary sections will be shown below the built-in sections outlined above.</p>
<h3>A brief Markdown Example</h3>
<p>Ordered list:</p>
<ol>
<li>Some feature</li>
<li>Another feature</li>
<li>Something else about the plugin</li>
</ol>
<p>Unordered list:</p>
<ul>
<li>something</li>
<li>something else</li>
<li>third thing</li>
</ul>
<p>Here’s a link to <a href="https://wordpress.org/" title="Your favorite software" rel="ugc">WordPress</a> and one to <a href="https://daringfireball.net/projects/markdown/syntax" title="Markdown is what the parser uses to process much of the readme file" rel="nofollow ugc">Markdown’s Syntax Documentation</a>.<br />
Titles are optional, naturally.</p>
<p>Markdown uses email style notation for blockquotes and I’ve been told:</p>
<blockquote>
<p>Asterisks for <em>emphasis</em>. Double it up  for <strong>strong</strong>.</p>
</blockquote>
<pre><code><?php code(); // goes in backticks ?>
</code></pre>


AdTrails UTM Grabber

Haktan Suren

<h4>UTM Tracking for WordPress (Built for Attribution)</h4>
<p>UTM Grabber helps marketing teams reduce attribution loss between click and conversion.</p>
<p>It captures UTM parameters and click IDs on first visit, stores them in first-party cookies, and makes them available site-wide so your forms, CRM syncs, and checkout flows keep campaign context intact.</p>
<p>Trusted by over <strong>250,000 WordPress sites</strong>, UTM Grabber is built for teams that need reliable source data to scale what works.</p>
<blockquote>
<h4>What you get in the free plugin</h4>
<ul>
<li>Capture the core attribution parameters: <code>utm_source</code>, <code>utm_medium</code>, <code>utm_campaign</code>, <code>utm_term</code>, <code>utm_content</code>, and <code>gclid</code></li>
<li>Store attribution data in first-party cookies</li>
<li>Use shortcodes to inject tracking values into forms and content</li>
<li>Track key context fields like referrer and landing page</li>
<li>Push clean attribution data into major workflows (forms, WooCommerce, CRM automations)</li>
<li>Includes iOS 14+ friendly tracking support</li>
</ul>
</blockquote>
<h4>Why teams choose UTM Grabber</h4>
<ul>
<li><strong>Attribution continuity:</strong> Preserve campaign context beyond the first pageview and across the customer journey.</li>
<li><strong>First-party data model:</strong> Your attribution data stays in your WordPress stack.</li>
<li><strong>Built for real WordPress setups:</strong> Designed for form-heavy, plugin-heavy, and marketing-driven sites.</li>
<li><strong>Fast to deploy:</strong> Activate, map fields, and start collecting usable source data quickly.</li>
</ul>
<h4>Major integrations and compatibility</h4>
<p>UTM Grabber works with the most-used WordPress forms and revenue plugins out of the box:</p>
<ul>
<li>Contact Form 7</li>
<li>Gravity Forms</li>
<li>Ninja Forms</li>
<li>Elementor</li>
<li>WPForms</li>
<li>Formidable Forms</li>
<li>Caldera Forms</li>
<li>Thrive Leads</li>
<li>WooCommerce</li>
<li>Ultimate Member</li>
<li>Fluent Forms</li>
<li>Forminator</li>
<li>Typeform</li>
<li>Webflow</li>
<li>and many more</li>
</ul>
<p>Need CRM or ops workflow delivery? UTM Grabber integrates with automation platforms so you can route attribution to tools like:</p>
<ul>
<li>Salesforce</li>
<li>HubSpot</li>
<li>Pipedrive</li>
<li>Zoho</li>
<li>ActiveCampaign</li>
<li>Google Sheets</li>
<li>Slack</li>
<li>Mailchimp</li>
<li>Klaviyo</li>
<li>and many others via Zapier/Make</li>
</ul>
<h4>Upgrade to HandL UTM Grabber V3</h4>
<p>Upgrade to unlock the full attribution stack and advanced controls:<br />
<a href="https://utmgrabber.com/?utm_source=WordPress_FREE&utm_medium=wordpress_update_link&utm_campaign=HandL_Plugin_Page" rel="nofollow ugc"><strong>See all premium features</strong></a></p>
<ul>
<li>Facebook Conversion API (FB CAPI) workflows for paid social and WooCommerce</li>
<li>AI-Powered Insights for anomaly detection and optimization recommendations</li>
<li>GCLID Reporter for Google Ads click tracking and offline conversion workflows</li>
<li>Track all UTM + advanced click IDs (<code>fbclid</code>, <code>gclid</code>, <code>msclkid</code>, ValueTrack) and custom parameters</li>
<li>First-touch and last-touch attribution fields</li>
<li>Track source categories (Paid, Organic, Referral, Direct)</li>
<li>Customize cookie duration to match your sales cycle</li>
<li>Server-side and client-side tracking options</li>
<li>Google Analytics client ID tracking</li>
<li>Cross-domain/iframe attribution passing</li>
<li>Site-to-site (S2S) postback options</li>
<li>Expanded integrations for forms, CRMs, and automation workflows</li>
<li>GDPR-ready setup with broad consent-tool compatibility</li>
</ul>
<h4>Documentation, support, and community</h4>
<ul>
<li><a href="https://docs.utmgrabber.com/?utm_medium=referral&utm_source=wordpress.org&utm_campaign=HandL+UTM+Grabber+Readme&utm_content=Documentation" rel="nofollow ugc">Documentation</a></li>
<li><a href="https://wordpress.org/support/view/plugin-reviews/handl-utm-grabber#postform" rel="ugc">Leave a review</a></li>
<li><a href="https://www.haktansuren.com/slack-handlwp/" rel="nofollow ugc">Join support Slack</a></li>
</ul>
<p><strong>SPECIAL THANKS:</strong> This plugin has been tested on various operating systems and browsers thanks to <a href="https://www.browserstack.com" rel="nofollow ugc">BrowserStack!</a></p>


HandL UTM Grabber / Tracker


UTMs should never be used internally. Analytics tools start a new session every time a UTM is passed.This is why they should be used only for external links incoming to your site.The default option on this plug-in (and it shouldn't even be an option) is to append UTMs to all CTAs.Very bad practice. Giving 1 star to warn others.


This Plug-in Breaks Tracking

The WordPress attribution plugin used by over 250,000+ sites to capture UTMs, gclid, and source data in your forms, CRM, and revenue workflows.

AdTrails UTM Grabber vs HandL UTM Grabber / Tracker