Oracle Eloqua Connection Details¶

Introduction¶

Connector Version

This documentation is based on version 23.0.8852 of the connector.

Get Started¶

Oracle Eloqua Version Support

The connector models the Oracle Eloqua REST API as bidirectional tables. Bulk operations are supported through version 2.0 of the Bulk API.

Establish a Connection¶

Authenticate to Oracle Eloqua¶

Oracle Eloqua supports both Basic (login) and OAuth authschemes.

Basic Authentication¶

Basic authentication runs over HTTP via SSL to enable users to connect via login.

To use Basic authentication, specify these properties:

• AuthScheme: Basic.
• Company: The company's unique identifier.
• User: Your login account name.
• Password: Your login password.

OAuth Authentication¶

To enable OAuth authentication from all OAuth flows, you must set AuthScheme to OAuth and create a custom OAuth application.

The following subsections describe how to authenticate to Oracle Eloqua from the three most common authentication flows. For information about how to create a custom OAuth application, see Creating a Custom OAuth Application. For a complete list of connection string properties available in Oracle Eloqua, see Connection.

Desktop Applications¶

To authenticate with the credentials for a custom OAuth application, you must get and refresh the OAuth access token. After you do that, you are ready to connect.

Get and refresh the OAuth access token:

• InitiateOAuth: GETANDREFRESH. Used to automatically get and refresh the OAuthAccessToken.
• OAuthClientId: The client ID assigned when you registered your application.
• OAuthClientSecret: The client secret that was assigned when you registered your application.
• CallbackURL: The redirect URI that was defined when you registered your application.

When you connect, the connector opens Oracle Eloqua's OAuth endpoint in your default browser. Log in and grant permissions to the application.

After you grant permissions to the application, the connector completes the OAuth process:

1. The connector obtains an access token from Oracle Eloqua and uses it to request data.
2. The OAuth values are saved in the path specified in OAuthSettingsLocation. These values persist across connections.

When the access token expires, the connector refreshes it automatically.

Automatic refresh of the OAuth access token:

To have the connector automatically refresh the OAuth access token:

1. Before connecting to data for the first time, set these connection parameters:
   • InitiateOAuth: REFRESH.
   • OAuthClientId: The client ID in your application settings.
   • OAuthClientSecret: The client secret in your application settings.
   • OAuthAccessToken: The access token returned by GetOAuthAccessToken.
   • OAuthSettingsLocation: The path where you want the connector to save the OAuth values, which persist across connections.
2. On subsequent data connections, set:
   • InitiateOAuth
   • OAuthSettingsLocation

Manual refresh of the OAuth access token:

The only value needed to manually refresh the OAuth access token is the OAuth refresh token.

1. To manually refresh the OAuthAccessToken after the ExpiresIn period (returned by GetOAuthAccessToken) has elapsed, call the RefreshOAuthAccessToken stored procedure.
2. Set these connection properties:
   • OAuthClientId: The Client ID in your application settings.
   • OAuthClientSecret: The Client Secret in your application settings.
3. Call RefreshOAuthAccessToken with OAuthRefreshToken set to the OAuth refresh token returned by GetOAuthAccessToken.
4. After the new tokens have been retrieved, set the OAuthAccessToken property to the value returned by RefreshOAuthAccessToken. This opens a new connection.

Store the OAuth refresh token so that you can use it to manually refresh the OAuth access token after it has expired.

Use PASSWORD Grant¶

If you set OAuthGrantType to password, it may trigger an OAuth flow that

passes credentials. In this case, there will be no browser window to authorize.

To ensure that you are authenticated properly, set these connection properties:

• User: The user name.
• Company: The company's unique identifier.
• OAuthClientId The Client ID returned in your custom OAuth application settings. (See Creating a Custom OAuth Application.)
• OAuthClientSecret: The Client Secret returned in your custom OAuth application settings (See Creating a Custom OAuth Application.)
• OAuthGrantType: password.
• InitiateOAuth: GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.

Create a Custom OAuth Application¶

Create a Custom OAuth Application¶

In order to obtain the OAuth credentials needed to authenticate to Oracle Eloqua, you must

create and register an custom OAuth application linked linked to your Oracle Eloqua account.

1. Log in to Oracle Eloqua.

2. Navigate to Settings > Platform Extensions > AppCloud Developer.

3. Click Create New App.

4. Enter a name, icon, and description for the new application, to be displayed

   to users when they connect to Oracle Eloqua.
   The console displays the OAuthClientId and OAuthClientSecret. Record these values for future use.

