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.
We now store custom timestamp fields in the TIMESTAMP WITH TIME ZONE format (for example,
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
updated_at, in the TIMESTAMP WITH TIME ZONE format (for example,
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.
You can now exclude custom objects from your syncs by deselecting them on the Schema tab in your Fivetran dashboard.
We have added two new tables,
CONTACT_ACTIVITYtable contains contact activity data.
VISITORtable contains details about visitors to your website.