Eloqua integration

Lead source in Eloqua.

Add submission-level source capture to Eloqua, independent of cookies and referrer integrity.

Augment Eloqua attribution → See the install
Deployable in days, not a six-month implementation No conflict with existing tracking scripts Custom Data Object integration optional

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
    Form Submit Listener script captures embedded forms with click-ID and full UTM persistence. Independent of Eloqua’s tracking cookies.
  • 02
    Webhook captures hosted-form submissions and external landing pages, delivered to Eloqua via Bulk API as a Custom Data Object update.
  • 03
    Source recorded with the campaign name written out alongside raw values. Available in your Lead Source dashboard for audit and as Bulk API enrichment for Eloqua reporting.
  • 04
    Or run as a parallel record of truth. Independent of Eloqua entirely, useful for catching the attribution Eloqua misses without committing to a Bulk API integration upfront.

// 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 or push to Eloqua via Bulk API.

example only · for Eloqua forms embedded on your site 
<!-- illustrative. Paste your real snippet from app.leadsource.co -->
<script src="https://leadsource.co/s/[your-site-id].js" async></script>

Add this anywhere in your site’s <head>. Same domain as your Eloqua form embed. Subscribes to Eloqua’s Form Submit Listener event automatically. No conflict with existing tracking script.

example only · for Eloqua landing pages & hosted forms 
# illustrative. Paste your real webhook URL from app.leadsource.co
https://hooks.leadsource.co/[your-account-id]

Use as an external system endpoint in Eloqua’s form completion actions. Receives every submission with source, campaign, and page journey. Optional Bulk API push to your Custom Data Objects.

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

If your Eloqua forms are embedded on your own site, paste the script into your <head>. If your forms are on Eloqua landing pages or external landing pages syncing to Eloqua, configure your form’s external system action pointing 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

Fill in a real form. Submit. Within a minute or two, the submission appears in your Lead Source dashboard with source, campaign, and page journey attached. If Bulk API push is configured, the corresponding Contact record in Eloqua receives the data shortly after.

For Bulk API integration setup (CDO mapping, field mapping, API credentials), contact us and we’ll configure it on your account.
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.

Will Lead Source conflict with Eloqua's tracking script?

No. Lead Source uses Eloqua's public Form Submit Listener API for embedded form integration. The documented integration point Eloqua provides for exactly this purpose. There's no contention with the main tracking script, no interference with cookie management, no impact on Profiler or behaviour-tracking.

Can data be pushed to a Custom Data Object via Bulk API?

Yes. We can deliver source data into Eloqua as a CDO update via the Bulk API on your behalf. You configure the CDO field mapping once and we handle the inbound delivery for every submission going forward. Contact us for setup help.

Does it integrate with Closed-Loop Reporting?

Indirectly. Via Custom Data Object updates that CLR reports against. We don't modify Eloqua's native CLR data structures; we deliver enrichment data that lives alongside, queryable by Eloqua's reporting engine and by your downstream BI tools.

Does it work with Marketing Cloud Account Engagement (post-Pardot rename)?

Yes. See our Salesforce integration page, which covers MCAE (the rebranded Pardot). The webhook install path applies equally to MCAE-hosted forms and Eloqua-hosted forms.

What about Eloqua Profiler and engagement scoring?

Lead Source doesn't modify Profiler data or engagement scores. Source data we capture can optionally feed into Eloqua as a Custom Data Object, which can then be referenced by scoring rules if you want, but that's configuration you control, not something we change automatically.

Augment Eloqua attribution. Deploy in days.

Lead Source runs alongside Eloqua&rsquo;s CLR. No conflict, no overwrites, no six-month implementation project. When Eloqua misses a source, we catch it.

Start free

Free to start &middot; no card