Skip to main content

You embed a Fillout form, leads land in your inbox, and a few weeks later someone notices Google Ads reports a fraction of them. The form works fine. The tracking around it doesn't. The same failure shows up with every embedded form tool, which is why we've also written up Typeform conversion tracking using the same approach.

Why don't Fillout form submissions show up as conversions?

Because the form usually runs inside an iframe on a different domain from your page, and the tags on your page can't see what happens in there. Your GTM container's form and click triggers listen to your page, not the frame, so the submit button never reaches them. Four things go wrong, usually together:

  1. Cross-origin isolation. GTM's form trigger, GA4's enhanced measurement form events and click triggers on the parent page all miss the submit.
  2. No URL change. Embeds finish on Fillout's ending page inside the frame, so a thank-you page trigger has nothing to fire on.
  3. Click IDs that never reach the form. The gclid or fbclid sits on the landing page URL and is gone after one more click unless you stored it. Fillout's own Google Ads guide says its GCLID capture reads the landing page URL, not cookies.
  4. Third-party cookie rules. Tracking inside the iframe runs in a third-party context, where Safari and Firefox restrict cookies, so identifiers in the frame don't match your page's.

Our guide to form conversions that don't fire covers the general debugging order.

What tracking does Fillout offer out of the box?

Fillout has a native Meta Pixel integration, a Google Tag Manager connection, custom code, a paid Google Ads add-on, redirect-on-submit, webhooks and URL parameters. Here's what Fillout's help docs say about each, and where each stops.

Fillout featureWhat it doesRequirement (per Fillout docs)Where it falls short
Meta Pixel (Integrate → Facebook Pixel)Sends Fillout.FormPageViewed and Fillout.FormSubmitted with the form ID in content_category and the page number in valueBusiness and Enterprise plansCustom event names, not Lead; no Conversions API, no event_id, no customer data
Google Tag Manager (Integrate → Tag Manager)Loads your GTM container on the form itselfA connected custom domainNo automatic dataLayer events; you write dataLayer.push calls in HTML or custom code blocks yourself
Custom code (Settings → Custom code)Injects scripts into the live formA connected custom domain; doesn't run in previewStill browser-side, still blockable
Conversion kit → Google AdsCaptures GCLID on submit and builds a CSV for Google Ads uploads, optionally with email and phone for enhanced conversionsPaid conversion kit add-onManual CSV download and upload; Fillout lists automatic uploads as planned, not available
Ending page → RedirectSends respondents to an external URL after submitStarter plan and upFillout's docs don't say whether an embedded form redirects the frame or the whole page; test it
Webhook (Integrate → Webhook)POSTs each submission to your URL, with optional custom headersCheck your planComes from Fillout's servers, so it has no visitor IP or browser user agent
URL parameters / hidden fieldsStores values passed in the form link or inherited from the embedding pageEach parameter registered in form settings firstValues only arrive if your page supplies them

One more: Fillout's @fillout/react package exposes an onSubmit callback with the submission UUID, the only documented way I found for the parent page to know a submit happened. I couldn't find an equivalent documented for the plain HTML snippet.

How do I pass gclid, fbclid and UTMs into a Fillout form?

Register each one as a URL parameter in the form, then let the embed pick the values up from your page. Fillout's embed docs say embeds automatically inherit URL parameters from the parent page through the data-fillout-inherit-parameters attribute, and you can add any other value as a data- attribute named after the parameter.

  1. In the form editor, open settings with the gear icon, choose URL parameters and add gclid, fbc, fbp, utm_source, utm_medium, utm_campaign and a lead ID such as leadid. Add gacid if you want to send GA4 events server-side.
  2. If an integration needs these values as fields, create a field, set its Default value to the parameter and choose Hide always, which is how Fillout's docs describe hidden fields.
  3. On landing pages, save click IDs to a first-party cookie on arrival so they survive browsing.
  4. On the page with the form, set the values on the embed element before Fillout's script loads.
  5. Submit a test and check the values in Fillout's results. Blank here means blank everywhere.
