Track Google Ads in Eloqua: capture campaign data on every lead
You can connect paid search activity to Eloqua leads by tagging ads consistently, storing the visitor's origin in a browser cookie, and writing that origin into hidden form fields at submission. Once Eloqua receives those fields with the contact details, reporting can compare campaigns, keywords and channels on leads, customers and revenue rather than clicks alone.
Why campaign-level capture matters
Without campaign-level lead data, budget decisions are guesswork: you cannot tell which campaigns deserve more spend or which should be paused. The workflow below closes that gap by carrying the ad context from the click, through the website visit, into Eloqua on the form submission.
Four-step setup checklist
Work through these four steps in order. Skipping the tagging or hidden-field steps means there is nothing for the attribution snippet to pass to Eloqua.
Step 1: Tag ads with UTM parameters
Add UTM parameters to every Google Ads campaign using a tracking template so new ads inherit the same structure. A consistent pattern is: UTM Medium set to Paid search, UTM Source set to Google, UTM Campaign set to the campaign name, UTM Term set to the ad group name, and UTM Content set to the specific ad. Consistency matters more than the exact labels, because those values become your reporting dimensions in Eloqua.
Step 3: Let the snippet write origin data into hidden fields
Place the attribution snippet on the website. On arrival it identifies the visitor's origin, groups it into channels comparable to those in Google Analytics such as Paid Search, Paid Social and Organic Search, and stores that attribution data in a cookie in the browser. When the visitor later completes a form, the snippet writes the stored origin into the hidden fields.
Worked example: what the hidden fields contain
For a concrete example, suppose a visitor arrives from a paid search ad and submits a form. The hidden fields could be populated as Channel = Paid search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand campaign, and Channel Drilldown 3 = Free account ad, depending on the UTM values used. The snippet also records the first landing page, for example a features page URL, and its page group, for example features. Eloqua then stores all of those values alongside the lead's name, email and other submitted details, so each contact carries its campaign context.
Step 4: Report inside Eloqua
With origin data on every contact, Eloqua reports can answer: how many leads came from Google Ads, how many customers each campaign produced, lead-to-customer conversion rate, average deal size for Google Ads customers, and win rate for opportunities originating from paid search. Because the snippet captures all channels, not only paid search, the same fields also support Organic Search, Organic Social and Paid Social comparisons.
Three reports to build first
Three reports are especially useful. First, Leads by Channel shows monthly lead volume per channel, giving a high-level view of what drives pipeline and where growth opportunities sit; for example, if Organic Search outproduces Paid Search, additional SEO investment may be warranted. Second, Customers by Campaign shows new customers per Google Ads campaign per month, separating campaigns that create real customers from those that only create non-converting leads. Third, Revenue by Keyword shows revenue per keyword per month, revealing which keywords return positively and where higher bids could increase impression share.
Wrap-up
In short, consistent UTM tagging plus hidden form fields plus a website attribution snippet gives Eloqua the campaign context it otherwise lacks. Set up the fields, verify a test submission populates them correctly, and then build the channel, campaign and keyword reports to guide spend.