Skip to content

Track Gravity Forms Submissions as Google Analytics Conversions

If your website collects leads through Gravity Forms, knowing how many submissions arrive is only half the picture. You also need to know which channels and campaigns produced them. This guide walks through the no-code route: install the Gravity Forms Google Analytics add-on, create a Feed on each form you care about, confirm the event reaches your GA4 property, and mark it as a key event so it can be used in acquisition and funnel reporting. It then covers the optional step of capturing lead-source data with each submission and three reports worth building once the event is flowing.

What you are building, and the choices involved

There is more than one way to get a Gravity Forms submission into Google Analytics. You can push events into a Tag Manager data layer, or send requests through the Measurement Protocol. Both give you fine control, and both assume you are comfortable writing code and handling things like API calls and authorisation headers. The add-on route trades that control for simplicity: it connects your WordPress site to a GA4 property and fires an event named form_submission whenever a configured form is submitted.

Before you start, decide three things:

  • Which GA4 account and property should receive the event. Every Feed sends to the property selected at the add-on settings level.
  • Which forms count as conversions. A high-value Contact Us or Request A Quote form usually deserves its own Feed; a newsletter signup or eBook download may not.
  • Whether any submissions should be excluded. Conditional rules let you suppress the event unless a particular field value is present, such as a chosen product or a budget threshold.

A useful rule of thumb: if a submission would be handed to sales, track it. If it is purely a content download, consider leaving it out so your conversion counts stay meaningful.

Choosing an approach:

  • Add-on: fastest to set up, no code, one event name across all tracked forms. Best when you want a single conversion signal and do not need custom event parameters.
  • Tag Manager data layer: more setup work and JavaScript, but lets you attach custom parameters and trigger different tags per form. Best when you need granular event design.
  • Measurement Protocol: server-side or custom requests, requires API knowledge and authorisation handling. Best for offline or server-confirmed conversions rather than simple on-page form submissions.

Step 1: Install the Google Analytics add-on and connect the property

In your WordPress dashboard, open the Gravity Forms Add-ons section and install the official Google Analytics add-on. After installation, open the Google Analytics settings inside Gravity Forms and choose the Google Analytics option. The screen that follows walks you through authorising Gravity Forms to access your Google Analytics account. When authorisation completes, pick the account and property that should receive form submission events. Any form with a Feed configured in the next step will send its event to that property, so confirm the selection before moving on.

Step 2: Create a Feed on every form you want to track

Open the specific form, go to its Settings menu, and select Google Analytics. On the Feeds page, create a new feed. The Feed Settings tab asks for a name, which is internal only and simply helps you recognise the feed later.

You can also send parameters to Google Analytics. In most cases leaving this blank is fine. If your site has several form types and you want to separate them in reporting, sending the form title is a practical option. That way a main enquiry form and a secondary download form do not blur into one conversion count.

Conditional rules are the third control. They decide whether a submission is sent at all. Most businesses can skip this, but it is useful when only some submissions should count, for example when a visitor selects a particular product or service, or enters a budget above a set amount.

Repeat the Feed setup on each form that should fire the event. A form without a Feed will not send anything.

Worked example: suppose you have a Contact Us form and a newsletter signup form. Give the Contact Us form a Feed with the form title as a parameter, and leave the newsletter form without a Feed. Now only genuine sales enquiries count as form_submission events, and the parameter lets you tell enquiry types apart if you later add a second sales form. If you want to go further, add a conditional rule so the Contact Us Feed only fires when the budget field is filled in, filtering out casual browsers.

Step 3: Confirm the event actually arrives

Open a fresh incognito window, load the page containing the form, and submit it. Then open Google Analytics, go to the Real Time dashboard, and look at the Recent Events section. You are looking for an event named form_submission. If it appears, the add-on is firing on submission and your chosen property is receiving it.

If it does not appear, work through the likely causes in order:

  • The form has no Feed, or the Feed was created on a different form.
  • The add-on is connected to a different account or property than the one you are watching.
  • A conditional rule is excluding your test submission.
  • The test was run in a browser or network that blocks analytics requests.