<div id="quote-form"></div>
<script>
  function ck(n){var m=document.cookie.match('(?:^|; )'+n+'=([^;]*)');return m?decodeURIComponent(m[1]):'';}
  var q = new URLSearchParams(location.search);
  var fbclid = q.get('fbclid');
  var leadId = crypto.randomUUID();
  sessionStorage.setItem('leadid', leadId);   // reused by the browser-side event

  var el = document.getElementById('quote-form');
  var attrs = {
    'data-fillout-id': 'YOUR_FORM_ID',
    'data-fillout-embed-type': 'standard',
    'data-fillout-inherit-parameters': '',
    'data-fillout-dynamic-resize': '',
    'data-gclid': q.get('gclid') || ck('lp_gclid'),
    'data-fbc': ck('_fbc') || (fbclid ? 'fb.1.' + Date.now() + '.' + fbclid : ''),
    'data-fbp': ck('_fbp'),
    'data-leadid': leadId
  };
  for (var k in attrs) el.setAttribute(k, attrs[k]);

  var s = document.createElement('script');
  s.src = 'https://server.fillout.com/embed/v1/';
  document.body.appendChild(s);
</script>

The leadid is the piece most setups skip. It's generated on your page, travels into the submission and comes back in the webhook, which is what lets you deduplicate browser and server events.

Should the conversion fire from a thank-you page or from the server?

From the server, with a browser event alongside it for Meta. A thank-you page is the classic fix: set the ending to Redirect, point it at /thank-you on your domain, fire tags there. But people reload it and bookmark it, ad blockers still strip the tags, and if the redirect loads inside the frame, your page's tags never see it.

The webhook fires once per real submission and can't be blocked by an extension. Fillout's API docs say webhook deliveries use the same format as submission records, which include a submissionId, submissionTime, the questions and a urlParameters array. That's everything a conversion API needs except the visitor's IP and user agent.

So the webhook is the conversion of record. A browser event (thank-you page or React onSubmit) fires with the same leadid, mainly to give Meta browser context, and the two are deduplicated.

How do I send Fillout leads to Meta CAPI, Google Ads and GA4 server-side?

Point Fillout's webhook at an endpoint you control, hash the personal data and forward one event per platform. In Fillout that's Integrate → Webhook; add a secret in the optional headers so your endpoint can reject anything that isn't Fillout.

Fillout sourceMeta Conversions APIGoogle Ads (click conversion upload)GA4 Measurement Protocol
Email answeruser_data.em, SHA-256 of trimmed lowercasehashed_email user identifierDon't send
Phone answeruser_data.ph, digits with country code, SHA-256hashed_phone_number, E.164 then SHA-256Don't send
gclid parameterNot usedgclidNot used
fbc / fbp parametersuser_data.fbc / user_data.fbpNot usedNot used
leadid parameterevent_idorder_idEvent parameter
gacid parameterNot usedNot usedclient_id
submissionTimeevent_time (Unix seconds)conversion_date_timetimestamp_micros

Meta. Send a Lead event with action_source set to website and event_id set to the leadid. Fire the browser pixel's Lead on your page with the same value as eventID, and Meta keeps one. Meta requires client_user_agent for website events and the webhook lacks it, so pass it as another URL parameter or let the browser event carry it. The difference between the two channels is covered in Meta Pixel vs Conversions API.

Google Ads. Fillout's conversion kit gives you a CSV to upload by hand: fine for a test, too slow for bidding. Upload through the Google Ads API instead, using the GCLID plus hashed email and phone, which is how enhanced conversions for leads matches people whose click ID went missing. Set order_id to the leadid so a retried webhook can't double count. Pick one source per conversion action: if the server upload is primary, don't also count a browser tag into the same action. Our enhanced conversions setup guide covers the account-side settings.

GA4. Send generate_lead through the Measurement Protocol with the client_id you passed in as gacid. Without it, GA4 can't tie the lead to the session that produced it.

How do I send lead quality back, not just form fills?

Send a second conversion when the lead becomes worth something, keyed to the same identifiers you stored at submit time. If half your leads are students and tire kickers, smart bidding will happily find you more of them.

  1. Push each submission into your CRM with gclid, fbc, fbp, leadid and the hashed email and phone on the record.
  2. Define one or two outcomes that matter: qualified, booked, closed-won.
  3. When a record hits that stage, upload a Google Ads conversion to a separate action ("Qualified lead") with the stored GCLID and hashed identifiers, and send Meta a matching server event with the same user_data.
  4. Once the qualified action has enough steady volume, make it the primary goal and demote the raw form fill to secondary.

