Capture Google Ads data in Ninja Forms
Form submissions alone do not show which paid search campaign produced a lead. By tagging ad URLs, adding hidden fields to Ninja Forms, and carrying the first-touch values through to submission, you can connect each enquiry to its campaign, ad group, ad and landing page — then follow it through to customer and revenue outcomes.
Why downstream outcomes change the decision
Counting visitors and completed forms can mislead budget decisions. In the pool equipment example, both campaigns cost $2,000. Pool Pumps produced more visitors and leads, yet Pool Cleaners produced more customers and far more revenue. Once customer and revenue results are attached to each campaign, the stronger performer becomes clear: higher lead-to-customer conversion, lower cost per customer, higher value per customer and stronger return on ad spend. The practical lesson is to judge campaigns by downstream outcomes, not only by traffic or lead volume.
Four steps to capture the data
First, append UTM parameters to the destination URL for each Google Ad. A consistent convention helps reporting: medium identifies paid search, source identifies Google, campaign uses the campaign name, term identifies the ad group, and content identifies the specific ad. Free UTM builders can help construct the URLs. Second, add hidden fields to the Ninja Form for Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. In Ninja Forms, drag a Hidden field type into the form. Third, the attribution tool detects the visitor's origin and fills those fields from the UTM values. Fourth, on submission the hidden values are stored alongside the person's name, email, company, phone and other form answers, ready for notification emails, CRM records or campaign reporting.
Example field values and pre-publish checklist
A worked example shows how the fields should look. A visitor arriving from a Google brand campaign in paid search might be recorded as Channel = Paid search, Drilldown 1 = Google, Drilldown 2 = Brand campaign and Drilldown 3 = Free account ad, together with the first landing page and its group. Before publishing, check that every hidden field is present, that campaign naming is consistent, and that a test submission carries the expected values into the email or CRM destination you intend to use.
Make the attribution data complete and clean
Three design choices make the setup more reliable. Capturing all traffic, not only paid search, lets you compare Google Ads with organic search, paid social and organic social before shifting budget. Storing UTM values in a cookie preserves attribution when the landing page differs from the form page, such as when a visitor moves from an ad landing page to a quote form. Normalising inconsistent values — for example Google.com, google and adwords — prevents one channel from fragmenting into several report labels. Recording the landing page and its group also shows whether particular content sections or individual posts generate leads, customers and revenue.
| Measure | Pool Pumps Campaign | Pool Cleaners Campaign |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Leads | 20 | 10 |
| Customers | 2 | 5 |
| Revenue | $8,000 | $25,000 |
Illustrative example from the source; figures are not current performance claims.
Frequently asked questions
What setup is needed to capture Google Ads data in Ninja Forms?
Add consistent UTM parameters to each ad destination, place hidden fields for channel, drilldowns, landing page and landing page group in the form, and let the attribution tool populate those fields from the visitor's first touch before submission.
Where can the captured attribution data be used after submission?
Yes. The attribution data can be included in lead notification emails, sent to a CRM such as Salesforce, Pipedrive or Dynamics, or used in reports showing which campaigns produce leads, customers and revenue.
What happens if the form is on a different page from the ad landing page?
Storing the UTM values in a browser cookie preserves them across pages, so a visitor who lands on one page and completes a form on another still gets credited to the original campaign.
Why normalise UTM values instead of storing them raw?
Normalising values such as Google.com, google and adwords into one channel prevents the same traffic being split across several inconsistent source labels in reports.
| Pool Pumps Campaign | Pool Cleaners Campaign | |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Goal Completions | 20 | 10 |
| Pool Pumps Campaign | Pool Cleaners Campaign | |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Leads | 20 | 10 |
| Customers | 2 | 5 |
| Revenue | $8,000 | $25,000 |