Lakeflow Connect adds managed Oracle Eloqua connector in Beta

Databricks has released a managed Oracle Eloqua connector in Lakeflow Connect in Beta. This feature enables teams to ingest marketing data directly into the lakehouse without relying on custom integrations or third-party tools.

Use cases

Imagine your marketing team manages inbound campaigns in Oracle Eloqua and data engineers need to unify those touchpoints in the lakehouse to evaluate conversion and campaign performance. With this connector, you can:

• Ingest contacts, accounts, campaigns, emails, forms, and landing pages.
• Collect form submissions, event registrations, and website visitors.
• Perform incremental ingestion to sync only modified records.
• Maintain historical tracking with SCD Type 2 on compatible tables.

Limitations and requirements

• Maturity: available in Beta. A workspace admin must enable the connector from the Previews page.
• Authentication: supports OAuth user-to-machine (U2M) only. OAuth machine-to-machine (M2M) and basic authentication (username/password) are not supported.
• Filtering and selection: column selection and deselection via API is supported, but row filtering via API is not supported.
• SCD Type 2: not supported for tables with VARIANT columns (account, campaign, email, form, form_submission, event_registration, user_info, landing_page, and program).
• Schema evolution: adding or deleting columns is handled automatically. Changing data types or renaming columns requires a full refresh.

Using it in a pipeline

Setting up the workflow requires three steps: an administrator prepares Oracle Eloqua, creates a connection in Unity Catalog's Catalog Explorer to hold the OAuth credentials, and sets up the ingestion pipeline via the UI, API, or Declarative Automation Bundles. The incoming data lands in your Bronze layer and can be scheduled through Lakeflow Jobs.