CRM lead source
How to add a custom field to a Freshsales web form
Eloqua integration
Lead source in Eloqua.
The real source of every Eloqua lead, recorded beside Eloqua rather than inside it. No implementation project, no six-month wait.
Live in five minutes, not a six-month implementation
No conflict with existing tracking scripts
Nothing changes inside your Eloqua instance
Works across Eloqua deployments
Embedded Eloqua forms
Eloqua-hosted forms
Eloqua landing pages
Your existing CLR
Embedded & hosted forms
B2B enterprise stacks
The gap
Eloqua’s attribution is comprehensive. It’s also conditional.
Closed-Loop Reporting works when Eloqua sees the full session. From first-touch ad click through to form submission. The conditions for that are increasingly hard to meet in 2026: ITP-strength browser privacy, cross-device research-to-purchase patterns, and ad networks that strip query parameters in pursuit of their own measurement.
What Eloqua delivers natively
A complete attribution framework
- Closed-Loop Reporting (CLR)
- Event hooks on form submissions
- Custom Data Objects for extended attribution
- Interfaces for external data
- Campaign-level attribution reporting
Where the framework has blind spots
Modern browser & channel realities
- Referrer-based attribution under iOS ITP
- Cross-device journey reconstruction
- Click ID capture (gclid, fbclid, msclkid)
- Source data outside the Eloqua session model
- Forms on third-party pages Eloqua doesn’t fully see
The usual workaround
Custom Data Objects. Cloud Connectors. A six-month implementation.
Eloqua has hooks for all of this: custom data objects, AppCloud, its import interfaces. Standing them up to capture source reliably is a project that typically runs months. Lead Source is the deploy-in-days alternative that fills the gap while a longer-term build runs in parallel (or replaces it). Eloqua is one entry on the list of lead source integrations.
The manual way
- 01Define custom data objects for every source value, then map them onto Contact records.
- 02Wire up a submission handler on every form, then test it on embedded forms, hosted landing pages and tracked sessions.
- 03Build a Cloud Connector or AppCloud component for inbound enrichment from external sources, or commission an Eloqua-certified partner to build one.
- 04Validate against your CDP, 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, click ID 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 a parallel record of truth, or send the source on to wherever your team works. Eloqua itself is left alone.
// Eloqua’s attribution is right when it can be. We deliver the rest.
What you install
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. Run it as a parallel record.
for Eloqua forms embedded on your site
<!-- 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.
Install with Eloqua
Live beside Eloqua in three steps.
1
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.
No credit card required to start. Use whichever install path matches your setup, or use both at once if you have a mix.
2
Install the path that matches your forms
For Eloqua-hosted forms, add your Lead Source link to the form’s completion actions.
Both can run at once, and neither touches your existing Eloqua tracking or your CLR setup.
3
Submit a test through any Eloqua form
The lead appears in your Lead Source dashboard with the source, campaign and full page journey attached.
Common questions
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.
Augment Eloqua attribution. Deploy in days.
Lead Source runs alongside Eloqua's CLR. No conflict, no overwrites, no six-month implementation project. When Eloqua misses a source, we catch it.
Start freeFree to start · no card