Oracle Eloqua connector FAQ
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.
Find answers about supported tables, historical data, deleted records, and authentication for the managed Oracle Eloqua connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which tables does the connector support?
For the list of supported tables, see Supported source tables. For the full schemas, see Destination table schemas.
How far back can the connector ingest data?
For form_submission, the first sync ingests submissions from the previous 760 days. For other incremental tables, the first sync ingests records updated since 2015-01-01T00:00:00Z. Each later sync ingests records modified after the last run. Full-refresh tables reingest all available records on every run. To change the start date of the first sync, set the start_datetime option. See Connector options.
Does the connector capture deleted records?
Full-refresh tables reflect deletions on every run. Incremental tables don't capture records deleted in Oracle Eloqua until you run a full refresh of the table.
Which authentication methods does the connector support?
The connector supports OAuth user-to-machine (U2M) authentication only, through an app that you register in the Oracle Eloqua AppCloud Developer Framework. OAuth machine-to-machine (M2M) and basic authentication with a username and password aren't supported.