Skip to main content
Use the @bijection/connectors/eloqua entrypoint to declare Oracle Eloqua resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
Contacts

​
changes: Contacts by C_DateModified, walked by updatedAt

The following example matches configuration standard.

​
Configuration: standard

Case: eloqua/contacts/changes/standard. Connection and resource configuration are declared by this exact case. Credential kind: eloqua. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: contacts
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
bulk: Bulk API 2.0 contact exports from the carried C_DateModified

The following example matches configuration standard.

​
Configuration: standard

Case: eloqua/contacts/bulk/standard. Connection and resource configuration are declared by this exact case. Credential kind: eloqua. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: contacts
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Activities

​
bulk: Bulk API 2.0 activity exports of one type in CreatedAt windows

The following example matches configuration standard.

​
Configuration: standard

Case: eloqua/activities/bulk/standard. Connection and resource configuration are declared by this exact case. Credential kind: eloqua. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: activities
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The binding’s baseUrl is the site’s pod REST address, <urls.base>/api/REST/1.0/, where urls.base is what https://login.eloqua.com/id answers for the site, such as https://secure.p03.eloqua.com/api/REST/1.0/. Discovery is not repeated: an instance Oracle moves to another pod needs its baseUrl rebound. Bind an eloqua credential: basic (<site name>\<user>:<password>) or an OAuth 2.0 bearer token. contacts.changes lists GET data/contacts?depth=complete&count=300&page=1&orderBy=updatedAt ASC with search=C_DateModified>'<wall time>'. Eloqua compares C_DateModified only as US Eastern wall time at whole seconds, so the guest passes a UTC since and the host renders it in America/New_York, one second earlier because the search is strict. Inside the repeated autumn hour the rendering moves one hour earlier, so that hour is re-read rather than skipped; how Eloqua reads a wall time in that hour is not documented. Each request is page one from the largest updatedAt (epoch seconds) the previous page returned, a continuation the host derives from the retained page, so an edit during a pass cannot shift a contact past a page boundary. The boundary second is re-read and deduplicated by version (updatedAt). A first pass lists without a search; a 204 is an empty page. A finished pass carries the largest updatedAt and the next begins five minutes before it. A page out of updatedAt order, a row older than the bound less the repeated hour, and a full page of contacts sharing one second are refused. Each record carries the documented contact properties and fieldValues as JSON text. Not observed: deletions, which this listing does not report. No command is declared. The site id is answered only by login.eloqua.com/id, another origin, so the connection is its own identity namespace.

​
Bulk API 2.0 exports

Compiled declaration examples and configuration details are published in the connector reference. The bulk modes bind the site’s Bulk address, <urls.base>/api/bulk/2.0/ (urls.apis.rest.bulk from https://login.eloqua.com/id), with the same eloqua credential. Only the user who ran a sync may read its data. Each pass is one export run as a provider job. The pass creates an export definition (POST contacts/exports or activities/exports) with areSystemTimestampsInUTC: true, twelve hours of data retention and automatic deletion after a day. Then POST syncs kicks the job off; the answer’s uri /syncs/<id> names the job. GET syncs/<id> is polled every minute while its status is pending or active. success is ready; warning, error, errored or a 404 end the pass with a typed gap. The sync’s data is then read at syncs/<id>/data?offset=&limit=128, the host naming each offset, until a page says hasMore: false.
  • contacts.bulk exports {{Contact.Id}} (the key), email, first and last name, C_DateCreated, C_DateModified (the version) and any further fields you name by internal name, at most 32 in all. A first pass exports every contact. Later passes filter C_DateModified >= five minutes before the previous sync’s createdAt.
  • activities.bulk exports one activity type, keyed by {{Activity.ExternalId}}, which Oracle states is unique across types. {{Activity.Id}} is not unique for EmailSend. CreatedAt is the version. Exports run in CreatedAt windows of windowDays (default 7, at most 31) from since, because one activity sync holds at most five million records. Once a window reaches the sync’s creation, the next pass re-reads lag seconds (default 3600) for activities Eloqua records late, such as bouncebacks. An activity recorded later than that is missed.
Oracle notes that an export filtered on a modification time can return a record twice. A second copy on another page deduplicates by version. Two copies on one page of 128 are refused rather than merged. Deleted contacts are not exported, and activities of deleted contacts are excluded, so no deletion is observed. Built from Oracle’s published Eloqua REST and Bulk API documentation; nothing here has run against an Eloqua site or been qualified.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.