Eloqua Release Notes

November 2021link

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 2021link

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 2021link

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 2021link

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 2021link

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 2021link

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 2020link

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 2020link

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

May 2020link

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 resync 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 2019link

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

May 2018link

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.