Optimizelylink
Optimizely is an experimentation platform, enabling businesses to deliver continuous experimentation and personalization across websites, mobile apps, and connected devices.
Featureslink
| Feature Name | Supported | Notes |
|---|---|---|
| Capture Deletes | ||
| Custom Data | check | VISITOR_ACTION and EXPERIMENT_CHANGE_HISTORY tables only |
| Data Blocking | check | VISITOR_ACTION, RESULT, DECISION, and CONVERSION tables. |
| Column Hashing | ||
| Re-sync | check | Connector level |
| History | check | CAMPAIGN_HISTORY, EXPERIMENT_HISTORY, CAMPAIGN_PAGE_HISTORY,CAMPAIGN_METRIC_HISTORY, CAMPAIGN_CHANGE_HISTORY, CAMPAIGN_CHANGE_DEPENDENCY_HISTORY, EXPERIMENT_VARIATION_HISTORY, EXPERIMENT_VARIATION_ACTION_HISTORY, EXPERIMENT_PAGE_HISTORY, EXPERIMENT_METRIC_HISTORY, EXPERIMENT_CHANGE_HISTORY, and EXPERIMENT_CHANGE_DEPENDENCY_HISTORY tables only |
| API Configurable | check | |
| Priority-first sync | ||
| dbt Package |
Setup guidelink
Follow our step-by-step Optimizely setup guide to connect Optimizely with your destination using Fivetran connectors.
Sync overviewlink
Fivetran can sync historical data from Optimizely as long as it is stored in your S3 bucket.
Schema informationlink
This schema applies to all Optimizely connectors
To zoom, open ERD in new window
Schema noteslink
Optimizely states that there are no duplicates in the event files, so Fivetran adds _fivetran_id (which is a hash of the entire record) as the primary key for the VISITOR_ACTION table.
_fivetran_id is a calculated hash that is added as the primary key in metrics as well as in the EXPERIMENT_PRIORITY table.