Adobe Analytics
Adobe Analytics lets you analyze data about customer engagement with your website or application.
Adobe only allows us to connect to the reporting layer of their API, so we can't access all the raw data like we can for many of our other connectors. Instead, Adobe must be queried through a pre-defined report.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | ||
| History mode | ||
| Custom data | check | |
| Data blocking | check | |
| Column hashing | check | |
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | check | |
| Fivetran data models | ||
| Private networking | ||
| Authorization via API |
Setup guide
Follow our step-by-step Adobe Analytics setup guide to connect Adobe Analytics with your destination using Fivetran connectors.
Schema information
Fivetran delivers custom tables with the standard fields - report_suite_id and datetime. You can add as many custom tables as you'd like. In each custom table, add as many custom fields as you'd like, such as elements, metrics, calculated metrics, and segments.
| column | type | notes |
|---|---|---|
| report_suite_id | STRING | standard field |
| datetime | INSTANT | standard field |
| element* | custom field | |
| metric* | custom field | |
| calculated_metric* | custom field | |
| segments* | STRING | custom field |
Updating data
Because Adobe Analytics data is delivered in a cube, changing the way that the cube is formatted is difficult. Adding or removing fields changes the way the data is aggregated and synced.
Instead, to ensure that the data you're receiving is reliable, we require that you create an entirely new connector for the updated version of your report. Keep in mind, you must:
- Name this new/modified report something different from the previous version. Or
- Keep the name of the new/modified report the same as the previous version, but delete the previous version beforehand. Or
- Keep the name of the modified report and sync it into a different schema.