Skip to main content
HandL UTM GrabberWebsite and marketing platforms

HandL UTM Grabber shows which ad each lead clicked. Google Ads still only learns "form submitted."

The plugin drops a first-party cookie on your WordPress site holding the UTMs, the gclid and the fbclid, then writes them into hidden fields on your Gravity Forms, WPForms or Elementor form, so every entry says which campaign sent it. What it can't do is tell Google Ads or Meta which entries became a booked consult or a funded case. Your ad account keeps bidding toward submissions, spam included. We close that loop from the gclid the plugin already stored, and put the accuracy in writing.

Free30 minutesNo obligation

HandL UTM Grabber · what breaks

What goes wrong with HandL UTM Grabber

  1. 01

    The gclid sits in the form entry, but Google Ads never hears about it

    The plugin stores the click ID and the GCLID Reporter turns it into a downloadable report of campaigns and keywords. Neither uploads a conversion, so Smart Bidding keeps optimizing for whatever your form-submit tag counts, at your cost per click.

  2. 02

    Every submission counts the same

    A spam entry, a job applicant and an executive-health consult all fire the same Lead event. Cost per lead looks fine while cost per real client climbs, and nobody can see it in the ad account.

  3. 03

    Leads arrive with empty UTM fields

    A caching layer, a consent banner nobody accepted or a plugin that loaded after the form, and the hidden fields come through blank. Those leads get filed as direct, and the ads that brought them look useless.

  4. 04

    The lead leaves WordPress before the money moves

    A tap on your phone number, a Calendly embed or a funding application on another portal. The cookie stays on your site; the booking or the funded case happens where the plugin can't see.

HandL UTM Grabber · the fix

What changes — HandL UTM Grabber

  • Google Ads learns from qualified leads

    Consults booked and cases funded go back against the stored gclid through offline conversion import, so bidding chases clients instead of submissions.

  • One Lead event per real inquiry

    Spam and existing clients filtered out; the plugin's CAPI call and your browser Pixel share one event ID so nothing counts twice.

  • Blank-field leads stop happening silently

    Capture verified on your live host with cache and consent in place, then monitored so a plugin update can't quietly empty the fields again.

HandL UTM Grabber · architecture

What HandL UTM Grabber actually lets you do

Everything below is in the vendor's docs. The plugin is a capture layer: good at storing the click, silent on what the click became.

  1. 1

    First-party cookie with UTMs and click IDs

    Captures utm_*, gclid, fbclid with _fbc and _fbp, msclkid, ttclid, referrer and landing page. Free plan keeps them 30 days; paid plans set the duration. wbraid and gbraid must be added as custom parameters.

  2. 2

    Hidden fields and shortcodes in 40+ form plugins

    One-click integrations for Gravity Forms, WPForms, Contact Form 7, Ninja Forms, Fluent Forms, Formidable and Elementor, shortcodes such as [utm_source] for any other field, and a Zapier or Make webhook on submit that carries the values to a CRM.

  3. 3

    GTM dataLayer push

    A handl_utm object on a handl_utms_ready event, which is where a tag should read the click ID instead of scraping the URL.

  4. 4

    Facebook Conversions API from the plugin

    Documented from v3.1 for Gravity Forms, Contact Form 7, Ninja Forms and WooCommerce. We confirm whether it deduplicates against your browser Pixel, because the docs don't say.

  5. 5

    GCLID Reporter

    Connects to your Google Ads account and emails a report tying each stored gclid to campaign, ad group, keyword and device. A report; nothing in the docs uploads a conversion.

  6. 6

    Phone click log

    Logs tel: taps with the UTMs attached, viewable in WP Admin and exportable to CSV. Nothing in the docs swaps numbers or records whether anyone answered.

HandL UTM Grabber · diagnose

Where HandL UTM Grabber tracking breaks, in diagnostic order

