Skip to main content

Gravity Forms tells you who completed a form and what they submitted. But the marketing context behind that submission—such as the original campaign, referring site, landing page, or supported AI referral—usually requires additional tracking and configuration.

That gap matters when form entries reach your inbox or CRM without a reliable answer to a basic question:

Which marketing source produced this lead?

This guide explains how to connect Gravity Forms submissions with AttribuLead’s WordPress attribution records. You will learn what the integration captures, how to configure the required hidden field, and how to test the complete path from a tagged visit to an attributed lead.

Important distinction: AttribuLead creates and stores its own lead-attribution record for a supported Gravity Forms submission. Unless a separate mapping or integration explicitly does so, it should not be described as adding every attribution value as a visible native field on the Gravity Forms entry.

Why Gravity Forms entries often lack useful source data

Gravity Forms stores the fields included in your form. You can add hidden fields and populate them with custom values, but Gravity Forms is not, by itself, a persistent first-touch and last-touch attribution system.

That creates several common reporting gaps:

  • UTM parameters may be present on the landing page but absent when the visitor submits later.
  • A visitor may return directly before converting, separating the submission from the earlier acquisition source.
  • The form entry may reach a CRM without the source details needed for segmentation, routing, or reporting.
  • Referrals from supported AI assistants or other websites may not be preserved at the lead level.

Session analytics can still report visits and conversions. The harder problem is attaching durable source evidence to the individual lead captured in WordPress.

The attribution views AttribuLead preserves

AttribuLead separates three useful views of the journey:

  • First touch: the earliest recorded source for the visitor. This helps identify what first created awareness.
  • Last touch: the latest recorded source before conversion. This helps identify what preceded the submission.
  • Effective source: AttribuLead’s single-source decision about the most representative source for the lead.

Effective source is not multi-touch attribution. It does not divide conversion credit among several channels. Instead, it selects one source using the available evidence and AttribuLead’s attribution rules.

Source Lock can prevent a source-less direct return from replacing an earlier identifiable acquisition source. That makes the effective source particularly useful for lead routing, CRM fields, exports, and single-source reporting.

How the Gravity Forms integration works

When Gravity Forms is active, AttribuLead detects the integration and can process supported submissions through Gravity Forms’ after-submission event.

The connection depends on a visitor identifier:

  1. AttribuLead classifies the visitor using available signals such as UTMs, click IDs, referrers, or supported AI referrals.
  2. Its front-end tracking associates that visit with a visitor UUID.
  3. A Gravity Forms Hidden field carries the configured visitor identifier with the submission.
  4. After Gravity Forms creates the entry, AttribuLead reads the submitted identifier and creates the corresponding conversion and lead-attribution record.

If the entry does not contain a valid visitor UUID, AttribuLead cannot reliably connect that submission to the earlier visit and does not create the attributed conversion.

Gravity Forms officially supports Hidden fields and dynamic population. In the field’s Advanced settings, the value used for dynamic population is called the Parameter Name. Use the exact identifier shown in AttribuLead’s settings rather than inventing one.

For optional lead details, AttribuLead can recognize supported Gravity Forms field types and labels. Based on the current implementation, these include native Email and Name fields and fields identified as company or organization. Lead-data storage settings determine whether that personally identifiable information is retained.

Set up Gravity Forms attribution

1. Install both plugins

Install and activate Gravity Forms and AttribuLead on the same WordPress site.

2. Confirm that Gravity Forms is detected

Open AttribuLead → Settings → Integrations and confirm that Gravity Forms appears as active.

This status confirms plugin detection. It does not, by itself, prove that every form contains the required visitor field.

3. Choose your lead-data storage setting

Open AttribuLead → Settings → Lead Intelligence and choose how much lead information AttribuLead may retain.

Depending on the available settings, you can keep attribution without storing lead PII or allow supported details such as email, name, and company to be stored. This setting affects identifying information, not whether the source itself can be classified.

4. Add the visitor identifier to each form

For every Gravity Form you want AttribuLead to process:

  1. Open the form in the Gravity Forms editor.
  2. Add a Hidden field.
  3. Open the field’s Advanced settings.
  4. Enable Allow field to be populated dynamically if required by the current AttribuLead integration.
  5. Enter the exact Parameter Name shown in AttribuLead’s settings.
  6. Save the form.

Do not copy an identifier from an old tutorial or create your own. The configured value must match what AttribuLead’s front-end script expects.

5. Check every conversion form

Repeat the hidden-field setup for each relevant form. A correctly configured contact form does not automatically configure a separate demo, quote, or download form.

Test the integration in five minutes

