How to capture UTM parameters in Eloqua
Website analytics can tell you how many visitors arrived from a campaign, but it usually stops short of showing which of those visitors became leads, customers, or revenue. This guide explains how to carry UTM parameters and landing-page context into Eloqua so that the contact record itself becomes a reliable source for campaign reporting.
Why UTM capture belongs in Eloqua, not only in analytics
A UTM-tagged URL describes the click that brought someone to your site. Analytics tools count that visit. Eloqua, however, is where the person becomes a known contact, and that is the point where campaign data can be attached to a lead record and carried into a CRM or reporting layer.
Without that handoff, you can see traffic volume but not the downstream outcome. With it, each contact can carry the channel, campaign detail, and landing page that preceded the form submission.
The four-step setup
The workflow has four stages: tag the ads, add hidden fields to the forms, let the capture layer populate those fields, and confirm the values arrive in Eloqua.
- Tag consistently. Apply UTM parameters to social ads (Facebook, LinkedIn, Instagram, Twitter), search ads (Google, Bing), and bespoke lead-generation placements such as trade-publication banners or newsletter sponsorships. Consistency matters more than volume: the same parameter names and values across placements make later reporting possible.
- Add hidden fields. The lead-capture form — a contact form, a quote request, or a demo request — needs hidden fields for Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. These can be added in Eloqua's own form builder or in third-party form tools such as Gravity Forms, Webflow Forms, and Typeform.
- Populate automatically. The capture layer reads the incoming UTM parameters, classifies the visit into a channel, stores the result in a cookie, and writes the values into the hidden fields at submission time. {{OWNER_PRODUCT_DESCRIPTION}} — confirm the exact behavior, storage mechanism, and classification rules of the capture product before publishing this step.
- Confirm the handoff. On submission, the UTM and landing-page values travel with the contact's name, email, and other form data into Eloqua.
Worked example: what the hidden fields receive
Suppose a visitor clicks a Google ad for an Eloqua feature page, lands on the site, and then submits a demo request. Depending on the UTM values used, the hidden fields could receive:
- Channel: Paid Search
- Channel Drilldown 1: Google
- Channel Drilldown 2: Brand Campaign
- Channel Drilldown 3: Eloqua
- Landing Page: www.eloqua.com/features/email
- Landing Page Group: Features
The first four values describe the campaign and channel. The last two describe the page context. Together they let a report answer both "which campaign?" and "which page?" without relying on a separate analytics join.
Field-to-report map
Use this map to decide which hidden field feeds which reporting question.
This mapping is a planning aid, not a fixed schema. The actual field names in Eloqua must match the hidden-field names exactly, and the report labels are examples of the questions the fields can answer.
Failure distinction: lost UTM vs. missing UTM
Two different problems can produce the same symptom — a contact record with no campaign data — but they need different fixes.
Lost UTM. The visitor arrived with UTM parameters, but the values disappeared before the form was submitted. This commonly happens when a capture method only reads the URL on the landing page and does not persist the values while the visitor browses elsewhere. The fix is a capture layer that stores the values in a cookie and writes them at submission.
Missing UTM. The visitor never arrived with UTM parameters in the first place, because the ad or link was not tagged. The fix is at the campaign level: apply consistent UTM parameters to every paid placement and bespoke campaign.
A quick check: if the landing page URL in the contact record is present but the channel fields are empty, suspect lost UTM. If both the landing page and channel fields are empty or generic, suspect missing UTM.
Why a classification layer beats raw UTM strings
Raw UTM values are only as clean as the people who created them. Over time, different teams or agencies may tag the same source in different ways — for example, UTM_Source=Google, UTM_Source=google.com, and UTM_Source=adwords. Captured raw, those become three separate sources in Eloqua, and someone has to stitch them together manually.
A classification layer groups those variants into a single channel, such as Paid Search, while still preserving the underlying detail in the drilldown fields. The result is cleaner reporting without losing the ability to drill into the original values.
The same layer can also capture traffic that has no UTM parameters at all — organic search, organic social, direct, and referral — so reports are not limited to paid campaigns. {{OWNER_PRODUCT_DESCRIPTION}} — confirm which of these behaviors the capture product actually provides before publishing.
Four reports worth building once the data is flowing
Once UTM and landing-page values reach Eloqua and any connected CRM or reporting tool, these four reports answer distinct questions.
Leads by Channel. Shows monthly lead volume broken down by channel. Use it to compare where leads actually come from against where budget is going. If most leads arrive through organic search while most spend goes to paid search, that mismatch is worth reviewing.
Leads by Facebook Ads Network. Facebook/Meta ads can appear across Facebook, Instagram, Messenger, and other owned networks. This report shows which network is producing leads so ad spend can be adjusted accordingly.
Customers by Google Ads campaign. When multiple campaigns run in one Google Ads account — brand terms, competitor terms, and others — this report shows customer volume per campaign and supports bid and budget decisions.
Revenue by Keyword. Google Ads tracking templates can carry the search keyword into UTM parameters. Once captured, revenue can be attributed to individual keywords, which supports bid-strategy adjustments.
Implementation checklist
- [ ] Every paid placement carries UTM parameters with consistent names and values.
- [ ] Bespoke campaigns (banner ads, newsletter sponsorships) are tagged as well.
- [ ] The lead-capture form includes hidden fields for Channel, Channel Drilldown 1–3, Landing Page, and Landing Page Group.
- [ ] Hidden-field names in the form match the names in Eloqua exactly.
- [ ] The capture layer persists values in a cookie so navigation does not erase them.
- [ ] A test submission is checked on the Eloqua contact record.
- [ ] At least one downstream report is built and reviewed against known campaign activity.
| Hidden field | What it answers | Typical report |
|---|---|---|
| Channel | Which broad source category produced the lead? | Leads by Channel |
| Channel Drilldown 1 | Which platform or network within that channel? | Leads by Facebook Ads Network |
| Channel Drilldown 2 | Which campaign within that platform? | Customers by Google Ads campaign |
| Channel Drilldown 3 | Which specific ad group or keyword context? | Revenue by Keyword |
| Landing Page | Which page did the visitor first see? | Content-level lead reports |
| Landing Page Group | Which section of the site did that page belong to? | Section-level lead reports |
Frequently asked questions
Do I need a third-party capture product, or can I capture UTM parameters directly in Eloqua?
Eloqua can store whatever values a form submits, including hidden fields. The harder part is making sure the right values are present at submission time. A direct implementation can work if it persists UTM parameters across page navigation and classifies them consistently. A dedicated capture layer handles those two problems for you and can also record non-paid traffic. Attribution Analytics — confirm the product name and whether it is required or optional for this workflow.
Which form tools can feed these hidden fields into Eloqua?
Eloqua's own form builder can host the hidden fields. Third-party form tools such as Gravity Forms, Webflow Forms, and Typeform can also be used, provided the hidden fields are added and mapped to the corresponding Eloqua fields.
What happens if a visitor lands on one page and submits a form on another?
If the capture method only reads the URL at the landing page, the UTM values are lost when the visitor navigates away. A cookie-based capture layer stores the values in the browser and writes them at submission, so the campaign data survives the journey.
Can I report on leads that did not come from paid ads?
Yes, if the capture layer classifies all traffic, not only UTM-tagged visits. Organic search, organic social, direct, and referral visits can be assigned to channels and passed into Eloqua alongside paid-campaign data.
How do I handle inconsistent UTM values from different teams?
A classification layer can group variants such as UTM_Source=Google, UTM_Source=google.com, and UTM_Source=adwords into a single channel while preserving the original detail in drilldown fields. Without that layer, each variant appears as a separate source and must be merged manually in reporting. {{OWNER_PRODUCT_DESCRIPTION}} — confirm the classification behavior before publishing.