5. Specify a CallbackURL:

   • If this is a Desktop application, set the CallbackURL to http://localhost:3000, or another port of your choice.
   • If this is a Web application, set the Callback URL to a page where you would like the user to be returned after they authorize your application. to after the user has authorized your application. Note that Eloqua requires that the Callback URL begin with https://, and that you specify a port.

When you connect, the add-in opens the OAuth endpoint in your default browser. Log in and grant permissions to the application.

Fine-Tuning Data Access¶

Fine Tuning Data Access¶

You can use the following properties to gain more granular control over how the connector surfaces the functionality of the underlying Oracle Eloqua APIs.
The connector uses the bulk API when possible; you can fine-tune the connectivity to the bulk API with the following connection properties:

• UseBulkAPI
• BulkPollingInterval
• BulkQueryTimeout
• DataRetentionDuration

Additionally, the following properties are useful to circumvent failed bulk API requests:

• RetryCount
• RetryInterval

Oracle Eloqua accepts characters for table and column names that must be escaped in SQL. You can set UseSimpleNames to true to report nonalphanumeric characters as underscores.

Important Notes¶

Configuration Files and Their Paths¶

• All references to adding configuration files and their paths refer to files and locations on the Harmony Agent where the connector is installed. These paths are to be adjusted as appropriate depending on the agent and the operating system. If multiple agents are used in an agent group, identical files will be required on each agent.

Advanced Features¶

This section details a selection of advanced features of the Oracle Eloqua connector.

User Defined Views

The connector allows you to define virtual tables, called user defined views, whose contents are decided by a pre-configured query. These views are useful when you cannot directly control queries being issued to the drivers. See User Defined Views for an overview of creating and configuring custom views.

SSL Configuration

Use SSL Configuration to adjust how connector handles TLS/SSL certificate negotiations. You can choose from various certificate formats; see the SSLServerCert property under "Connection String Options" for more information.

Proxy

To configure the connector using Private Agent proxy settings, select the Use Proxy Settings checkbox on the connection configuration screen.

Query Processing

The connector offloads as much of the SELECT statement processing as possible to Oracle Eloqua and then processes the rest of the query in memory (client-side).

See Query Processing for more information.

User Defined Views¶

The Oracle Eloqua connector allows you to define a virtual table whose contents are decided by a pre-configured query. These are called User Defined Views, which are useful in situations where you cannot directly control the query being issued to the driver, e.g. when using the driver from Jitterbit. The User Defined Views can be used to define predicates that are always applied. If you specify additional predicates in the query to the view, they are combined with the query already defined as part of the view.

There are two ways to create user defined views:

• Create a JSON-formatted configuration file defining the views you want.
• DDL statements.

Define Views Using a Configuration File¶

User Defined Views are defined in a JSON-formatted configuration file called UserDefinedViews.json. The connector automatically detects the views specified in this file.

You can also have multiple view definitions and control them using the UserDefinedViews connection property. When you use this property, only the specified views are seen by the connector.

This User Defined View configuration file is formatted as follows:

• Each root element defines the name of a view.
• Each root element contains a child element, called query, which contains the custom SQL query for the view.

For example:

{
    "MyView": {
        "query": "SELECT * FROM Contact WHERE MyColumn = 'value'"
    },
    "MyView2": {
        "query": "SELECT * FROM MyTable WHERE Id IN (1,2,3)"
    }
}

Use the UserDefinedViews connection property to specify the location of your JSON configuration file. For example:

"UserDefinedViews", "C:\Users\yourusername\Desktop\tmp\UserDefinedViews.json"

Define Views Using DDL Statements¶

The connector is also capable of creating and altering the schema via DDL Statements such as CREATE LOCAL VIEW, ALTER LOCAL VIEW, and DROP LOCAL VIEW.

Create a View¶

To create a new view using DDL statements, provide the view name and query as follows:

CREATE LOCAL VIEW [MyViewName] AS SELECT * FROM Customers LIMIT 20;

If no JSON file exists, the above code creates one. The view is then created in the JSON configuration file and is now discoverable. The JSON file location is specified by the UserDefinedViews connection property.

Alter a View¶

To alter an existing view, provide the name of an existing view alongside the new query you would like to use instead:

ALTER LOCAL VIEW [MyViewName] AS SELECT * FROM Customers WHERE TimeModified > '3/1/2020';

The view is then updated in the JSON configuration file.

Drop a View¶

To drop an existing view, provide the name of an existing schema alongside the new query you would like to use instead.

