Release Notes

October 2023

We now support Pack Mode for all Optimizely connectors, so you can choose the form in which Fivetran delivers your data.

We have updated Packed as the default option for all new connectors. Whereas for all the existing connectors, we have retained Unpacked as the default selection to ensure continued service.

We are gradually rolling out this feature to all existing connectors. For more information, see our Pack mode documentation.

August 2023

The Optimizely 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. Optimizely's priority-first syncs fetch the most recent 30 days' worth of data from the DECISION and CONVERSION tables and their child tables.

To learn more, see our priority-first sync documentation.

August 2022

We no longer sync client activation events (event_type = client_activation).

December 2020

We have expanded the public API endpoints Create a connection and Update a connection. Now you can authorize the following connectors by adding the auth section to payloads:

• AdRoll
• Facebook Pages
• Front
• Google Ad Manager
• Help Scout
• LinkedIn Ad Analytics
• Optimizely
• Pipedrive
• SurveyMonkey
• Zendesk Chat
• Zendesk Support

September 2020

You can now exclude the following tables from the sync:

• DECISION
• CONVERSION
• RESULT

On your connector details page, go to the Schema tab and deselect the tables you want to exclude.

August 2020

We have added the following tables to support Enriched Events Export:

• DECISION
• DECISION_ATTRIBUTE
• CONVERSION
• CONVERSION_ATTRIBUTE
• CONVERSION_EXPERIMENT
• CONVERSION_TAG

We will discontinue the VISITOR_ACTION, RESULT, and RESULT_SEGMENT tables after November 15, 2020. Be sure to update your queries.

April 2020

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

January 2020

You can now exclude the VISITOR_ACTION table from your syncs by deselecting it on the Schema tab in your Fivetran dashboard.

We have added a new table, EXPERIMENT_RESULT_HISTORY.

To improve data security, we will discontinue the aws_access_key and aws_secret_key columns from the LIST_ATTRIBUTE table, on March 1, 2020. Be sure to update your queries.

June 2019

Optimizely has introduced a new way to access your processed results data via an S3 export. We have added two tables to support access to that data:

• RESULT table with the following columns:

  • id
  • campaign_id
  • experiment_id
  • project_id
  • variation_id
  • timestamp
  • account_id
  • visitor_id
  • session_id
  • event_id
  • count
  • revenue
  • value
  • received_timestamp

• RESULT_SEGMENT table with the following columns:

  • id
  • result_id
  • value

February 2019

We released a new version of the Optimizely connector and have made the following schema changes:

• Renamed the existing EVENT table to VISITOR_ACTION table.
• Added a new EVENT table that syncs from /v2/events.
• Converted existing tables EXPERIMENT, EXPERIMENT_PAGE, CAMPAIGN and CAMPAIGN_PAGE to HISTORY tables.
• Dropped EXPERIMENT_STATUS and CAMPAIGN_STATUS tables.
• Separated existing METRIC table into EXPERIMENT_METRIC_HISTORY and CAMPAIGN_METRIC_HISTORY tables.
• Added field event_id in the EXPERIMENT_METRIC_HISTORY and CAMPAIGN_METRIC_HISTORY tables.
• Separated existing CHANGE table into EXPERIMENT_CHANGE_HISTORY and CAMPAIGN_CHANGE_HISTORY tables.