How to Track Demo Request Forms in GA4 With generate_lead

Rakibul SumonRakibul Sumon
Published: Nov 18, 2026
How to Track Demo Request Forms in GA4 With generate_lead

TL;DR Summary

Track confirmed demo requests in GA4 with generate_lead. Set up the GTM trigger, test failure cases, and reconcile confirmed leads with your CRM.

Send GA4's generate_lead event when your demo request is accepted. A click tells you someone tried to book a demo. A successful form response tells you the request exists. If confirmation happens inside an embedded calendar, use the platform's documented completion callback or integration.

Trigger the event where you can verify success

On a form you control, have the application push a data layer event after the backend accepts the request. This example assumes the application already guards against retries and repeated callbacks for the same request.

window.dataLayer = window.dataLayer || [];

window.dataLayer.push({event: "demo_request_confirmed", form_location: "pricing", form_variant: "short"});

In Google Tag Manager, add a Custom Event trigger for demo_request_confirmed. Configure a GA4 Event tag for generate_lead using your intended Google tag. Pass only the reporting parameters you need, such as form location. Keep names, phone numbers, email addresses, and other personally identifying information out of GA4. Check Google's recommended event reference for the event definition.

A thank-you page should emit the event only when it has a valid confirmation state. If the form callback and thank-you page both emit the event, choose one

The server accepts the demo request before the application reports a single generate_lead event.

source.

Test the cases that usually inflate lead reports

  • A valid request gets confirmation. Expect one lead event.
  • A required field is missing. Expect zero.
  • The user clicks twice while the request is pending. Expect one event after confirmation.

Growth mechanics, zero fluff.

Join SaaS founders and operators getting weekly notes and tear-downs on organic acquisition and churn reduction.

  • A failed request succeeds on retry. Expect one after the success.
  • A thank-you page is opened directly or reloaded. Expect no additional lead event.

Use GTM Preview and GA4 DebugView to check the event name, parameters, and destination. Test the site's expected behavior with and without analytics consent. Mark generate_lead as a key event if this is the lead action you want to report. If the event also covers other forms, segment the report by form type and avoid counting the same request twice.

Compare the counts with your CRM

The CRM or booking system is the record of accepted requests. GA4 helps compare measured traffic and acquisition paths. Check both by day and form type. Consent and attribution can affect the totals. A spike in GA4 with steady CRM requests is a cue to rerun the duplicate tests.

For the form fields themselves, use the SaaS demo request form template.

Rakibul Sumon

Written by · SaaS Growth Marketer

Rakibul Sumon

SaaS growth marketer who learns deeply, experiments openly, and shares results publicly. Focused on content-led SEO, brand positioning, and building growth systems that compound over time.

Learning In Public

SaaS growth insights,_

No hype, no recycled advice - just honest experiments, frameworks, and lessons from the trenches, delivered when there's something worth sharing.

No spam, ever. Unsubscribe anytime.