DROP LOCAL VIEW [MyViewName]

This removes the view from the JSON configuration file. It can no longer be queried.

Schema for User Defined Views¶

User Defined Views are exposed in the UserViews schema by default. This is done to avoid the view's name clashing with an actual entity in the data model. You can change the name of the schema used for UserViews by setting the UserViewsSchemaName property.

Work with User Defined Views¶

For example, a SQL statement with a User Defined View called UserViews.RCustomers only lists customers in Raleigh:

SELECT * FROM Customers WHERE City = 'Raleigh';

An example of a query to the driver:

SELECT * FROM UserViews.RCustomers WHERE Status = 'Active';

Resulting in the effective query to the source:

SELECT * FROM Customers WHERE City = 'Raleigh' AND Status = 'Active';

That is a very simple example of a query to a User Defined View that is effectively a combination of the view query and the view definition. It is possible to compose these queries in much more complex patterns. All SQL operations are allowed in both queries and are combined when appropriate.

SSL Configuration¶

Customize the SSL Configuration¶

By default, the connector attempts to negotiate SSL/TLS by checking the server's certificate against the system's trusted certificate store.

To specify another certificate, see the SSLServerCert property for the available formats to do so.

Data Model¶

The Oracle Eloqua connector models the Bulk API and the REST API as relational tables, views, and stored procedures. For example, Oracle Eloqua activity types are represented by the corresponding views. Views are tables that cannot be modified.

Working with Oracle Eloqua APIs as Tables

All tables are accessible with the REST API, including custom tables. A limited number of tables and views can be used with the Bulk API. The connector supports version 2.0 of the Bulk API and version 2.0 of the REST API.

Custom Tables and Columns¶

The connector can expose custom tables, views, and columns from Oracle Eloqua that are not mentioned in the Tables and Views. The data model illustrates a sample of what your Oracle Eloqua data model might look like. The actual data model will be obtained dynamically based on your user credentials and Oracle Eloqua account. For example, the Account, Campaign, and Contact tables are dynamic: These tables contain the columns described and your custom columns.

Tables Available in the Bulk API¶

The following tables and views, including custom tables, are supported with the Bulk API:

• Account
• Activity_Bounceback
• Activity_EmailClickThrough
• Activity_EmailOpen
• Activity_EmailSend
• Activity_EmailSubscribe
• Activity_EmailUnsubscribe
• Activity_FormSubmit
• Activity_PageView
• Activity_WebVisit
• Contact
• Custom tables
• CampaignResponses

Stored Procedures

Stored Procedures are function-like interfaces to Oracle Eloqua that complement the data available from Oracle Eloqua tables. Stored procedures implement actions available in the Bulk API and other API functionality that cannot be expressed as SELECT, INSERT, UPDATE, or DELETE statements.

API SQL Limitations

Table-specific API limitations and requirements are documented in Tables and Views; you can use the SupportEnhancedSQL feature, set by default, to circumvent most of these limitations. For both the Bulk and REST APIs, the following limitation exists for filtering on datetime columns: The "=" operator cannot be used with datetime columns in the WHERE clause. However, the "<", ">", ">=", and "<=" operators can be used to filter on datetime columns.

Additionally, the UpdatedAt column only supports filtering with the ">" operator.

Oracle Eloqua also has limited support on multiple conditions. In many tables the AND condition between filters is not supported. If AND is included the server might not return any results, nor will it return an error.

Bulk API Limitations¶

DELETE and UPDATE are not supported by the Bulk API. Additionally, the column count must be <250 for SELECT and must be <= 100 for INSERT.

REST API Limitations¶

Bulk updates are only supported in the Bulk API.

Custom Table Limitations¶

Custom tables are read-only in the REST API. In the Bulk API, SELECT and INSERT are supported.

Tables¶

The connector models the data in Oracle Eloqua as a list of tables in a relational database that can be queried using standard SQL statements.

Oracle Eloqua Connector Tables¶

The connector can expose custom tables, views, and columns from Oracle Eloqua that are not mentioned in the Tables and Views. The data model illustrates a sample of what your Oracle Eloqua data model might look like. The actual data model will be obtained dynamically based on your user credentials and Oracle Eloqua account.

Account¶

Create, update, delete, and query Accounts. This table is supported in bulk mode.

Columns¶

AccountGroup¶

Retrieve Account group.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Campaign¶

Create, update, delete, and query Campaigns.

Columns¶

CampaignResponses¶

