Eloqua integration

Lead source in Eloqua.

Submission-level source capture that runs beside Eloqua, not inside it. No implementation project, no cookies to depend on.

Augment Eloqua attribution → See the install
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

Form Submit Listener Custom Data Objects Bulk API integration AppCloud-compatible 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)
  • Form Submit Listener via JS API
  • Custom Data Objects for extended attribution
  • Bulk API and REST API 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. CDOs, AppCloud, Bulk API. 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).

The manual way

  • 01
    Define Custom Data Objects for source, campaign, channel, and full page journey. Configure field-mapping to Contact records.
  • 02
    Configure Form Submit Listener handlers in JavaScript on every form. Test across embedded contexts, hosted landing pages, and Profiler-tracked sessions.
  • 03
    Build a Cloud Connector or AppCloud component for inbound enrichment from external sources. Or commission an Eloqua-certified partner to build one.
  • 04
    Validate against your CDP, ad-platform data, and Salesforce records. Reconcile attribution discrepancies. Maintain it as the org evolves.

With Lead Source

  • 01
    One script on your site captures the real source, campaign, click ID and full page journey when the visitor lands.
  • 02
    Eloqua’s own hosted forms live on Eloqua’s domain, so a script cannot reach them. Point their completion action at a Lead Source webhook URL instead.
  • 03
    The lead lands in your Lead Source dashboard named, with the real source and the pages read before the form.
  • 04
    Run it as a parallel record of truth, or push it onward with Zapier or your own webhook endpoint. Eloqua itself is left alone.

// Eloqua’s attribution is right when it can be. We deliver the rest.

What you install

Two install paths. Pick the one that matches your forms.

Sign up to get both a script tag and a webhook URL. Use the script with Eloqua’s Form Submit Listener API for forms embedded on your own site. Use the webhook for Eloqua-hosted forms and landing pages. Deliver as a parallel record.

example only · for Eloqua forms embedded on your site 
<!-- illustrative. 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.

example only · for Eloqua landing pages & hosted forms 
# illustrative. Paste your real webhook URL from app.leadsource.co
https://app.leadsource.co/api/capture/webhook/YOUR_SITE_KEY

For Eloqua-hosted forms, use this as an external system endpoint in the form’s completion actions. Every submission arrives with its source attached.

Sign up to get both →
Install with Eloqua

Three steps. Done in five minutes.

1

Sign up. Get both your snippet and your webhook URL

Create your free Lead Source account. Your dashboard shows both: a script tag for sites you control, and a webhook URL for receiving submissions from hosted forms.

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, configure the form’s external system callout to point at your Lead Source webhook URL.

Both can run simultaneously. Lead Source deduplicates submissions automatically and respects existing Eloqua tracking. No contention with 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.

Related

Other tools we work with

CRM

Lead source in Salesforce

For B2B stacks running Eloqua + Salesforce. One capture, both records.

Read → CRM

Lead source in HubSpot

For comparison: same attribution gap, different platform mechanics.

Read → Product

How Lead Source works

The script, the webhook, the dashboard. Three minutes of reading.

Read →
Common questions

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 callout. Nothing inside Eloqua is modified.

Can the source reach Eloqua as a Custom Data Object?

Not directly. Lead Source holds the record and Zapier or your own webhook carries it onward, so anything that can consume our payload can receive it. There is no built-in Bulk API push.

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 webhook path 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 free

Free to start · no card