Skip to content

Track SEO Leads in Eloqua With Form Attribution Data

Organic-search traffic only tells part of the story. To know whether SEO is producing business, each Eloqua form submission also needs to record how the visitor arrived and which page brought them in. This guide explains the four-step setup, the six fields involved, and three reports for turning that data into content and budget decisions.

The measurement gap

A software marketing team had invested heavily in SEO and seen website visits climb sharply, yet it could not tell whether those visits were becoming leads or customers. Analytics showed the volume of organic-search sessions, but not the downstream form submissions. The missing connection is attribution data attached to each lead at the moment a form is submitted.

Four steps to capture SEO leads in Eloqua

The workflow has four stages. First, install the attribution tracking code on the website, either through site settings or a tag manager such as Google Tag Manager. Second, add hidden fields to Eloqua forms. Third, let the tracking code classify the visitor and populate those fields when a form is submitted. Fourth, Eloqua stores the attribution values with the contact details, so every lead carries its acquisition context.

Hidden-field checklist

Open the form in Eloqua and add six hidden fields, configuring each with its required label and static value. The fields are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. A quick pre-launch check helps: confirm the tracking code loads on every page with a lead form, confirm all six fields are present on each form, and submit a test form to verify the fields arrive populated on the contact record.

What the captured data looks like

On arrival, the visitor is classified into a channel such as Organic Search, Paid Search, or Paid Social, and that classification is stored in the browser. When the visitor later submits a form, the hidden fields are filled automatically. For an organic-search visitor, the record can show the channel, the search engine, the search domain, and the keyword when available, alongside the exact landing page and its page group. A residential-building example illustrates the pattern: Channel is Organic Search, Drilldown 1 is Google, Drilldown 2 is the Google domain used, Drilldown 3 is the search keyword when available, Landing Page is the full blog URL visited, and Landing Page Group is /blog. That combination shows both how the lead arrived and which content earned the visit.

Putting the data to work

Once captured, the data can be viewed on the Eloqua contact record, added to lead-notification emails so the team sees the origin immediately, pushed to a CRM such as Salesforce, NetSuite, or Microsoft Dynamics for lead, customer, and revenue reporting, or exported to a spreadsheet or dashboard tool for visual analysis. The practical decision rule is simple: if a page group or channel consistently produces leads, prioritise more content and optimisation there; if it produces visits but no leads, investigate the page and the form journey before investing further.

Three reports to run first

Run leads by channel month by month to see whether organic search is growing and how it compares with paid channels. Then break organic-search leads down by landing-page group, such as Home, Blog, or Services, to find which site sections generate enquiries. Finally, break the same leads down by individual landing page to identify the specific articles or pages worth expanding. Used together, these three views separate overall SEO momentum from the content actually responsible for leads.

Wrap up

Traffic growth without lead visibility can lead to the wrong investment. Capturing channel and landing-page data on Eloqua forms closes that gap: every submission records whether it came from organic search, which engine and keyword were involved when available, and which page earned the visit. With those fields in place, SEO performance can be judged by leads and customers rather than visits alone. Before choosing a tool, check its current trial length, plan limits and setup requirements directly, and confirm that its form-field workflow matches how your Eloqua forms are built.

Eloqua hidden fields for SEO attribution
FieldWhat it recordsExample use
ChannelHow the visitor arrivedOrganic Search
Channel Drilldown 1Search engine or sourceGoogle
Channel Drilldown 2Search domainwww.google.com or a regional domain
Channel Drilldown 3Search keyword, when availableThe query used
Landing PageExact page visitedFull page URL
Landing Page GroupBroader site section/blog

Keyword is recorded only when available.

Frequently asked questions

Why is website traffic not enough to measure SEO leads?

Google Analytics can show organic-search visits, but it does not by itself show how many of those visitors became Eloqua leads or customers. Capturing channel and landing-page data on the form submission connects the visit to the lead record.

Which hidden fields are needed on Eloqua forms?

Add six hidden fields to each Eloqua lead-capture form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Configure each field with the label and static value specified for the attribution setup.

What do the channel and landing-page fields mean?

Channel records how the visitor arrived, such as Organic Search. The drilldowns add the search engine, domain, and keyword when available. Landing Page records the exact page, while Landing Page Group records its broader section, such as /blog.

Which three reports are most useful first?

Start with leads by channel over time, then organic-search leads by landing-page group, then organic-search leads by individual landing page. Together they move from overall channel performance to the content section and then to the specific page producing leads.