Create, delete, and query Campaign Responses. This table is only supported in bulk mode.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Contact¶

Create, update, delete, and query Contacts. This table is supported in bulk mode.

Table Specific Information¶

The EmailAddress column is required for INSERTs and updates.

Columns¶

ContactEmailSubscription¶

Retrieve all email group subscription status for the specific contact.

Columns¶

ContactSegment¶

Create, update, delete, and query Contact Segments.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ContentSection¶

Create, update, delete, and query Content Sections.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Custom¶

Create and delete custom.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Email¶

Create, update, delete, and query Emails.

Table Specific Information¶

Select¶

The following limitation exists for filtering on datetime columns: The "=" operator cannot be used with datetime columns in the WHERE clause. However, the "<", ">", ">=", and "<=" operators can be used to filter on datetime columns.

Additionally, the UpdatedAt column only supports filtering with the '>' operator.

Oracle Eloqua also has limited support on multiple conditions. In many tables the AND condition between filters is not supported. If AND is included the server might not return any results, nor will it return an error.

Columns¶

EmailFooter¶

Create, update, delete, and query Email Footers.

Columns¶

EmailGroup¶

Create, update, delete, and query Email Groups.

Table Specific Information¶

Select¶

The following limitation exists for filtering on datetime columns: The "=" operator cannot be used with datetime columns in the WHERE clause. However, the "<", ">", ">=", and "<=" operators can be used to filter on datetime columns.

Additionally, the UpdatedAt column only supports filtering with the '>' operator.

Oracle Eloqua also has limited support on multiple conditions. In many tables the AND condition between filters is not supported. If AND is included the server might not return any results, nor will it return an error.

Columns¶

EmailHeader¶

Create, update, delete, and query Email Headers.

Table Specific Information¶

Select¶

The following limitation exists for filtering on datetime columns: The "=" operator cannot be used with datetime columns in the WHERE clause. However, the "<", ">", ">=", and "<=" operators can be used to filter on datetime columns.

Additionally, the UpdatedAt column only supports filtering with the '>' operator.

Oracle Eloqua also has limited support on multiple conditions. In many tables the AND condition between filters is not supported. If AND is included the server might not return any results, nor will it return an error.

Columns¶

Event¶

Create and delete Event.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ExternalActivity¶

Create and query External Activities.

Table Specific Information¶

Select¶

This table requires that either Id or ContactId be specified to retrieve data:

SELECT * FROM ExternalActivity WHERE Id = '1111'
SELECT * FROM ExternalActivity WHERE ContactId = '11'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ExternalAsset¶

Create, update, delete, and query External Assets.

Table Specific Information¶

Select¶

The following limitation exists for filtering on datetime columns: The "=" operator cannot be used with datetime columns in the WHERE clause. However, the "<", ">", ">=", and "<=" operators can be used to filter on datetime columns.

Additionally, the UpdatedAt column only supports filtering with the '>' operator.

Oracle Eloqua also has limited support on multiple conditions. In many tables the AND condition between filters is not supported. If AND is included the server might not return any results, nor will it return an error.

Columns¶

Folder¶

Create, update, delete, and query Folders.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Form¶

Create, update, delete, and query Forms.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Hyperlink¶

Create, update, delete, and query Hyperlinks.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

LandingPage¶

Create, update, delete, and query Landing Pages.

Table Specific Information¶

Select¶

The following limitation exists for filtering on datetime columns: The "=" operator cannot be used with datetime columns in the WHERE clause. However, the "<", ">", ">=", and "<=" operators can be used to filter on datetime columns.

Additionally, the UpdatedAt column only supports filtering with the '>' operator.

Oracle Eloqua also has limited support on multiple conditions. In many tables the AND condition between filters is not supported. If AND is included the server might not return any results, nor will it return an error.

Columns¶

Microsite¶

Create, update, delete, and query Microsites.

Table Specific Information¶

Select¶

The following limitation exists for filtering on datetime columns: The "=" operator cannot be used with datetime columns in the WHERE clause. However, the "<", ">", ">=", and "<=" operators can be used to filter on datetime columns.

Additionally, the UpdatedAt column only supports filtering with the '>' operator.

Oracle Eloqua also has limited support on multiple conditions. In many tables the AND condition between filters is not supported. If AND is included the server might not return any results, nor will it return an error.

Columns¶

OptionList¶

Create, update, delete, and query Option Lists.

Table Specific Information¶

Select¶

The following limitation exists for filtering on datetime columns: The "=" operator cannot be used with datetime columns in the WHERE clause. However, the "<", ">", ">=", and "<=" operators can be used to filter on datetime columns.

