Release Notes

October 2024

You can now limit the amount of historical data you want to sync for the CONTACT_ACTIVITY and custom object tables. We have added a new optional drop-down menu, Historical Sync Limit, to the connector setup form. We have also added a new config parameter, historical_sync_limit, to the REST API config. For more information, see our documentation.

April 2024

We now support table level re-syncs for Eloqua connectors.

February 2024

We have changed the behavior of the following tables in relation to the custom columns:

• ACCOUNT
• CONTACT
• CAMPAIGN

If a custom column name in one of the tables matches the name of a standard column, then we append the prefix, custom_, to the column name. If applicable, we will sync all data to the new column(s).

For example, the CONTACT table has a province column. If you add a new custom column province to the table, the custom column name in your destination will be custom_province. However, if your custom column name is province_country for which a standard column does not exist, the column name in the destination will not change.

To re-sync these tables, contact Fivetran support.

December 2023

The Eloqua connector now supports priority-first sync for custom objects. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Eloqua's priority-first syncs fetch the most recent 7 days' worth of data from the custom object tables. To learn more, see our priority-first sync documentation.

November 2023

We now delete the contact export definitions created by the Eloqua connector for syncing the CONTACT_LIST_CONTACT and CONTACT_SEGMENT tables. We delete these definitions at the end of each sync, which may temporarily increase your sync durations until the backlog of existing definitions are cleared. We are gradually rolling out this change to all Eloqua connectors.

July 2023

We have added a new column, current_status, to the FORM table.

We now capture deletes for the following tables:

• CAMPAIGN
• EMAIL
• FORM

June 2023

The Eloqua connector now supports data blocking for all Eloqua tables. You can now choose which tables to sync and which to block from syncing to your destination. On your Connector Details page, go to the Schema tab and select or deselect the tables. If you want to sync a child table, you must include the parent table in the sync.

December 2022

You can now exclude the VISITOR table from your syncs. On your Connector Details page, go to the Schema tab and deselect the table.

We have added the following new tables:

• CONTACT_FILTER
• CONTACT_FILTER_SEGMENT_ELEMENT
• CONTACT_LIST
• CONTACT_LIST_CONTACT
• CONTACT_LIST_SEGMENT_ELEMENT
• CONTACT_SEGMENT
• SEGMENT

We are gradually rolling out this change to all existing connectors.

November 2022

We have added two new columns, fax and mobile_phone, to the CONTACT table. To sync your historical data from the newly added columns, contact our support team.

July 2022

The Eloqua connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Eloqua's priority-first syncs fetch the most recent 7 days' worth of data from the CONTACT_ACTIVITY table. To learn more, see our priority-first sync documentation.

November 2021

We have added the following new columns to the CONTACT table:

• address1
• address2
• address3

If you want to sync historical data for these columns, contact Fivetran Support to re-sync the CONTACT table.

August 2021

We have added a new primary key column, activty_type, to the CONTACT_ACTIVTY table. This change prevents data integrity issues when multiple contact activities have the same id.

April 2021

We have added a new table, USER_INFO, to support Users endpoints.

We have added the following new columns to the CONTACT table:

• account_name
• bounceback_date
• city
• created_by
• current_status
• description
• first_name
• is_bounceback
• is_subscribed
• last_name
• postal_code
• province
• sales_person
• subscription_date
• title
• unsubscription_date
• updated_by

March 2021

We have added two new tables, CONTACT_LIST and CONTACT_LIST_CONTACT, to support Contact list endpoints.

We have added the following new tables to support Contact segments endpoints:

• SEGMENT
• CONTACT_FILTER_SEGMENT_ELEMENT
• CONTACT_FILTER
• CONTACT_LIST_SEGMENT_ELEMENT
• CONTACT_SEGMENT

February 2021

We now add a prefix, custom_, to a custom column name if we find a standard column with the same name in the FORM_SUBMISSION table.

If your FORM_SUBMISSION table contains custom columns and standard columns with the same names, contact support to re-sync your FORM_SUBMISSION table. See our Eloqua ERD for more information on the standard columns in the FORM_SUBMISSION table.

January 2021

We have added the following new columns to the CAMPAIGN table:

• accessed_at
• badge_id
• clr_end_date
• created_by
• current_status
• first_activation
• is_read_only
• member_count
• run_as_user_id
• scheduled_for
• source_template_id
• updated_by

Trigger a re-sync to backfill the history data for these columns.

We have added 3 new tables to support Eloqua's Email API:

• EMAIL
• EMAIL_FORM
• EMAIL_HYPERLINK

November 2020

We now add a prefix, custom_, to a custom column name if we find a standard column with the same name in your custom object table.

If your custom object table contains custom columns and standard columns with the same names, contact support to re-sync your custom object table. See our Eloqua ERD for more information on the standard columns in the custom object tables.

July 2020

We now store custom timestamp fields in the TIMESTAMP WITH TIME ZONE format (for example, 2020-06-28T16:02:25.987Z).

May 2020

We now store custom timestamp fields in the TIMESTAMP WITHOUT TIME ZONE format (for example, 2020-02-28T16:02:25). These custom fields use the Eastern Time Zone (ET). Previously, we used the Epoch timestamp format to store custom timestamp fields. We will re-sync existing custom tables so that they use the new TIMESTAMP WITHOUT TIME ZONE format.

NOTE: We will continue to store Eloqua system-level timestamp fields, such as created_at and updated_at, in the TIMESTAMP WITH TIME ZONE format (for example, 2020-02-28T16:02:25.987Z).

You can now configure your Eloqua connector using the Fivetran REST API. This feature is in BETA and is available only for Standard and Enterprise accounts.

September 2019

You can now exclude custom objects from your syncs by deselecting them on the Schema tab in your Fivetran dashboard.

May 2018

We have added two new tables, CONTACT_ACTIVITY and VISITOR.

• The CONTACT_ACTIVITY table contains contact activity data.
• The VISITOR table contains details about visitors to your website.