Lead source in Eloqua.
Lead Source records the ad, search or site that sent every Eloqua lead, in its own dashboard beside Eloqua. No implementation project.
Free to start · no card
Eloqua credits the right source only when it sees the whole visit
Eloqua’s Closed-Loop Reporting (CLR) ties a sale to its marketing when Eloqua sees the whole visit, from the first ad click to the form. That keeps getting harder: browsers such as Safari block more tracking, people research on one device and buy on another, and some ad networks strip the campaign tags from their links.
What Eloqua gives you
- Closed-Loop Reporting (CLR)
- Event hooks on form submissions
- Custom Data Objects (extra data tables) for extended attribution
- Interfaces for external data
- Campaign-level attribution reporting
Where it loses the trail
- The referring site, when the browser hides it
- Visits that move from one device to another
- Visits Eloqua did not track
- Forms on third-party pages Eloqua doesn’t fully see
Building source tracking inside Eloqua is a project of its own
Eloqua has hooks for all of this: custom data objects, add-on apps, its import interfaces. Standing them up to capture source reliably takes custom build work. Lead Source takes one script and one link. Use it while a longer build goes ahead, or instead of one. Like our other lead source integrations, it works beside Eloqua and changes nothing inside it.
The manual way
- 01Define a custom data object for every source value, then attach them to Contact records.
- 02Wire up a submission handler on every form, then test it on embedded forms, hosted landing pages and tracked sessions.
- 03Build an add-on app that brings source data in from outside Eloqua, or commission an Eloqua-certified partner to build one.
- 04Check it against your customer data platform, ad-platform data, and Salesforce records. Reconcile attribution discrepancies. Maintain it as the org evolves.
With Lead Source
- One script on your site captures the real source, campaign, ad click ID (the code an ad adds to each click) and full page journey when the visitor lands.
- Eloqua’s own hosted forms live on Eloqua’s domain, so a script cannot reach them. Point their completion action at Lead Source instead, and each submission arrives with its source attached when it can be tied to a visit.
- The lead lands in your Lead Source dashboard named, with the real source and the pages read before the form.
- Run it as an independent record, or send the source on to wherever your team works. Eloqua itself is left alone.
Eloqua reports the source when it can see it. Lead Source records the visits it cannot.
Two install paths, one for each kind of Eloqua form.
Sign up and your dashboard has both install paths: one line for forms embedded on your own site, and a link for Eloqua-hosted forms and landing pages. Both keep their own record beside Eloqua.
<!-- Paste your real snippet from app.leadsource.co --> <script async src="https://app.leadsource.co/ft.js" data-site="YOUR_SITE_KEY"></script>
One line in your site header. It captures every form on the page it can see, without modifying Eloqua’s scripts or your forms.
For Eloqua-hosted forms, add your Lead Source link to the form’s completion actions, and every submission arrives with its source attached when it can be tied to a visit.
Live beside Eloqua in three steps.
Sign up. Both install paths are waiting
Create your free Lead Source account. Your dashboard has both: a script tag for sites you control, and a link for forms hosted elsewhere.
Install the path that matches your forms
For Eloqua-hosted forms, add your Lead Source link to the form’s completion actions.
Submit a test through any Eloqua form
The lead appears in your Lead Source dashboard with the source, campaign and full page journey attached.
Works across Eloqua deployments
Each Eloqua submission, with its real source named
Embedded on a page you control, an Eloqua form carries the full list below. Hosted on Eloqua’s domain, it carries the source once Lead Source matches the submission to a visit.
- Name, email, phone when the form asks for it
- Every other answer given
- Which form produced it, embedded or hosted
- Source and channel
- Campaign and the tags on the ad link (UTMs)
- Ad click IDs
- Landing page and referrer
- First visit and last visit
- Every page they viewed before submitting
What stays on the Eloqua side
Lead Source runs beside Eloqua and changes nothing inside it, so the source does not feed Closed-Loop Reporting by itself. To get it into your stack, send it on through the Zapier app or a signed webhook you set up.
Campaign emails are the usual gap. When a contact clicks through to a hosted Eloqua form without ever touching your website, there is nothing to match, and that lead arrives with its source unknown. Phone enquiries are out of scope too: Lead Source records forms, and nobody fills one in on a call.
Eloqua questions, answered.
Does this require changes to our Eloqua instance?
No. Capture happens on your website, and for Eloqua-hosted forms through a completion action. Nothing inside Eloqua is modified.
Can the source reach Eloqua as a Custom Data Object?
Not by itself. Lead Source holds the record, and you can send the source on to wherever your team works.
Does this feed Closed-Loop Reporting?
Not on its own. Lead Source is a separate record of what produced each lead. Teams typically use it alongside CLR rather than inside it.
We also use Salesforce. Does that change anything?
No. The install is the same either way, and the same link covers forms hosted outside your site. See our Salesforce page for the detail.
Where does the data actually live?
In Lead Source. That is the point of running it in parallel: the record is outside Eloqua, so it cannot be altered by anything happening inside it.
Track the source of every Eloqua lead. Free to start.
Sign up free, add the script or the form link, and each Eloqua lead arrives in your dashboard with the marketing that sent it. Nothing inside Eloqua changes.
Start freeFree to start · no card









