Capture Google Ads Data in Unbounce and Follow It to Revenue
Visitors and form submissions show activity, not business value. When each Unbounce lead carries the campaign, ad group, ad, landing page, and channel that produced it, those records can be carried into a CRM and compared with customers and revenue. The setup below separates tagging, form fields, attribution, and reporting so each part can be checked independently.
Why leads alone can point to the wrong campaign
A pool-equipment advertiser spends $2,000 on each of two campaigns. Pool Pumps brings 200 visitors and 20 leads; Pool Cleaners brings 100 visitors and 10 leads. Judged only on traffic and leads, Pool Pumps looks stronger. The downstream result reverses that impression: Pool Cleaners produces five customers and $25,000, while Pool Pumps produces two customers and $8,000. Pool Cleaners also converts leads to customers at 50% rather than 10%, costs $400 rather than $1,000 per customer, and returns about three times as much revenue per advertising dollar. The lesson is practical: budget decisions need the full chain from click to customer, not the first two steps alone.
Step 1: Tag every Google Ads destination consistently
Start with a consistent tagging convention. A workable Google Ads pattern is: medium for paid search, source for Google, campaign for the campaign name, term for the ad group, and content for the specific ad. For example, a destination URL can carry utm_medium=paidsearch, utm_source=google, and utm_campaign=brand-campaign. Consistency matters more than clever naming. Decide the values once, document them, and apply them across every ad that points to an Unbounce page. Free URL builders can help assemble the links, but they do not enforce consistency across a team.
Step 2: Add the six attribution hidden fields
Add six hidden fields to each Unbounce form that should carry attribution: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. In Unbounce, drag a Hidden field type into the form for each one. Use the exact field names in the form and in the receiving system; a renamed field can silently break the mapping. Before publishing, submit a test form and inspect the resulting notification or CRM record to confirm all six values arrive.
Step 3: Let attribution populate the fields at submission
When a visitor submits a form, the attribution tool reads the stored campaign information and writes it into those hidden fields. In a paid-search brand example, the result might read: Channel = Paid search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand campaign, and Channel Drilldown 3 = Free account ad. The tool also records the first landing page, such as a features page, and its group, such as features. That combination answers two different questions: which campaign produced the lead, and which page first received the visitor.
Step 4: Use the captured data in notifications, CRM, and reports
Once captured, the attribution fields travel with the contact details the visitor entered, including name, company, email, and phone. Teams can include them in lead notifications, send them to a CRM, and build campaign reports that extend beyond leads to customers and revenue. A useful reporting checklist is: confirm campaign and ad values on a test lead, confirm the landing page and group, confirm the CRM field mapping, and confirm that customer and revenue records can be joined back to the original lead.
Three distinctions that prevent misleading reports
A common failure is expecting UTM parameters to survive only when they remain in the URL. If a visitor lands from an ad, clicks through to a quote page, and submits there, the parameters may no longer be present. Storing attribution in a browser cookie avoids that gap. Another failure is reporting on raw UTM values: Google.com, google, and adwords can appear as three separate sources for the same platform. Normalized channel values prevent that fragmentation. Finally, capturing only Google Ads misses the rest of the picture. The same approach can record organic search, organic social, and paid social, making it possible to compare all lead sources before shifting budget.
Use landing page and group to judge content, not just campaigns
Landing-page fields add a content view that channel data alone cannot provide. Recording the exact first page shows whether a particular article or guide generated leads; recording its group shows how the whole section performed. That makes it possible to review a blog as a whole and also identify individual posts worth expanding, updating, or promoting. The same pattern applies to product, feature, and resource pages.
Final check before you rely on the data
Before scaling the setup, run one end-to-end test from a tagged ad URL through an Unbounce submission and into the CRM. Verify the channel, three drilldowns, landing page, and landing page group. Then repeat the test after navigating to a second page before submitting. If both records carry the original campaign data, the tagging, hidden fields, cookie persistence, and downstream mapping are working together. Treat that result as a baseline: re-run the same check whenever a form, field name, or CRM mapping changes, and keep a dated record of each pass so later reporting discrepancies can be traced to a specific change rather than guessed at.
| Check | What to verify | Pass signal |
|---|---|---|
| Tagging | Medium, source, campaign, term, and content are present and consistently named | Test URL and CRM record show the intended values |
| Hidden fields | All six fields exist on the Unbounce form with matching names | Submission record contains every field |
| Cross-page journey | Visitor lands from an ad, moves to another page, then submits | Original campaign data is still present |
| Normalization | Variant spellings do not create duplicate sources | One channel value appears in reporting |
| Downstream use | Notification and CRM receive the fields and can join to customer and revenue | Campaign report reconciles to closed business |
Use as a pre-launch and post-launch test checklist; do not treat a single successful submission as proof for every form.
Frequently asked questions
What happens if the form is on a different page from the ad landing page?
No. The attribution data is stored in a browser cookie, so it can still be passed through when the visitor later submits a form on a different page. That matters when someone lands from an ad, browses further, and only then completes a quote or contact form.
Why not simply store the raw UTM values?
Raw values can create duplicate sources when capitalization or naming varies, such as Google.com, google, or adwords. A normalized channel model groups those variants so reporting does not require manual stitching.
Can landing-page information be captured as well?
Yes. The same hidden-field pattern can also record the first landing page and its group, which helps distinguish performance of a whole content section from performance of an individual page.
| 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 |