Oracle Eloqua connector

Beta

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Oracle Eloqua from the Previews page. See Manage Databricks previews.

The managed Oracle Eloqua connector in Lakeflow Connect ingests marketing data such as contacts, accounts, campaigns, emails, forms, form submissions, and website visitors from Oracle Eloqua into Databricks.

Feature availability

Feature	Availability
UI-based pipeline authoring	Supported
API-based pipeline authoring	Supported
Declarative Automation Bundles	Supported
Incremental ingestion	Supported
Unity Catalog governance	Supported
Orchestration using Lakeflow Jobs	Supported
API-based column selection and deselection	Supported
API-based row filtering	Not supported
SCD Type 2	Supported Tables with VARIANT columns (account, campaign, email, form, form_submission, event_registration, user_info, landing_page, program) do not support slowly changing dimension (SCD) type 2.
Automated schema evolution: New and deleted columns	Supported
Automated schema evolution: Data type changes	Not supported
Automated schema evolution: Column renames	Not supported Requires a full refresh.

Feature	Availability
UI-based pipeline authoring	Supported
API-based pipeline authoring	Supported
Declarative Automation Bundles	Supported
Incremental ingestion	Supported
Unity Catalog governance	Supported
Orchestration using Lakeflow Jobs	Supported
API-based column selection and deselection	Supported
API-based row filtering	Not supported
SCD Type 2	Supported Tables with VARIANT columns (account, campaign, email, form, form_submission, event_registration, user_info, landing_page, program) do not support slowly changing dimension (SCD) type 2.
Automated schema evolution: New and deleted columns	Supported
Automated schema evolution: Data type changes	Not supported
Automated schema evolution: Column renames	Not supported Requires a full refresh.

Authentication methods

Authentication method	Availability
OAuth user-to-machine (U2M)	Supported
OAuth machine-to-machine (M2M)	Not supported
Basic authentication (username/password)	Not supported

Authentication method	Availability
OAuth user-to-machine (U2M)	Supported
OAuth machine-to-machine (M2M)	Not supported
Basic authentication (username/password)	Not supported

Ingest from Oracle Eloqua in 3 steps

note

Before starting, review the Databricks user persona, supported interfaces, ingestion frequency, and common patterns.

1. Configure Oracle Eloqua for ingestion (Admins): Set up Oracle Eloqua to authenticate with Databricks.
2. Create a Unity Catalog connection (Admins): Create a connection in Catalog Explorer to store credentials for Databricks to authenticate with Oracle Eloqua.
3. Create an ingestion pipeline (Admins or non-admins): Select any supported interface and create a pipeline from an existing connection.