Why does first-party server-side tracking fix what Fillout's defaults miss?

It moves measurement out of the iframe and the browser, onto a server on your own subdomain. Fillout's pixel runs in a frame you don't own, on cookies Safari treats as third-party. The webhook knows the lead but not the browser. Each piece has half the picture.

A server-side GTM container on something like data.yourdomain.com joins the halves:

  • First-party identifiers that last. The container can set _fbp, _fbc and the click-ID cookie from your own domain via HTTP headers, so they survive Safari's limits on script-set cookies. Those are the values you hand to the embed.
  • Browser context on the server. The browser Lead hits your container, which sees the real IP and user agent. The webhook event carries hashed email and phone. Same event_id, so Meta merges them.
  • Ad blockers stop mattering. Requests to your own subdomain generally aren't on the blocklists that strip third-party pixels, and the webhook path never touches the browser at all.
  • One place for rules. Hashing and opt-out handling happen once, in the container.

Starting from zero? See our server-side GTM setup guide.

What do CCPA and CPRA mean for Fillout lead data?

Sending a lead's email and phone to Meta or Google for ad purposes is likely "sharing" under the CCPA as amended by CPRA, so California visitors need a working opt-out. A SHA-256 email is still personal information; hashing only makes it unreadable in transit.

  • Read Global Privacy Control (navigator.globalPrivacyControl) and your own "Do Not Sell or Share" choice on the parent page, and pass it into the form as one more parameter.
  • On the server, set Meta's Limited Data Use (data_processing_options) and Google's restricted data processing for opted-out leads, or drop the ad-platform events for them.
  • Send identifiers only. Form answers about health, finances or anything sensitive never belong in a conversion payload.

For EU traffic, Fillout's Meta Pixel doc mentions a cookie banner you can toggle in form settings.

Frequently asked questions

Does Fillout have a native Meta Pixel integration?

Yes, on Business and Enterprise plans. It sends custom events named Fillout.FormPageViewed and Fillout.FormSubmitted, not the standard Lead event, and it doesn't use the Conversions API.

Can Google Tag Manager track an embedded Fillout form?

Not from your page's container, because the form runs in a cross-origin iframe. Fillout can load GTM on the form itself via a custom domain, but you write the dataLayer pushes.

How do I capture the gclid in a Fillout form?

Register gclid as a URL parameter in form settings, keep data-fillout-inherit-parameters on the embed, and store the GCLID in a first-party cookie on arrival.

Does Fillout upload conversions to Google Ads automatically?

Not according to its current docs. The conversion kit add-on produces a CSV you upload manually, and Fillout lists automatic uploads as planned.

Do I need a thank-you page redirect if I use the webhook?

Not for counting. It's still a good place to fire a browser event with the same lead ID, giving Meta browser context for matching.

How do I stop Fillout leads being counted twice?

Generate one lead ID on your page and pass it into the form. Use it as event_id for Meta on both pixel and server events, and as order_id on Google Ads uploads.

If your Fillout leads and ad platforms disagree, the gap is usually the iframe and missing click IDs. We can rebuild it on first-party server-side tracking: webhook-driven conversions, deduplicated browser events and qualified-lead feedback. About 98% accuracy is typical, and we guarantee 95%+. Tell us how your forms are set up and we'll show you where the leads are going missing.

  • fillout
  • meta conversions api
  • enhanced conversions
  • hidden fields
  • webhooks
SETUP GUIDES

Guides for this topic

How accurate is your conversion tracking?

PLATFORM-REPORTEDconversionsdivided byBACKENDreal orders or leadsequalsaccuracy
TRY IT · YOUR NUMBERS
68%Broken. Something is missing entirely. Worth a free audit.
Reading guides because something is broken?Book 30 minutes with Ariful. We'll find it on the call and send a written fix list within 24 hours.
Get my free audit →
Ariful Islam
WRITTEN BYAriful IslamFounder of Tracking Consulting and a computer engineer (Diploma, BSc, MSc in CSE). 300+ clients and 1,000+ tracking projects since 2019.
About Ariful →
FREE · 30-MIN CALL · WRITTEN AUDIT IN 24H

Want us to check your accuracy for you?

We look at your setup together on the call. Within 24 hours you get a written audit and a prioritized fix list you can hand to any developer. Not a fit? We'll say so.