Oracle

Oracle Eloqua

Curated anchor platform in b2b marketing automation with material relevance to the Marcom operating stack and a first-party developer surface.

Marketing automation, lifecycle & CDPSystem of engagementExtensible SaaS
System roleSystem of engagement
Access maturityExtensible SaaS
Agent postureBridge
Reference updatedMay 1, 2026
BYO-UI reviewedJul 10, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Contacts, accounts, custom objects, activities, external activities, events, campaign responses, opportunities, campaigns, emails, landing pages, forms, images, and segments.

02 · Data you can retrieve

Query and bulk import/export Eloqua elements; retrieve campaign assets, permissions, fields, activities, and operational state.

03 · Actions and write paths

Create, update, and delete supported contacts, accounts, custom objects, fields, campaign assets, AppCloud applications, and bulk synchronizations.

04 · Authentication and permissions

Eloqua authentication, instance permissions, asset-level permissions, app scopes, and bulk synchronization credentials apply.

05 · Monitoring, approval, and recovery

Protect contact consent, field permissions, campaign activation, asset ownership, bulk-sync correctness, and send/launch authority.

06 · Gaps and implementation limits

No product-native provider MCP was verified; Oracle Integration can expose approved workflows. Bulk and Application APIs have different semantics.

Agent access

MCP and adjacent posture

First-party bridge can expose workflows; no product-native provider verifiedOracle Integration bridge; no Eloqua-native provider verifiedNo first-party provider verified

Role: bridge

Read scope: No first-party MCP read surface verified.

Write scope: No first-party MCP write surface verified.

Authentication: Not applicable to a first-party MCP provider.

Approval boundary: Any customer-built adapter must define its own approval and confirmation controls.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access1
Identity4
Governance4
Agent access2
UI extensibility4
Portability3
Observability3
Documentation4

Proposed interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that Oracle ships these experiences.

Single-platform patterns

  • Enterprise B2B campaign and lead-nurture cockpit
  • Lifecycle journey debugger
  • Audience activation workbench
  • Campaign QA and approval room
Use in the brief composer →

Multi-platform compositions

  • Oracle Eloqua + CRM or commerce system: lifecycle journey debugger
  • Oracle Eloqua + warehouse or CDP + content-production platform: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

4 recorded sources
HomepageSource inventory
https://www.oracle.com/cx/marketing/automation/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to the representative first-party source or targeted access review.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.