This check separates two very different failures: an event that never reaches GA4, and an event that arrives but is not yet treated as a conversion. The next step addresses the second.

Step 4: Mark form_submission as a key event

Marking the event as a key event is optional but recommended. In GA4 terms it turns form_submission into a conversion, which unlocks its use in acquisition reports, funnel and path exploration, and other conversion-based reporting.

To do it, open the Admin section, choose Events under the Data Display heading, and switch to the Recent Events tab. Find form_submission in the list and click the star icon beside it.

Then open the three-dot menu next to the event and choose Change Counting Method. Select Once Per Session. For lead-generation sites this usually fits better than counting every occurrence, because a single lead rarely submits the same form more than once in a session, and the setting reduces double counting. An eCommerce site with repeat purchases would make a different choice.

Adding lead-source data to each submission

The setup above tells you how many submissions happened. It does not tell you who each lead was or what happened after they enquired. If you want per-lead attribution, you need the source data to travel with the form entry itself.

That is the gap a lead-source tool fills. A script placed on the site reads the same kind of technical signals Google Analytics uses, classifies the visit into standard marketing channels such as Organic Search, Paid Search, and Paid Social, and stores the result in the visitor's browser. When the visitor submits a form, the values are written into hidden fields you have added to that form. Gravity Forms then captures them with the entry, so they can be sent to a CRM, included in notification emails, or exported to a spreadsheet. Whichever lead-source tool you choose, the same principle applies: it must write values into hidden form fields so Gravity Forms can capture them.

A practical example: a visitor arrives from a paid social ad, browses two pages, and submits your demo request form. With hidden attribution fields in place, the entry records the channel and campaign alongside the contact details. Without them, the entry holds only what the visitor typed, and the campaign link is lost once the session ends.

This is optional. The GA4 event setup works independently, and you can add per-lead attribution later without redoing it.

Three reports worth building once the event is live

With form_submission marked as a key event, three views tend to be the most immediately useful.

  1. Conversions by channel. Group key events by default channel grouping to see whether Organic Search, Paid Search, Paid Social, or another channel is producing the most form submissions. This is the fastest way to spot where growth is coming from and where it is not.
  1. Conversions by Meta Ads network. If you advertise through Meta, your ads may run across Facebook, Instagram, Messenger, and WhatsApp. Those are distinct environments with different behaviour, so breaking conversions down by network shows which placement deserves more budget and which can be trimmed.
  1. Conversions by Google Ads campaign. Most Google advertisers run several campaigns at once, split by product, keyword type, or geography. A campaign-level conversion view shows which ones are producing enquiries, giving you a basis for bid changes, keyword additions, and ad copy tests.

Each of these depends on the same underlying event, so the setup work is shared.

Where to go next

Once the event is confirmed and marked as a key event, the main remaining task is discipline: keep the Feed list current as forms are added or retired, and revisit conditional rules when your lead definitions change. If you also want campaign data attached to individual leads, add hidden attribution fields and route the entries to your CRM or spreadsheet. Either way, the value comes from acting on the numbers rather than simply collecting them.

Frequently asked questions

What event name does the Gravity Forms Google Analytics add-on send?

It sends an event called form_submission. You can confirm this in the Real Time dashboard's Recent Events section after submitting a test form.

The event is not showing in Real Time. What should I check first?

Check that the form has its own Feed, that the add-on is connected to the same account and property you are viewing, and that no conditional rule is excluding your test submission. Also try an incognito window so browser extensions and cached sessions do not interfere.

Should form_submission count every occurrence or once per session?

For lead-generation forms, Once Per Session is usually the better fit because a lead rarely submits the same form twice in one session, and it reduces double counting. Businesses with repeat transactional behaviour may prefer a different method.

Do I need a separate Feed for each form?

Yes. Each form that should send the event needs its own Feed. A form without a Feed will not send anything to Google Analytics.

What parameters should I send with the event?

In most cases you can leave the parameter field blank. If you have several form types and want to distinguish them in reporting, sending the form title is a practical choice.