Start with capture, because if the hidden fields are blank, nothing downstream can be trusted.

  1. 01

    Count blank hidden fields in last month's entries

    A high blank rate points at caching, consent or load order; the vendor keeps a whole troubleshooting chapter for WP Engine, WP Rocket, Cloudflare and Kinsta for this.

  2. 02

    Check who writes the cookie and how long Safari keeps it

    Server-set or browser-set? Safari caps browser-written cookies at seven days, well under the 30-day default.

  3. 03

    Check whether the consent banner is blocking US visitors

    With the GDPR option or a consent-plugin integration switched on, the plugin writes nothing until the visitor accepts. A blanket opt-in banner your US visitors don't need is attribution lost on purpose.

  4. 04

    Count Lead events per submission in Events Manager

    The plugin's CAPI connection plus a browser Pixel on the thank-you page is the usual pair.

  5. 05

    Trace one gclid from form entry to Google Ads

    Submit from an ad-tagged URL, find the entry, then look for the conversion. The trail usually ends at the entry, and the same goes for a Calendly embed unless the plugin's Calendly guide is wired into the embed.

HandL UTM Grabber · prove

The QA evidence — HandL UTM Grabber

Run on your live site, through the cache and the consent banner, not on a staging copy.

Source of truth

Your form entries and CRM records — each inquiry with its HandL hidden-field values, its qualification status and whether it booked, funded or paid

  • One submission from an ad-tagged URL, with gclid and fbclid confirmed in the entry's hidden fields on the live host.
  • Blank-field rate measured over a closed month and reported as a number.
  • Exactly one Lead event per submission in Events Manager, with a shared event ID across the plugin's CAPI call and the browser Pixel.
  • A qualified lead and a booked consult uploaded to Google Ads against the stored gclid and visible in the conversion report.
  • A spam entry and an existing-client inquiry confirmed absent from every destination.
  • Phone-click log reconciled against answered calls for one week.
  • Repeated 30 days later and after the next plugin or theme update.

HandL UTM Grabber · free audit

What we check in the free audit

  • Count blank hidden fields in last month's entries
  • Check who writes the cookie and how long Safari keeps it
  • Check whether the consent banner is blocking US visitors
  • Count Lead events per submission in Events Manager
  • Trace one gclid from form entry to Google Ads

Checked against

Your form entries and CRM records — each inquiry with its HandL hidden-field values, its qualification status and whether it booked, funded or paid

Get my free conversion tracking audit

Free30 minutesNo obligation

HandL UTM Grabber · when not to buy

When you don't need this on HandL UTM Grabber

Sometimes the plugin plus a careful settings pass is enough.

  • If all you want is to know which campaign each lead came from, and you read it off the form entry, the plugin already does that.
  • If nearly every inquiry is worth about the same and spam is rare, a single form-submit conversion is close enough to feed bidding.
  • If your hidden fields are blank, fix caching, consent and load order first; the vendor's host-specific guides cover most of it and we'll point you to the right one.

HandL UTM Grabber · what we deliver

The event map on HandL UTM Grabber

  • Click ID captured

    gclid, fbclid and wbraid/gbraid confirmed in the cookie on your real host, after the consent step.

  • Form submitted

    Fired once from the form plugin with the hidden-field values attached; spam excluded at the source.

  • Lead qualified

    Marked in your CRM or intake sheet and sent to Google Ads and Meta as its own event.

  • Consult booked or application funded

    The conversion that carries value, matched to the original click by its stored gclid.

  • Phone clicks reconciled

    The plugin's tel: click log lined up against answered calls, so a tap isn't counted as a lead.

  • Excluded on purpose

    Existing patients, job applicants, vendor pitches and anything the hidden fields show came from your own email list.

Written guarantee

95%+ tracking accuracy

Measured against Your form entries and CRM records — each inquiry with its HandL hidden-field values, its qualification status and whether it booked, funded or paid. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

HandL UTM Grabber questions, answered

No. It stores the gclid in a cookie and writes it into your form; the GCLID Reporter turns stored gclids into a downloadable report of campaigns and keywords. Sending a conversion back is a separate step, done by offline conversion import from your records.

Free · 30 min

Get HandL UTM Grabber tracking right

Free30 minutesNo obligation