Additionally, the UpdatedAt column only supports filtering with the '>' operator.

Oracle Eloqua also has limited support on multiple conditions. In many tables the AND condition between filters is not supported. If AND is included the server might not return any results, nor will it return an error.

Columns¶

OptionListElement¶

Create, update, delete, and query Option List Elements.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Views¶

Views are similar to tables in the way that data is represented; however, views are read-only.

Queries can be executed against a view as if it were a normal table.

Oracle Eloqua Connector Views¶

AccountField¶

Retrieve Account Fields.

Columns¶

AccountView¶

Retrieve Account Views.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Activity_Bounceback¶

Retrieve Bounceback Activities. This table is only supported in bulk mode.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Activity_CampaignMembership¶

Retrieve Campaign Membership Activities.

Table Specific Information¶

This table is the only activity table not available in the Bulk API.

Select¶

ContactId is required to query Activity tables.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Activity_EmailClickThrough¶

Retrieve Email Click Through Activities.

Table Specific Information¶

Select¶

If you are not using the Bulk API, ContactId is required to query Activity tables.

Additionally, the COUNT function is supported for this table in bulk mode.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Activity_EmailOpen¶

Retrieve Email Open Activities.

Table Specific Information¶

Select¶

If you are not using the Bulk API, ContactId is required to query Activity tables.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Activity_EmailSend¶

Retrieve Email Send Activities.

Table Specific Information¶

Select¶

If you are not using the Bulk API, ContactId is required to query Activity tables.

Additionally, the COUNT function is supported for this table in bulk mode.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Activity_EmailSubscribe¶

Retrieve Email Subscribe Activities.

Table Specific Information¶

Select¶

If you are not using the Bulk API, ContactId is required to query Activity tables.

Additionally, the COUNT function is supported for this table in bulk mode.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Activity_EmailUnsubscribe¶

Retrieve Email Unsubscribe Activities.

Table Specific Information¶

Select¶

If you are not using the Bulk API, ContactId is required to query Activity tables.

Additionally, the COUNT function is supported for this table in bulk mode.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Activity_FormSubmit¶

Retrieve Form Submit Activities.

Table Specific Information¶

Select¶

If you are not using the Bulk API, ContactId is required to query Activity tables.

Additionally, the COUNT function is supported for this table in bulk mode.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Activity_PageView¶

Retrieve Page View Activities. This table is only supported in bulk mode.

Table Specific Information¶

Select¶

COUNT is supported for this table.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Activity_WebVisit¶

Retrieve Web Visit Activities.

Table Specific Information¶

Select¶

If you are not using the Bulk API, ContactId is required to query Activity tables.

Additionally, the COUNT function is supported for this table in bulk mode.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

CampaignElement¶

Retrieve Campaign Elements.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

CampaignField¶

Retrieve Campaign Fields.

Columns¶

CampaignFolder¶

Retrieve Campaign Folders.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ContactField¶

Retrieve Contact Fields.

Table Specific Information¶

The EmailAddress column is required to INSERT INTO or to update the Contact table. For example,

UPDATE [Contact] SET emailAddress = 'example@test.com', firstName = 'test' WHERE ID = ?

Columns¶

ContactFilter¶

Retrieve Contact Filters.

Columns¶

ContactFilterFolder¶

Retrieve Contact Filter Folders.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ContactList¶

Create, update, delete, and query Contact Lists.

Table Specific Information¶

Select¶

The following limitation exists for filtering on datetime columns: The "=" operator cannot be used with datetime columns in the WHERE clause. However, the "<", ">", ">=", and "<=" operators can be used to filter on datetime columns.

Additionally, the UpdatedAt column only supports filtering with the '>' operator.

Oracle Eloqua also has limited support on multiple conditions. In many tables the AND condition between filters is not supported. If AND is included the server might not return any results, nor will it return an error.

Columns¶

ContactListFolder¶

Retrieve Contact List Folders.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ContactScoringModelFolder¶

Retrieve Contact Scoring Model Folders.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ContactSegmentData¶

Retrieve Contact Segment Data. Note: The pseudo column SegmentID must be specified to retrieve the data of this table. This SegmentID can be retrieved from the ContactSegment table's ID column.

Columns¶

ContactSegmentFolder¶

Retrieve Contact Segment Folders.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ContactView¶

Retrieve Contact Views.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ContentSectionFolder¶

Retrieve Content Section Folders.

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Dependencies¶