Sequel connects natively to Oracle Eloqua so every webinar registration, attendance record, and engagement signal flows into your marketing automation platform automatically — with no manual exports and no post-event data cleanup.

What flows into Eloqua

When someone registers (immediately):

Contact details, custom registration questions, UTM and attribution parameters, campaign association, registered status.

When the event ends (within ~10 minutes):

Attended / no-show status, live minutes watched, percentage viewed, poll responses, Q&A questions, CTA clicks, resource downloads.

When someone watches on demand (as it happens):

On-demand status, minutes watched, and the same full engagement payload.

On-demand tracking continues indefinitely after the live event. A registrant who returns three weeks later to watch the replay generates the same depth of data as a live attendee — including engagement with polls, CTAs, and resources left open on the recording.

Where the data lands

You decide the destination. Sequel supports:

- Contact fields — straightforward for scores, summaries, and single-value attributes

- Native Eloqua objects — campaign membership with automatic status progression

- Custom Data Objects (CDOs) — the most common choice for teams that want full control over structure and downstream segmentation

Field mapping is configured through the Sequel interface, at two levels:

- Account level — set once; applies to every event your team runs

- Event level — per-webinar campaign IDs, status values, and any event-specific fields. Save as a template so your team only changes one value per event.

Sequel determines attended, no-show, and on-demand status internally. If you currently maintain automation in Eloqua purely to derive those statuses, you can retire it.

Registration- three options:

Your registration process doesn't have to change. Choose whichever fits your stack:

1. Keep your Eloqua form

Your existing form stays exactly where it is. Sequel listens for the submission, registers the attendee, sends the confirmation email, and turns that same page into the live event experience when it starts. No form migration, no new process for your campaign team.

2. Register via your backend

If you run validation, enrichment, approval, or consent logic before accepting a registrant, call Sequel once the registration is approved. Full control stays with you.

3. Route through Eloqua

Keep posting registrations to Eloqua exactly as you do today. Eloqua passes the registrant to Sequel. Nothing changes on your website or in your campaign operations workflow.

Many teams start with option 1 or 3 to avoid disrupting an established process, then adopt Sequel's native forms later for the time savings — conditional logic, UTM passthrough, default values, multi-language support, and validation are all built in.

Beyond the Standard Sync:

Sequel Score — an engagement-based lead score calculated from activity across all of your webinars, delivered as an additional Eloqua field to layer onto your existing scoring model.

AI engagement summaries — a plain-language summary of everything a lead or account has done across your webinar program and website, written for sales to act on directly. Delivered as a text field in Eloqua, refreshed after each event and whenever new on-demand views are detected. Available at both lead and account level, and tunable to your ICP, segments, and preferred length.

Multiple Eloqua Instances

Fully supported. Teams running separate Eloqua instances — by business unit, region, or brand — get a dedicated Sequel workspace per instance, each with its own integration, branding, templates, and events. A parent account retains visibility across all of them, and granular custom roles control which teams can see and edit what.

Getting Started

To configure the integration we need:

- An Eloqua API user with scoped access, and its authentication token

- The Custom Data Object ID, if you're using CDOs

- A short working session with your marketing operations team to agree on field mapping — which Sequel fields land where, in which objects, with which status values

Setup is typically completed in a single session. Enterprise customers work with a dedicated implementation specialist alongside their customer success manager, who stay involved as your Eloqua configuration evolves.

Common Questions

How quickly does data arrive?

Registrations post immediately. Post-event data is aggregated and synced within roughly ten minutes of the event ending.

Can we re-push data?

Yes. Engagement data is retained in Sequel, so any event can be re-synced to Eloqua on request.

Is there a limit on Custom Data Objects?

Not from Sequel's side. You create the CDOs you need and share the IDs with us.

Does this work for pre-recorded and in-person events?

Yes. Simulive events capture polls, chat, and CTA engagement exactly as live events do, and in-person events use the same mapping configuration. One integration covers your entire event program.

Can we send data elsewhere too?

Yes. Eloqua can run alongside other destinations — CRM, ABM platforms, or your data warehouse — and Sequel's APIs let you pull raw engagement data into your own systems.