Use a controlled test so the expected result is unambiguous.

  1. Create a tagged test URL, for example:https://example.com/demo/?utm_source=linkedin&utm_medium=paid-social&utm_campaign=gf-attribution-test
  2. Open the URL in a fresh private window.
  3. Navigate normally to the page containing the configured Gravity Form.
  4. Submit the form with recognizable test details.
  5. Confirm that Gravity Forms created the entry.
  6. In AttribuLead → Leads, find the test lead.
  7. Check the recorded channel, effective source, campaign, landing page, and confidence or attribution explanation available in the current interface.
  8. Verify that the explanation points to the expected UTM evidence.

This test validates the whole chain: visit classification, visitor identification, hidden-field population, form submission, and lead creation.

After the tagged test passes, run a second test that begins with a tagged visit and converts after a direct return. This is the useful test for first-touch persistence and Source Lock.

Troubleshooting Gravity Forms attribution

The Gravity Forms entry exists, but no AttribuLead lead appears

Start with the visitor identifier. The Hidden field may be absent, incorrectly configured, or empty in the submitted entry.

  • Confirm that the form contains the Hidden field.
  • Confirm that its Parameter Name exactly matches the value in AttribuLead.
  • Inspect the test entry to see whether the hidden value was saved.
  • Retest in a fresh private window.
  • Check for JavaScript optimization, consent, or caching behavior that could prevent the front-end value from being populated.

The lead appears, but the source is Direct or has weak evidence

The test visit may not have supplied a recognizable source signal.

  • Use a fully tagged test URL.
  • Check that redirects preserve the UTM parameters.
  • Avoid opening the form first in another tab or session.
  • Review AttribuLead’s attribution explanation rather than judging the result from the channel label alone.

The hidden field does not populate

Confirm both the Gravity Forms field configuration and the page environment. Script deferral, aggressive optimization, cached markup, AJAX-rendered forms, or a consent rule can affect when tracking values become available.

Gravity Forms notes that its PHP-based dynamic-population methods can be affected by full-page caching. AttribuLead’s front-end population may use a different mechanism, so diagnose the actual submitted value rather than assuming caching is always the cause.

Tracking starts only after consent

If you use AttribuLead’s Consent-Aware mode, verify that your consent platform communicates the expected consent signal to AttribuLead. Do not assume that consent recorded only inside the consent manager is automatically visible to every other plugin.

Confirm the current consent-integration instructions in AttribuLead before publishing a specific cookie name as a universal requirement.

Multi-page or AJAX forms behave differently

Test the exact production form configuration. A simple form test does not validate every multi-page, dynamically loaded, or AJAX-submitted implementation. Confirm that the visitor identifier remains populated in the final saved entry.

What you can do with attributed Gravity Forms leads

Once the integration is working, the attribution record can support:

  • lead exports by source, medium, campaign, or landing page;
  • comparison of first touch, last touch, and effective source;
  • investigation of leads with unknown or low-confidence attribution;
  • custom CRM lists, workflows, or routing when the relevant fields are synced;
  • campaign-level lead reporting inside WordPress; and
  • analysis of supported AI-assistant referrals at the lead level.

Keep the system boundary clear: AttribuLead’s WordPress record does not automatically rewrite the attribution model or native reports in GA4, Gravity Forms, or a connected CRM.

Gravity Forms attribution in Free and Pro

Based on the current product plan, AttribuLead Free includes the core Gravity Forms attribution workflow, source classification, Source Lock, supported AI-referral recognition, and core CSV export.

Paid plans add capabilities such as HubSpot contact sync, more advanced traffic and attribution-health reporting, and native WooCommerce or Easy Digital Downloads revenue attribution.

Because packaging can change, verify the pricing-page feature table against the release build before publication.

Add source context to your next Gravity Forms lead

Gravity Forms already handles the submission. AttribuLead connects that submission with the marketing evidence captured on the visitor journey.

Download AttribuLead Free and run the tagged-link test on one Gravity Form.

Frequently asked questions

AttribuLead can automatically detect that Gravity Forms is active. Each form still needs the correctly configured Hidden field so the submitted entry carries the visitor identifier required to connect it with the visit.

The core integration should be described as creating an AttribuLead lead-attribution record from a supported Gravity Forms submission. Do not claim that all source values appear as native Gravity Forms entry fields unless the current release explicitly writes them there.

The intended setup uses a standard Gravity Forms Hidden field and the identifier configured in AttribuLead. Follow the current settings-screen instructions; custom code should not be required for the standard integration.

Gravity Forms can receive values through hidden fields and dynamic population, including values passed in a query string or supplied through custom hooks. A complete attribution system must additionally decide how those values persist across pages and return visits, connect them with the visitor, and select the source used for lead reporting.

AttribuLead cannot reliably connect the entry to the tracked visitor. Under the behavior described for the current integration, it does not create the attributed conversion.

The integration can recognize supported fields such as native Gravity Forms Email and Name fields and company or organization fields. What is retained depends on the current Lead Intelligence data-storage setting and the form’s actual fields.

The current product plan places the core Gravity Forms attribution workflow in Free. Confirm the final release and pricing table before publishing edition-specific promises.

Privacy Preference Center